Framework
The Striviz Framework What is Change Management? Why Change Fails
Certification
Programme Overview Pricing FAQs Change Management Careers
Services
ERP & Systems Digital Transformation M&A Integration AI Adoption Government & Public Sector
Locations
All Locations Australia New Zealand Asia United States Canada Europe Middle East
Insights
Blog Glossary Templates & Downloads
Company
About Striviz Sustainability Careers Contact Apply Now →

Why 70% of change programmes fail — and what the other 30% do differently.

Most change initiatives don't fail because of bad technology or bad strategy. They fail because of how people were brought along — or weren't.

Research has consistently found that around 70% of change initiatives fail to fully achieve their intended outcomes. The reasons are almost always the same — and almost always avoidable. Here are the seven most common failure modes, and what high-performing organisations do instead.

1

Weak or absent sponsorship

The single biggest predictor of change failure. When the most senior sponsor of a change programme is not actively and visibly engaged — attending key sessions, communicating personally with staff, removing blockers — the programme loses credibility and momentum at every level of the organisation. What the 30% do: They secure genuine, active sponsorship before the programme is announced, not after it starts to stall.

2

Change management bolted on at the end

The most common structural failure: treating change management as a communication exercise to be delivered two weeks before go-live. By this point, the decisions that matter have already been made, resistance has already formed, and there's no time to address the real concerns. What the 30% do: They engage change management from the start — in the same room as the project team, from the first planning meeting.

3

Treating communication as broadcast

Many organisations confuse communication with information. Sending all-staff emails, posting on intranets, and running town halls is broadcasting. It informs, but it does not engage. People change when they feel heard, not just informed. What the 30% do: They build two-way feedback mechanisms into the plan from the start — and actually use the input to change the approach.

4

Underestimating middle managers

Middle managers are the most important audience in any change programme — and the most frequently neglected. They're the ones who answer the questions, model the behaviours and set the tone for their teams. When they're not on board, the change doesn't happen regardless of what leadership says. What the 30% do: They run dedicated manager enablement programmes alongside the main change effort.

5

No measurement of adoption

Most programmes measure outputs (training attendance, communication reach, milestone completion) rather than outcomes (actual behaviour change, system usage, process adherence). The result is a programme that looks successful on paper while the change quietly fails on the ground. What the 30% do: They define adoption metrics before the programme starts and track them through and after implementation.

6

Declaring victory at go-live

Go-live is the beginning of adoption, not the end of change. When teams pack up and move on at launch, old habits typically reassert themselves over the following weeks and months. The investment in change is wasted if reinforcement doesn't follow through. What the 30% do: They plan the post-go-live reinforcement programme before the programme launches — not after.

7

Change saturation and fatigue

In most organisations, change is not a single event — it's continuous. When people are already managing multiple changes simultaneously, adding another one without accounting for capacity overwhelms even the most change-capable teams. What the 30% do: They assess the change portfolio and sequence or pace change deliberately, rather than launching programmes based purely on project timelines.

Want to be in the 30%?

The Striviz certification teaches the Striviz Framework — a practical, applied framework for avoiding every one of these failure modes.

Explore Certification →