Why Change Fails · Series Overview
Why Change Fails
Six papers. One argument.
Why organizational transformation fails — and what it takes to make change hold.
Brandon Freitag · workthatholds.com · 2026
Why Change Fails · The Problem
Seventy percent of organizational transformations fail.
That number has been consistent across McKinsey, BCG, KPMG, and Bain for over fifteen years.
It is not a coincidence. It is not bad luck. It is not a knowledge gap — leaders know what transformation requires. The 70 percent failure rate is the equilibrium produced by the current design of how organizations launch, staff, and sustain change. This series is about that design.
~70%
Transformation failure rate — consistent across McKinsey, BCG, KPMG, Bain for 15+ years
Why Change Fails · The Argument
The argument runs in three movements.
Diagnose
What goes wrong, and why
Five breakpoints appear in every failed transformation. Beneath them are four forces. Each force requires stewardship. Papers 1 & 2.
Explain
Why it keeps happening
Skipping the design work is individually rational. AI accelerates what was already broken. The structural environment rewards the wrong things. Papers 3 & 4.
Act
What actually changes it
Seven disciplines before the launch. And the operating system beneath all of it: what the leader actually believes about people. Papers 5 & 6.
Why Change Fails · Six Papers
Six papers. A complete arc.
Paper 1
Five Breakpoints Leaders Miss
The five places where transformations predictably fail — and the four forces beneath each one.
Paper 2
The Stewardship Gap
Why transformations keep losing force after leaders have already named the problem.
Paper 3
Designed to Stall
Why the system rewards the choices that cause transformation to fail — and six mechanisms that change the structure.
Paper 4
The AI Mirror
Agentic AI compresses the timeline and tells the truth about what was already broken.
Paper 5
Before It Breaks
Seven disciplines. Three phases. What leaders who get transformation right do before anyone is watching.
Paper 6
The Leader the Work Requires
The operating system beneath everything — what the leader believes about people, and whether they act on it under pressure.
Why Change Fails · Paper 1
Five breakpoints.
All of them structural.
01
Strategic Disconnection
Looks like alignment. Leaders leave the kickoff nodding. Six months later, diverged.
02
Incentive Fragmentation
The most dangerous resistance looks like support until the real tradeoffs arrive.
03
Process Friction
Skilled people working inside broken handoffs. Strategy negotiated, not executed.
04
Technology Illusion
Leaders buy a tool and mistake the tool for the system.
05
Momentum Mirage
Activity continues. Progress does not. No one is watching for drift.
Why Change Fails · Paper 1 & 2
Beneath the breakpoints are four forces that must be actively maintained.
Force 1
Purpose
Shared definition of success — specific enough to fail.
Force 2
Commitment
The designed priority that holds when tradeoffs appear.
Force 3
Capability
Organizational machinery — how work moves, where decisions live.
Force 4
Momentum
The ability to convert progress into confidence and confidence into continued action.
Each force requires stewardship. Most transformations launch with all four forces intact. They fail because no one is responsible for sustaining them when operating pressure arrives.
Why Change Fails · Paper 2
The complete map.
| Breakpoint | Force at Risk | Stewardship Needed | What It Looks Like |
|---|
| Strategic Disconnection | Purpose | Interpretation | Translating enterprise outcomes into team-level success definitions, continuously |
| Incentive Fragmentation | Commitment | Ownership | Named decision rights; incentive conflicts resolved before the announcement |
| Process Friction | Capability | Architecture | Owning how work moves across boundaries — the space between functions |
| Technology Illusion | Capability | Architecture | Readiness before deployment — process, strategy, and capability |
| Momentum Mirage | Momentum | Reinforcement | Named owner; written stall definition; authority to intervene |
Why Change Fails · Paper 3
Skipping the design work
is individually rational.
Skill Gravity
Leaders do what they're expert at
Customer engagement, operational firefighting. Organizational design is slow, structural, produces no short-term signal anyone tracks.
The Feedback Gap
Consequences arrive after they've left
Average C-suite tenure: 4 years. Design failures visible in 18–36 months. The leader who skips the work is rarely in the role when the transformation stalls.
Career Calculus
Real transformation is visible risk
Political conflict, short-term disruption, association with failure. Softer alternatives manage the pressure without creating the conflict.
The strongest predictor of whether a leader does the design work is whether the structure penalizes skipping it — not whether they understand it.
Why Change Fails · Paper 4
AI doesn't change the core dynamic.
It compresses the timeline.
AI absorbs routing. It does not absorb stewardship.
What AI exposes
The diagnostic function
A vague strategic direction that took six months to surface in human execution can surface in six days in agentic execution. AI tells the truth about the organization around it.
The missed distinction
Routing vs. stewardship
When organizations eliminate management layers without explicitly reassigning stewardship, the four forces lose their carriers. The breakpoints don't disappear — they accelerate.
Organizations whose four forces were already stewarded absorb AI more effectively. Organizations whose forces were not stewarded discover the gaps faster than they expected.
Why Change Fails · Paper 5
Seven disciplines.
Three phases. Before anyone is watching.
Phase 1 — Anchor
What is true
1. Define the outcome specific enough to fail.
2. Resolve incentive conflicts before the announcement.
Phase 2 — Build
The machinery
3. Redesign the delivery system before you ask it to carry new work.
4. Test organizational readiness before you deploy the technology.
Phase 3 — Sustain
What holds
5. Build the momentum system before you need it.
6. Sequence for value inside 90 days.
7. Design for adoption, not announcement.
Why Change Fails · Paper 6
Beneath everything in this series
is one prior question.
Do you believe that people fundamentally want to contribute — and that they underperform primarily when the system fails them?
Or do you believe that people need to be managed into performance through accountability and consequences? These two positions produce different organizations. They use the same levers to entirely different effect. Every framework in this series only holds in hands that have answered this question honestly.
Theory X vs. Y
McGregor, 1960. The labels became shorthand. The underlying distinction has not become less important.
Why Change Fails · Paper 6
Beliefs are necessary.
They are not sufficient.
Test 1
Absorb the cost under pressure
Culture is built in the moments when a value is tested by something real — not in normal conditions. Every exception teaches the organization the actual terms of the value.
Test 2
Say the uncomfortable thing first
Leaders who manage perception upward while expecting transparency downward don't get transparency. They get very polished reporting.
Test 3
Promote the person who told you the truth
Every promotion tells the organization what behavior leads forward — more powerfully than any stated value or leadership principle.
Why Change Fails · Diagnostic
Eight questions before the launch.
- Have you defined the outcome in terms specific enough to be proven wrong — in language every leader describes the same way?
- Have you mapped every leader with veto power and resolved incentive conflicts before the announcement?
- Have you redesigned the handoffs the new work will depend on before it lands on top of them?
- Have you tested organizational readiness across strategy, process, and capability — before procurement?
- Have you named the momentum owner and written the stall definition before anyone needs to interpret it under pressure?
- Have you committed to a real, visible, financially meaningful result inside the first 90 days?
- Have you identified the first cohort and designed the opening phase to produce results with them — not announce to everyone?
- Have you confirmed you have the standing to do this work, or is the first task renegotiating the role itself?
Why Change Fails · The Full Argument
The 70 percent rate is not an anomaly.
It is the equilibrium.
Doing the structural work to move it costs less than the current arrangement does.
What the series shows
The structure produced this
Launches get rewarded. Sustainment doesn't. Accountability diffuses by the time consequences arrive. AI accelerates what was already there. The same breakpoints reappear in the next transformation.
What changes it
Structure, not exhortation
Stewardship lines that survive sponsor turnover. Pre-committed stall protocols. Compensation tied to multi-year outcomes. Post-mortem discipline that names the skipped design decision. And the leader who believes people are the asset.
The work
that holds.
Read the full series at workthatholds.com
workthatholds.com · brandonfreitag.com