Designed to Stall
Why the system keeps rewarding the choices that cause transformation to fail
There is a leader at most major enterprises right now who can see why their transformation may stall, has some authority to prevent it and will still be pulled toward choices that leave the stall pattern intact.
That is not mainly a story about weak leaders. It is a story about rational leaders operating inside an accountability system that rewards visible motion, diffuses consequences and treats structural design as optional until the damage is already visible.
The 70 percent transformation failure rate has held steady across decades. It has survived Six Sigma, agile transformation, lean methodologies, change management certification and an entire industry of consulting frameworks. Most leaders who have been through this cycle more than once can name the patterns themselves. The diagnosis is not the problem. The work that the diagnosis points to keeps not getting done.
The downstream consequence is the pattern most readers will recognize. The program stalls. A retrospective is convened. The findings are familiar: timeline was aggressive, scope was too broad, change management was insufficient, organizational readiness was misjudged. Accountability lands one or two levels below the actual decision point. The program director is replaced. The consulting firm is blamed. The VP who agreed to the scope has been promoted. The CFO who set the timeline has signed off on the post-mortem. The leader who declined to address the structural issues at launch is at the next company.
I have watched this play out across enough transformations to recognize that the post-mortem above is not a parody. It is the median outcome. The same five breakpoints reappear in the next transformation. The same four forces go unstewarded. The same design decisions get skipped.
“The Five Breakpoints” described the visible failure patterns. “The Stewardship Gap” traced them back to the underlying conditions that have to be sustained. This piece takes on the harder question: if the diagnosis is widely available and the prescription is understood, why does the failure rate hold?
The argument is that 70 percent is not a knowledge gap. It is a structural feature of how leadership accountability works in modern enterprises. Telling leaders to be different leaders has been the field’s response across decades. It has not moved the number. Moving it requires changing the system, not just the people inside it.
Why Leaders Skip the Design Work
Three pressures, all individually rational, push the design work off the leader’s plate. Each one alone would weaken the design discipline. Together, they make skipping it the path of least resistance.
Skill gravity
Senior executives are real experts in customer engagement, product judgment, operational firefighting and managing the board. Those activities produce visible results quickly and feel like leading. Organizational design is structural, slow, produces no short-term signal that anyone tracks and requires political confrontation with peers. It gets crowded out. The layer that should own it most, the group just below the CEO, is the layer most consumed by upward management and execution crises. The work falls in the gap between strategy above and delivery below. It belongs to everyone in theory and to no one in practice.
The feedback gap
Senior executive tenure averages around four years and is shorter for many transformation-era roles. Major organizational design decisions take 18 to 36 months to produce visible consequences. Most leaders who skip the design work will not be in the role when the transformation stalls. Accountability diffuses by the time the consequences arrive. The failure lands in the delivery layer, while the design choices that made the failure likely remain largely unexamined. There is no corrective feedback loop, so the same choices get made again by the same kind of leader.
Career calculus
Senior executive roles carry significant compensation and, for many leaders, real financial stakes. A real transformation effort means visible risk: political conflict, short-term disruption that looks like underperformance before it looks like progress and the possibility of being the person associated with a failed initiative.
There are softer alternatives that avoid most of that risk: a reorganization that signals decisiveness without redesigning incentives, a technology investment that demonstrates activity without requiring process change, a communications campaign that updates the language without changing the operating model. The board’s visibility into the difference is limited in the early years, and each leader who responds incrementally leaves the organization slightly more resistant to the next genuine attempt.
These are not character flaws in individual leaders. They are predictable responses to a system that rewards visible action over structural design, distributes consequences across a longer time horizon than tenure and treats incremental motion and substantive change as equivalent for purposes of board reporting and analyst calls.
What “Better Leaders” Does Not Fix
The dominant response from the change management field, across decades, has been to address this through training, certification, methodology and exhortation. Tell leaders what good design looks like. Show them frameworks. Make the case for sustained executive sponsorship. Across the same period, the failure rate has not moved.
The clearest case study is the Lean Manufacturing transplant phenomenon of the 1990s and 2000s. Hundreds of major manufacturers across automotive, aerospace, electronics and pharmaceuticals sent executives to Toyota for benchmark studies. They hired consultants steeped in the Toyota Production System. They implemented kanban systems, established lean centers of excellence, certified internal practitioners and adopted the methodology with high fidelity.
The pattern documented across decades of subsequent research was consistent: implementations that adopted the visible methodology without the underlying structural commitments produced sustained results in roughly the same proportion as the broader transformation literature suggests. The visible tools transferred. The deeper conditions did not. The frameworks were correctly applied. The structural conditions for them to work were not.
The strongest predictor of whether a leader does the design work is whether the structure penalizes skipping it. Training and frameworks improved over the same decades. The rate did not move, because the structural incentives that produced the skipping behavior were never altered.
The path to moving the failure rate goes through structural change. The rest of this piece is about the mechanisms that shift leader behavior at scale, inside the same set of human pressures.
Why Stewardship Alone Is Not Enough
“The Stewardship Gap” argued that the four forces, Purpose, Commitment, Capability and Momentum, each need a stewardship function with a named owner. That argument holds. But naming a steward is not enough.
Stewardship without structural support produces the dynamic anyone who has sat in one of those roles will recognize: responsibility for the gap, authority over neither side.
This is the DevOps pattern at scale. A common adoption pattern for DevOps was to take what was meant as a cultural change and operationalize it as a third team inserted between Development and Operations. Dev kept the speed mandate. Ops kept the stability mandate. DevOps became the steward of the gap with no power to change behavior on either end of it. Both sides now had somewhere to send problems they did not want to own. The DevOps team absorbed the blame for failures caused by the relationship between Development and Operations, not by the team itself.
The same pattern shows up in Chief Transformation Officer roles, Program Management Offices asked to drive transformation across functions, Centers of Excellence responsible for adoption without authority over the functions adopting and product operations teams tasked with cross-functional coordination while reporting into one of the functions they are trying to coordinate.
Stewardship without structural authority is worse than no stewardship at all. It signals that the work is being addressed while ensuring that it cannot be, absorbing the political pressure that would otherwise force structural change. The breakpoint pattern continues, now with a designated absorber.
Naming a steward is the first step. The harder step is building the structure that makes stewardship rational to take, possible to execute and consequential when ignored.
Six Structural Mechanisms
The mechanisms below are not six tips. They are interventions in how the organization structures recognition, accountability and tenure around transformation work. The current system has a cost too: capital waste, organizational fatigue, missed opportunity and another post-mortem that names the execution problem while missing the design decision that made the failure predictable.
The first three change accountability. The second three strengthen organizational memory, commitment and design capacity. Any organization that adopts even three of them seriously will see the failure rate move.
Mechanisms That Change Accountability
1. Stewardship lines that survive sponsor turnover
Most stewardship roles report into the executive sponsor. When the sponsor moves, the steward loses the authority that made the role functional. The transformation continues nominally. The energy disappears.
The structural fix is to give stewardship roles a reporting line that does not collapse when the sponsor changes. In practice, this often means direct reporting to the CEO or COO rather than the functional sponsor, independent reporting on transformation health to the board separate from the sponsor’s status updates and a formal handoff protocol when the sponsor changes. The new sponsor has to either reaffirm or restructure the stewardship roles. They cannot quietly starve them.
In many enterprises, this configuration takes the form of an Office of Transformation reporting directly to the CEO or COO. The configuration only works if the office has actual decision authority over the transformation, not just monitoring authority. The most common failure pattern is to create one with weak political backing, which becomes a PMO under a different name. The reporting line is necessary. The authority that comes with it is what determines whether the steward can act on what they see.
2. Pre-committed stall protocols
Most transformations have no formal definition of stalled. The judgment is left to the sponsor, the program team or whoever is reading the status reports. Activity continues. The conditions for action are vague. Drift becomes recognizable only in retrospect.
Pre-committed stall protocols define, before launch, what specific signals indicate that the transformation is losing force and what specific action follows at each level of severity.
Early-stage drift, like sustained slippage in decision velocity beyond an agreed number of business days, triggers structural review of decision rights at the executive committee level. Mid-stage drift, like rollout adoption falling below an agreed percentage at the 90-day mark, triggers mandatory readiness assessment with the CEO and a redesign of the rollout approach. Severe drift, like quarterly milestone completion below an agreed percentage for two consecutive quarters, triggers escalation to the board with the possibility of program restructuring.
The tiering matters. Every signal does not need to go to the board, but every level of severity needs a defined response that the political weather of the moment cannot soften.
3. Compensation tied to multi-year transformation outcomes
Most senior executive compensation is structured around annual cycles. Major transformations produce results across 18 to 36 months. The mismatch is structural and produces the skip behavior described above.
A meaningful share of executive compensation, not a token slice, is tied to specific multi-year transformation outcomes. Transformation-tied compensation vests over the original time horizon, regardless of role changes. The leader is exposed to the consequence of their own design choices, even after moving into the next role internally.
This pattern is most visible in sales organizations, where compensation rewards the close while the cost of a bad close is paid in installments by customer success teams, implementation partners, product teams handling commitments they did not sign up for and the customer. Most enterprises do not restructure the misalignment because sales talent is mobile and will not accept pay at risk for outcomes that depend on functions outside their control. The result is a stable misalignment that everyone names and no one fixes. The same dynamic operates at the executive level for transformation work.
There are working examples of the structural change. Microsoft’s cloud transition under Satya Nadella included a restructuring of executive long-term incentive grants tied to multi-year cloud adoption outcomes, exposing senior leaders to the consequences of decisions that would unfold over years rather than quarters. Berkshire Hathaway has structured executive compensation around long-term outcomes for decades and Warren Buffett has written extensively about why most peer companies have not followed. These examples are notable precisely because they are exceptions.
A note on equity, which is technically multi-year. Equity ties executives to stock price, which is market perception, and under quarterly pressure can drift toward managing perception rather than producing the operational outcomes the transformation requires. The tie this mechanism describes is to specific transformation outcomes measurable independently of market perception: customer retention, operating efficiency, organizational adaptability.
This is the mechanism that most directly addresses the feedback gap. It is also the one most boards and executive committees resist, because it changes the relationship between executive authority and personal financial outcome. The resistance is the signal.
Mechanisms That Strengthen Memory, Commitment and Design Capacity
4. Hard-to-reverse architectural commitments at launch
Most transformations are launched with reversible commitments. The board approves a budget that can be cut. The sponsor announces a timeline that can be revised. The program structure can be reorganized. The reversibility is what makes incremental retreat possible. The retreat is the dominant failure mode.
Hard-to-reverse commitments at launch raise the political cost of incremental retreat: external commitments to customers tied to transformation milestones, public board commitments with named accountability, contractual dependencies that make alternative paths visibly expensive and architectural decisions that lock in the transformation’s structural premises before the political pressure has time to soften them.
Amazon’s 2006 commitment to launch AWS as a public business is a working example. The customer-facing service contracts, the public pricing commitments and the technical investment levels could not be quietly walked back. The structural commitment made retreat costly enough that the organization continued forward through periods when the business case was not yet proven.
The contrasting pattern is IBM’s repeated reversibility around cloud strategy across multiple CEO transitions, which produced the corresponding reversibility of organizational commitment. The technology was comparable. The structural commitment was not. The resulting market position differed by an order of magnitude.
When retreat is structurally easier than continuation, organizations retreat.
5. Post-mortem discipline that names the skipped design decision
Most transformation post-mortems identify execution issues. The timeline was aggressive. Change management was insufficient. Organizational readiness was misjudged. These findings reach the program team and the consulting firm. They do not reach the design layer.
A disciplined post-mortem identifies not only what went wrong in execution, but what design decision at launch made the failure predictable. The findings reach the executive who made or skipped that decision. The pattern is documented. The next launch is required to address it.
Without this, the same skipped design decision produces the same breakpoint at the next transformation. This requires post-mortem authority that does not report into the leadership that authored the decisions being reviewed. Most organizations do not have this. Building it is the work.
6. A standing organizational design function
Organizational design is treated in most enterprises as a special-purpose activity. It happens during reorganizations. It happens during M&A integrations. It happens when a transformation is announced. It does not happen as continuous work owned by a function whose career depends on doing it well.
A standing organizational design function exists to do the work between transformations. It maintains the operating model. It surfaces structural friction before it becomes a transformation breakpoint. It has the authority to recommend structural changes outside the cycle of major announcements. It is staffed by people whose careers are advanced by structural quality, not by the success of any single initiative.
It exists to map actual work flow against formal process and identify structural friction across functional boundaries. It needs explicit mandate to recommend cross-functional changes, reporting authority to the CEO and political standing to challenge senior leaders who would otherwise prefer to keep their functional structures intact. It should be measured on structural improvement outcomes, not project completion.
The function should avoid becoming what many strategy and operations groups become in practice: a delivery arm for leadership-defined initiatives without the mandate or standing to challenge senior leaders. Over time, that kind of function comes to accommodate existing silos rather than address them, accumulating the dysfunction it was meant to prevent.
What This Changes
The six mechanisms have a common structure. Each one shifts the rational response to a transformation moment. The steward with structural authority acts on what they see. The leader whose compensation is tied to multi-year outcomes invests in design before launch. The team that knows the post-mortem will trace failures to design decisions stops skipping them. The board that has to undo a public commitment to retreat thinks harder before retreating.
Build these mechanisms into the system and the failure starts landing at the design layer where it originated. Leaders make different choices. Not because they have become better leaders, but because they are rational leaders operating inside a different structure.
The Honest Trade
Implementing the six mechanisms is not free. Boards lose some flexibility. Executives lose some upside optionality. The organization commits to a longer accountability horizon than the typical political cycle inside the company.
There are real reasons most enterprises have not adopted these structures. They are tradeoffs that historically went the other way. The argument of this piece is that the tradeoff has become harder to defend. The 70 percent failure rate is not an anomaly. It is the equilibrium produced by the current design. The cost of that failure rate, in capital, in opportunity, in organizational fatigue and in the credibility of leadership itself, is large and growing. Doing the structural work to move it costs less than the current arrangement does.
I have watched leaders see this clearly and still reach for the soft alternative because the structure rewarded it. The mechanisms above do not require those leaders to behave differently. They change the structure those leaders are operating inside.
The leaders who do this work first will operate inside a structurally different organization than their peers. They will be the ones building the cases that other leaders eventually point to as proof that the failure rate can move. For everyone else, the post-mortem pattern at the opening of this piece keeps repeating and the number keeps holding.
That raises the question for the next piece: what happens when AI enters organizations that were already designed to skip the work that transformation requires?
Citations
McKinsey & Company, multiple studies on transformation success rates published since 2009, with the most recent figures in The State of Organizations 2026, published February 19, 2026. The 70 percent figure has been independently corroborated in published research from BCG, KPMG and Bain across the same period.
Senior executive tenure data: a composite estimate drawing on Korn Ferry, Spencer Stuart and Crist|Kolder annual studies of CEO and C-suite tenure, most recent editions, 2024 to 2026. Average tenure has been declining across most C-suite roles for the past decade.
Lean Manufacturing implementation outcomes: see Liker, J., The Toyota Way, McGraw-Hill, 2004, for the original methodology framing, and Hines, P., Holweg, M. and Rich, N., “Learning to evolve: A review of contemporary lean thinking,” International Journal of Operations & Production Management, 2004, and subsequent literature for documentation of implementation failure rates and the structural conditions that distinguished successful from failed transplants.
Microsoft cloud transition compensation restructuring: documented in Microsoft proxy statements 2014 to 2020 and analyzed in Eichenwald, K., “How Microsoft Lost Its Mojo,” Vanity Fair, 2012; and Nadella, S., Hit Refresh, HarperBusiness, 2017.
Berkshire Hathaway compensation philosophy: see annual letters to shareholders, particularly Buffett, W., 2005 and 2017 letters, on the structural problems with conventional executive compensation.
AWS launch and structural commitment: documented in Stone, B., The Everything Store, Little, Brown, 2013, and Amazon Unbound, Simon & Schuster, 2021, and corroborated in Amazon shareholder letters from 2006 onward. IBM cloud strategy reversibility documented in IBM annual reports and analyst coverage across CEO transitions.