Crank Labs Book a 15-min call

Transformation, 10 min read, by the Crank Labs team,

Why Transformation Projects Fail, and How to Make Change Stick

Why transformation projects fail: seven failure modes with their early symptoms and fixes, how to make change stick, and a pre-mortem checklist to use first.

The short answer

Transformation projects fail for predictable reasons, not bad luck: advice and build split across different firms, a first scope that is too big, no single owner, measuring activity instead of outcomes, ignoring the people who do the work, data that is not ready, and no run phase after go-live. Each has early symptoms you can spot and a practical fix you can apply before the money is spent.

If you want to understand why transformation projects fail, do not look at the plan. Look at what happens between the plan and the third month after go-live. That is where almost every failed programme comes apart, and it comes apart for the same few reasons in a 50-person clinic group as in a 400-person manufacturer. The good news is that each failure mode has symptoms you can spot early and a fix you can apply before the money is spent. This guide sets out the seven we see most often, how to recognise each one, how to fix it, and a pre-mortem checklist to run before you start.

Why do transformation projects fail? The short answer

Transformation projects rarely fail because the idea was wrong. They fail because of how the work was set up: who designs it, who builds it, who owns it, what gets measured and what happens after launch. Here are the seven failure modes at a glance.

Failure modeEarly symptomFix
1. Advice and build split across firmsThe build team asks questions the strategy deck never answeredOne team, or one accountable lead, from diagnosis to run
2. Starting too bigThe first measurable result is more than a quarter awayOne function, one metric, a first result in weeks
3. No ownerA steering committee, but no single name on the outcomeA named process owner with real authority
4. Measuring activity, not outcomesStatus reports count workshops and features shippedA baseline and an outcome metric agreed before work starts
5. Ignoring the front lineStaff first see the change at trainingInvolve them in diagnosis, design and testing
6. Data not readyThe new reports are wrong on day oneData clean-up scoped as its own workstream before build
7. No run phaseThe project closes at go-liveA funded, staffed run phase of measuring, tuning and training

The seven failure modes, with symptoms and fixes

1. Advice and build are split across firms

The classic pattern: a consulting firm diagnoses the business, designs the future state, writes a roadmap and leaves. A separate IT vendor or development agency receives the roadmap and builds. At that hand-off, most of the context disappears: the reasons behind decisions, the exceptions that came up in interviews, the constraints nobody wrote down. The builder builds what the document says, which is not quite what the business needs, and each side blames the other.

2. Starting too big

Big-bang programmes try to change everything at once: a new ERP, a new CRM, a new structure, every function, one go-live date. They take a long time, the business changes while they run, and people lose faith before any value arrives. By the time the system launches, the requirements are out of date.

3. No owner

Steering committees do not own outcomes. When a transformation belongs to everyone, it belongs to no one. IT owns the system, the consultants own the plan, the vendor owns the go-live, and nobody owns whether the function actually performs better.

4. Measuring activity, not outcomes

A surprising number of programmes report green status every week while the business carries on exactly as before. That happens when the project measures its own effort rather than its effect on the business.

5. Ignoring the front line

The people who answer the phones, raise the invoices and run the shop floor know where the exceptions are. When they are left out, the design misses the exceptions, the system cannot handle real work, and staff build workarounds. What gets labelled as resistance to change is often a perfectly rational response to a system that makes their day harder.

6. Data not ready

Duplicate customers, the same product under three codes, missing fields and stock figures nobody trusts. Load that into a new system and it shows wrong numbers on the first day. People conclude the system is broken and return to the spreadsheet they trust.

7. No run phase

Go-live is the start of the change, not the end. Without someone measuring, tuning and training in the months that follow, the new process decays. New joiners learn the old habits from colleagues, exceptions get handled outside the system, small bugs never get fixed, and within a year the business is back where it started with an expensive system on top.

Why does digital transformation fail when it starts with software?

Most stories about why digital transformation fails are a special case of the seven modes above. A business buys a platform before it has designed the process the platform should run. The software then encodes the old way of working, usually including its delays, and nobody owns the outcome because the project was framed as a system implementation. The fix is to reverse the order: diagnose, redesign, then choose and build the technology. We explain the difference in more depth in digital transformation vs business transformation.

How do you make change stick in a mid-sized business?

In a company of 20 to 500 people, change management is not a communications plan or a slogan. It is a handful of practical habits that make the new way of working the easiest one to follow.

Pre-mortem checklist: run this before you start

A pre-mortem asks the leadership team to imagine that it is a year from now and the transformation has failed, then to list the reasons why. It surfaces risks that nobody wants to raise in a kick-off meeting. Follow it with this checklist. Every unticked item is a risk you are choosing to accept.

How do you rescue a transformation that is already stalling?

If you are reading this halfway through a programme that is not delivering, the steps are the same, applied in reverse order of urgency.

  1. Stop adding scope. Freeze new requirements until something is working.
  2. Re-baseline. Agree which business number the programme was meant to move, and where it is today.
  3. Name the owner. If there is no single accountable person for the function, appoint one this week.
  4. Spend a day with the front line. List every workaround, duplicate spreadsheet and manual step people still rely on.
  5. Pick the part closest to working and finish it. Fix the main issues, retrain, switch off the old way and measure.
  6. Then decide the rest. With one function working and measured, you can make an honest call on what to continue, change or stop.

What should you do next?

Run the pre-mortem checklist against your current or planned project and be honest about the gaps. If more than a couple are open, fix them before you commit more budget. Our business transformation framework lays out the seven steps that avoid most of these failure modes by design.

If you want help, Crank Labs runs business transformation as one team from diagnosis through build to the run phase, and our consulting and strategy work starts with a free working session that maps where time and money leak. Book a 15-minute call to set one up.

Frequently asked questions

Is resistance to change the main reason transformations fail?

Resistance is usually a symptom rather than the cause. Staff push back when a new process makes their day harder, misses the exceptions they deal with, or arrives without explanation. Involving the front line in the design, training on real work and fixing their complaints quickly removes most of it. If resistance persists after that, it often points to a design problem worth investigating.

How long should the run phase last after go-live?

Long enough for the outcome metric to improve and hold for several consecutive weeks, and for new joiners to be trained into the new process rather than the old one. For a focused workflow that is often a few months. The run phase should end with a clear handover to the process owner, not simply when the budget runs out.

Should we run a transformation in-house or bring in outside help?

In-house works when you have a leader with time to own it and people who can both redesign processes and build systems. Most mid-sized businesses have one but not the other. Outside help is useful when it covers the gap without creating a new hand-off, so look for a partner that will stay through build and rollout rather than leave after the plan.

What should we do if the software vendor blames our process?

They may be right. Software implementations often stall because the process was never designed, only configured. Ask the vendor to name the specific process decisions that are blocking them, then assign each one to your process owner with a deadline. If nobody on your side can make those decisions, that is the real gap to fix before spending more on the software.

How do we know early whether a transformation is working?

Watch two numbers from the first week after go-live: the outcome metric you set a baseline for, and an adoption measure such as the share of work going through the new system instead of the old one. A short dip followed by steady improvement is normal. Flat numbers after a month mean something in the design or the rollout needs fixing.

Book a callWhatsApp