Most organizational change failure stories begin with inspirational town halls and end with the old system quietly returning. We pour coaching and communications into people while the structures that govern priorities, approvals, and promises stay untouched.
Consider three composite scenarios drawn from dozens of observations. In one, a bank-sized organization trains hundreds of people on agile rituals, yet sprint reviews stay theatrical because compliance still locks scope six months ahead. In another, a consumer brand rolls out a new CRM with beautiful playbooks, but account teams are still paid for solo wins, so collaboration dies the second targets are under threat. In a third, a manufacturer reorganizes around customer journeys, only to route every investment through the same capital committee, so decisions crawl and people quietly rebuild the old escalation chains.
In each case, the system snaps back because the underlying agreements never moved: who can say yes, what gets measured, which constraints are sacred.
Our own post-mortems keep surfacing the same warning: inspiration cannot outrun structural friction. If incentives, decision paths, and capacity stay untouched, the system drags people back to the old equilibrium no matter how excited they sounded in the kickoff.
Systems thinkers like Donella Meadows and Peter Senge describe this as a balancing loop: every push on performance triggers a counterforce that protects the current equilibrium. If you chase speed, the hidden loop tightens around risk reviews. If you chase innovation, the loop reroutes budget approvals. You cannot coach your way past a balancing loop; you have to change the promises that keep it in place.
That is the bridge into the practical work. A promise inside a system is simply an agreement about an outcome, the boundary that protects it, and the evidence that proves it happened. Some promises are throughput promises (deliver X by Y), some are quality promises (meet this tolerance, uphold this standard), and some are learning promises (surface a constraint before it snaps). When you can name which kind you are reshaping, the diagnostic work below becomes far less chaotic.
Start every change initiative by mapping the agreements that currently make the status quo rational. If you cannot point to a promise that will change, you are not running a transformation, but a communication plan. Document who benefits from the current promise, what risk it protects, and what evidence would make them comfortable signing a different one. That worksheet becomes your negotiation script when resistance shows up later.
Look for agreements such as “All customer discounts above 5% need CFO approval,” “Capacity planning happens quarterly,” or “People earn bonuses for keeping their headcount flat.” Each one explains why smart people cling to the current behavior. When you can point to the promise that will change, you are finally working on the system, not just the messaging. This might include moving pricing guardrails to the product line, shifting capacity reviews to rolling six-week windows, or rewarding teams for sharing talent instead of hoarding it.
Integrity leaks hide inside overlapping commitments
Authenticity and integrity decay when teams are forced to make conflicting promises. Sales commits to bespoke delivery, operations commits to standardization, and finance commits to cost reductions in the same quarter. Nobody is lying; the system is forcing mutually exclusive truths.
The fastest diagnostic is to follow a single customer or employee journey (such as work process from idea to delivery) and note every time ownership becomes unclear. Each handoff is a potential integrity leak. When people spend more energy defending their identity (“we are the team that never misses a date”) than describing reality, the change effort is already underwater. Map the promises that collide at each handoff, then ask what constraint keeps them both alive. Often it is something mundane: legal review cycles, an OKR written three quarters ago, or a leader who still approves every exception. Naming the constraint out loud gives you an actionable list of structural fixes instead of vague pleas for collaboration.
Capture those leaks and feed them into your Organizational Change collection so future initiatives start with a list of known fault lines instead of rediscovering them under pressure.
Design structural guardrails that carry the new behavior
Once the leaks are visible, redesign the work so the system, and not heroics, supports the new behavior.
- Replace one recurring approval with a boundary. Specify the budget, risk, or customer segment where teams decide without escalation.
- Shift reporting to highlight what was learned, not just what was delivered. Pair every metric with a short narrative: which new agreement was tested, what constraint surfaced, what will change next sprint. Dashboards that celebrate these promises (systemic, not delivery) kept teach teams how the new system works far faster than activity charts.
- Schedule integrity reviews instead of status meetings. Spend 15 minutes inspecting one agreement in depth: who owns it, what support it lacked, and what constraint needs redesign. Not to blame someone but to understand how the system acts.
Watch for subtle signals that the system is carrying more of the load: escalation volume drops, cross-team arguments reference shared boundaries, and retros focus on experience instead of blame.
Keep promises small and inspect them in daylight
Grand change narratives rarely survive the quarter. Small, structural promises do. Commit to redesigning one hiring loop, one budget handoff, or one product launch ritual per sprint and publish the before/after inside the Organizational Change collection so everyone can see what “different” looks like. Do the good work, then talk about it so the story of change is grounded in evidence, not slogans.
Invite teams into integrity walks: short sessions where people bring a promise that feels impossible to keep and, together, you change the system around it. That habit builds the muscle for continuous change and keeps authenticity attached to visible actions instead of slogans.
Before you declare victory, run a monthly integrity check with three simple questions: Which promise felt fragile? Which boundary held under pressure? Which constraint reappeared even after we redesigned it? Writing down the answers keeps leaders honest about whether the system and not charisma is carrying the change.
If you want a facilitated version, our Learning Organisation workshop spends a day mapping these promises and designing experiments that stick. Reach out when you are ready to replace inspiration with new agreements.
