Dr. LaTonya Applewhite – The Change Management Statistic Costing Companies Real Money
New York, NY, USA – August 27, 2026 – Every year, companies commit enormous sums to restructuring, systems migrations, post-merger integration and operating model redesign. Those programmes are among the largest discretionary expenses on a corporate budget, and they are routinely justified, governed and abandoned on the basis of a single statistic.
Seventy percent of change initiatives fail. It appears in consulting proposals, board papers and investor presentations. It has no empirical foundation.
Where the number came from
Mark Hughes examined the claim in a peer-reviewed paper, “Do 70 Percent of All Organizational Change Initiatives Really Fail?”, published in the Journal of Change Management in December 2011. He followed the citation trail and found the figure was repeated everywhere and sourced nowhere. There was no underlying study.
The likely origin is a hedged line in Hammer and Champy’s 1993 work on reengineering, estimating that as many as 50 to 70 percent of organisations undertaking a reengineering effort did not achieve the dramatic results they intended. It was presented as an impression, not a finding. Michael Hammer later stated plainly, in 1995, that there is no inherent success or failure rate for reengineering.
What converted an impression into a hard number was commercial repetition. A high failure rate supports a specific conclusion: that organisations should not attempt significant change without external help. Firms with an interest in that conclusion published the figure, cited each other, and the circular referencing eventually gave it the appearance of evidence.
Why this costs money
A statistic that shapes expectations shapes behaviour, and in capital terms the effects are measurable.
Programmes get over-governed. A change initiative framed as a 70 percent risk attracts heavy oversight, extended approval chains and defensive reporting. That governance carries direct cost and slows the work it is supposed to protect.
Failures stop being investigated. If most change fails, a failed programme is unremarkable rather than a signal that something specific went wrong. The organisation books the write-off and moves on without learning what it did badly, which guarantees the next attempt repeats it.
Capital gets allocated to the wrong remedy. The figure was popularised to sell advisory support. That is sometimes the right purchase. Treating it as universally necessary is how organisations spend on external programme management when the actual constraint was an unclear decision right or a process nobody had mapped.
Momentum is abandoned early. Teams that expect failure withdraw at the first difficulty, and leadership reads the withdrawal as confirmation. The prophecy closes.
What the evidence actually supports
There is no credible aggregate failure rate for organisational change, and there probably cannot be one. A systems migration, a merger integration and a culture programme are not comparable events, and pooling them produces a number that describes nothing.
What can be examined is why a specific initiative held or did not. Across executive, operational and educational settings, the same four conditions separate programmes that survive from those that quietly stop:
- The problem was defined by the people who have it. Initiatives specified in a leadership session, working from dashboards, consistently underperform ones shaped by the teams doing the work.
- The new method is genuinely easier for at least one influential group. If every party loses time, adoption fails on arithmetic regardless of communication quality.
- A named individual holds decision authority. Steering committees that meet monthly and cannot decide between meetings are a common structural cause of drift.
- Something visible is removed. Programmes that only add processes are rejected by the people expected to absorb them.
None of that is expensive to apply. It is considerably cheaper than the governance apparatus organisations build when they assume failure is the base case.
Resistance is usually information
The most costly misreading in change management is treating objection as obstruction. When frontline teams push back on a new process, leadership frequently interprets it as reluctance and responds with more communication.
In practice the objection is often accurate. The people closest to the work can see why a design will not survive contact with reality, and they usually saw it before the launch date was fixed. Organisations that treat that feedback as data rather than as friction avoid the rework, and rework is where change budgets are actually consumed.
The practical takeaway
When the 70 percent figure appears in a proposal, ask for the source. The answer will indicate whether the analysis underneath it was performed or assumed. If the number was assumed, the recommendations resting on it deserve the same scrutiny before capital is committed.
Organisational change is genuinely difficult. It does not require an invented statistic to make that case, and the reasons it fails are specific, identifiable and fixable, which is far more actionable than being told that failure is statistically normal.
AUTHOR BIO BLOCK
Dr. LaTonya Applewhite is an executive leader with more than 20 years of experience in human resources, talent development, operations and organisational transformation. She has led workforce planning, leadership development, change management and employee engagement initiatives across executive, operational and educational organisations.
Media Contact
Company Name: CB Herald
Contact Person: Ray
Email: Send Email
Country: United States
Website: cbherald.com
