Why the system keeps rewarding the choices that cause transformation to fail.
Brandon Freitag · workthatholds.com · May 2026
It is a structural feature of how leadership accountability works in modern enterprises.
Skipping the design work is individually rational. Telling leaders to be different leaders has been the field's response for decades. It has not moved the number. Moving the number requires changing the system, not just the people inside it.
"The program director is replaced. The consulting firm is blamed. The VP who agreed to the scope has been promoted."
Accountability lands one or two levels below the actual decision point. 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. The same five breakpoints reappear in the next transformation.
These activities produce visible results quickly and feel like leading.
Organizational design is structural, slow, produces no short-term signal anyone tracks, and requires political confrontation with peers. The layer that should own design 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.
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 it likely remain largely unexamined. No corrective feedback loop. Same choices made again by the same kind of leader in the same kind of role.
Political conflict, short-term disruption, the possibility of being associated with a failed initiative.
Softer alternatives manage the pressure without creating the conflict: 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. Each is individually rational. Together they produce the 70 percent.
The Lean Manufacturing case: hundreds of manufacturers sent executives to Toyota. The frameworks transferred. The structural conditions did not.
Implementations that adopted the visible methodology without the underlying structural commitments produced sustained results in roughly the same proportion as the broader transformation literature. Training and frameworks improved across the same decades. The rate did not move.
The strongest predictor of whether a leader does the design work is whether the structure penalizes skipping it. Not whether they understand it.
The DevOps pattern: responsibility for the gap, authority over neither side.
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. Both sides had somewhere to send problems they didn't want to own. The DevOps team absorbed the blame for failures caused by the relationship between Dev and Ops.
It signals the work is being addressed while ensuring it cannot be. It absorbs the political pressure that would otherwise force structural change.
The mismatch is structural: executive compensation on annual cycles; transformation results across 18–36 months.
A meaningful share of compensation tied to specific multi-year transformation outcomes, vesting over the original time horizon regardless of role changes. Working example: Microsoft's cloud transition under Nadella — executive long-term incentive grants tied to multi-year cloud adoption outcomes. The mechanism makes the design work rational to invest in before launch.
Most transformations are launched with reversible commitments. Reversibility makes incremental retreat the path of least resistance.
Each mechanism shifts the rational response to a transformation moment.
Implementing the six mechanisms is not free. Boards lose flexibility. Executives lose upside optionality.
The argument: 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. Doing the structural work to move it costs less than the current arrangement does.
None of these require heroic leadership. They make the design work the rational path for leaders responding to their actual incentives.
workthatholds.com · brandonfreitag.com