The Transformation Stall Test: Seven Signs Your Change Programme Has Lost Momentum

Eleven months into a transformation, the steering pack is usually still green. The programme office meets every Tuesday. Workstream leads report milestones met. And the management accounts look much as they did the month before the programme began.

That gap between reported activity and banked value is how most transformations disappoint. Very few are cancelled. They slow, lose their best people to the day job, and settle into a permanent state of being "in progress" until someone quietly stops asking about them.

The research on this is consistent and not encouraging. BCG estimates that about 70 per cent of transformations fall short of their objectives. McKinsey has found that successful programmes deliver most of their value early, 57 per cent within six months and 74 per cent within the first year, and that performance discipline often fades after year one as budgets and incentives drift back to the old priorities.

If the value has not started to arrive by month nine or twelve, the honest working assumption is that the programme has stalled.

This article sets out a test that a leadership team can run in an hour. It covers seven signals, how to score them, how to read what kind of stall you have, and a 30-day reset for programmes that need one.

Green on the tracker, flat in the accounts

Programme trackers measure what is easy to measure: tasks completed, workshops held, systems configured, people trained. All of that is necessary. None of it is the outcome.

A stalled programme often looks healthy on paper for a long time. Each workstream is making progress against its own plan, so each status is defensible. The problem only shows when you ask a different question: what has changed in how the business performs, and can the finance team see it?

In SMEs and mid-market businesses the problem is sharper. The transformation is usually run by the same small group who run the company. There is rarely an independent value-tracking function. The CEO hears about progress from the people delivering it, and they are, understandably, optimistic.

Who should run the test

Run it with the full leadership team, plus the finance lead and two or three managers one level below the executive. Do not leave it to the programme office alone. The people closest to the plan are the least well placed to see that it has stalled.

Ask each person to score the seven signals independently before the meeting. Then compare. Wide disagreement between scorers is itself a finding. If the CEO scores the programme as healthy and the operations managers score it as stalled, you have learned something about the programme and about how information reaches the top.

The seven signals

Score each signal 0, 1 or 2. Zero means there is no sign of the problem. One means a warning. Two means the signal is clearly present.

Signal 1: The portfolio has grown since launch

Programmes tend to accumulate work. A cost programme picks up a systems project. A growth programme adds a rebrand. Each addition is reasonable on its own, and together they spread the same people across more initiatives than they can finish.

BCG's research suggests companies can often capture around 80 per cent of a transformation's value from roughly 20 per cent of its initiatives. It also names the reasons leaders struggle to cut: everything feels urgent, past investment feels hard to abandon, and stopping someone's project feels personal.

The test: Count the live initiatives today and compare with the number at launch. Then ask each member of the leadership team to name, without notes, the five initiatives that will deliver most of the value.

• 0: The portfolio is the same size or smaller, and the team names the same top five.
• 1: The portfolio has grown, or the team's top fives differ.
• 2: The portfolio has grown by more than a quarter, and nobody can confidently name the top five.

First repair: Rank every initiative by expected value and by the scarce people it consumes. Pause or stop the bottom half. Write the decision down and tell the organisation what has stopped.

Signal 2: Milestones are green but the P&L is not moving

This is the most important signal and the one most often hidden. Status reports measure delivery against plan. The business case measured change in revenue, margin, cash or cost. Somewhere between the two, the link has been lost.

The test: Take the benefits the programme claims to have delivered so far. Ask the finance lead how much of that figure they can see in the management accounts, against a baseline agreed before the work started.

• 0: Most claimed benefits are visible in the accounts and signed off by finance.
• 1: Some benefits are visible, but much of the reported figure is forecast, gross or unverified.
• 2: Finance cannot trace the reported benefits to the accounts, or there was no agreed baseline.

First repair: Rebase the benefits case with finance. Separate banked value from forecast value, and gross savings from net. Report only banked value to the board from now on, with the forecast shown separately. Our AI Investment Ledger sets out the same discipline for AI spend, and the rules transfer directly.

Signal 3: Nothing has been stopped

Change is almost always added on top of existing work. The new process runs alongside the old one. The new report is produced as well as the old one. The weekly meeting stays in the diary after its purpose has gone.

Deloitte's 2026 UK findings show the cost: 57 per cent of UK workers say organisational change has increased their workload, and 76 per cent say their wellbeing has suffered from too many changes. People who are overloaded protect the day job first, and the programme loses.

The test: Ask for a list of things the business has formally stopped doing since the programme began: reports, meetings, approvals, legacy processes, products or customer commitments.

• 0: There is a written stop list and it is being enforced.
• 1: Some things have stopped informally, but there is no list and old work keeps returning.
• 2: Nobody can point to anything that has stopped.

First repair: Each leadership team member names three pieces of recurring work in their area to stop within 30 days. The CEO approves the list and announces it. Our Operations & Efficiency work often starts with exactly this list.

Signal 4: Middle managers cannot describe the new way of working

Senior leaders usually understand what the programme is for. The managers who must run the new process every day often understand what has changed, but not how they are supposed to work now: which decisions are theirs, which handoffs have moved, what good looks like on a Tuesday afternoon.

Bain's 2026 research found that more than 80 per cent of leaders believed they supported the people most affected by a reorganisation well, while only 57 per cent of middle managers agreed. We covered that gap in detail in The 52-Point Gap. In a stalled programme it tends to show up as managers quietly reverting to the old way.

The test: Ask five managers, separately, to describe one workflow that should now work differently. Ask what they personally do differently, and what they have stopped doing.

• 0: At least four give a specific, consistent answer.
• 1: Answers are general or inconsistent.
• 2: Most managers describe the programme in leadership language but cannot name a change in their own working week.

First repair: Pick the two workflows that matter most to value. Run working sessions with the managers who own them to redesign the steps, decision rights and handoffs in detail. Then give them the authority to run the new version.

Signal 5: Decisions wait for the steering meeting

A healthy programme makes decisions quickly. A stalled one parks them. Issues are "taken offline", escalated to the next steering meeting, or sent back for more analysis. Meanwhile teams wait, or work around the gap.

The test: Look at the last three months of programme decisions. How many were deferred at least twice? How long does a typical escalation take to resolve? How often does the CEO, or the named sponsor, actually attend?

• 0: Most decisions are made within a week, and the sponsor attends consistently.
• 1: Several decisions have been deferred more than once, or attendance has slipped.
• 2: There is a backlog of deferred decisions, and senior attendance has visibly fallen.

First repair: Clear the backlog in a single session. Agree in writing which decisions workstream leads can make without escalation. Our Execution Contract for Leadership Teams gives a format for making those commitments visible.

Signal 6: The budget and incentives still pay for the old model

McKinsey's research points to a specific failure after the first year: incentives and budgets fall out of line with the programme's objectives. Next year's budget is built on last year's cost base. Bonuses reward the old measures. Managers are asked to deliver change while being paid to hold the line.

The test: Look at next year's draft budget and the current bonus scheme. Are the programme's benefits already built into the budget? Do the targets of the people responsible for delivery include programme outcomes?

• 0: Benefits are in the budget, and incentives for the key owners include them.
• 1: One of the two is aligned, but not both.
• 2: Neither the budget nor the incentives reflect the programme.

First repair: Build the banked and committed benefits into next year's budget, owned by named line managers rather than the programme office. Adjust at least the leadership team's targets to include programme outcomes.

Signal 7: Nobody outside the leadership team can name a win

People believe a change is working when they see it working. BCG's latest research on momentum, published last week, recommends that leaders show belief, promote wins, set new challenges for teams that are ahead and give struggling teams a fresh start. A programme that has gone quiet loses support even if it is quietly making progress.

The test: Ask ten people below management level, in different teams, to name one thing the programme has improved.

• 0: Most can name something specific.
• 1: A few can, but the answers are vague.
• 2: Most cannot name anything, or the answers are cynical.

First repair: Find two or three real, verified wins. Have the people who delivered them explain them at the next all-staff meeting, in their own words. Do not claim wins that finance has not seen.

Read the pattern, then the total

The total score matters less than the pattern. Signals tend to cluster, and each cluster points to a different cause.

A leadership stall often sits behind the others. If signal 5 scores 2, deal with it first, because none of the other repairs will hold without decisions being made.

Then use the total score as a guide to how much intervention you need.

These bands are our working guide rather than a benchmark from published research. Use them to prompt a decision.

A 30-day reset

A reset is a short, deliberate interruption, and it should come with fewer slides than the launch did. The aim is to come out with fewer initiatives, honest numbers and a leadership team that has recommitted in public.

Week 1: Count and cut

List every live initiative with its owner, expected value, cost to complete and the scarce people it uses. Rank them. Agree what continues, what pauses and what stops. Publish the stop list, including business-as-usual work being dropped.

Week 2: Rebase the value

The CFO or finance lead rebuilds the benefits case for the surviving initiatives against an agreed baseline. Separate banked from forecast, gross from net, and cash from capacity. Agree the three or four measures the board will see every month.

Week 3: Move the middle

Take the two workflows that carry most of the value. Run working sessions with the managers who own them. Redesign the steps, decision rights and handoffs. Agree what each manager will stop doing. Give them the authority to change the process without further escalation.

Week 4: Recommit

The leadership team confirms the narrowed programme, the rebased value and the decision rights. Build the benefits into next year's budget and adjust leadership incentives. The CEO tells the organisation what has changed, what has stopped and what has already worked, using verified wins. Set the date for the next stall test, 90 days out.

Our 90-Day Strategy Reset gives a fuller method for reallocating resources on a regular cycle, which suits programmes that need repeated narrowing.

When the right answer is to stop

Some programmes should not be restarted. If the original case depended on market conditions that no longer hold, or the business has since changed direction, more effort on the same plan wastes money and goodwill.

Three questions help. If you were starting today, would you launch this programme? Would you fund it at its current cost to complete? Is there a smaller version that captures most of the value with half the effort?

If the answers are no, no and yes, narrow the programme to that smaller version and close the rest formally. Leaders tend to avoid this decision because it feels like admitting failure. Usually the bigger risk is the opposite: a programme that keeps running long after it stopped creating value, consuming the senior attention the business needs elsewhere.

If the stall test is revealing something deeper, such as falling margins that no programme seems able to fix, it may be a question of business health rather than programme health. Solvent but Stuck sets out how to tell a bad year from structural decline.

Questions for the board or leadership team

• How much of the value claimed so far can finance see in the management accounts?
• How many initiatives are live today, compared with launch?
• What has the business formally stopped doing since the programme began?
• Which decisions have been deferred more than once, and why?
• Are the programme's benefits in next year's budget, owned by line managers?
• Can managers below the executive describe what they now do differently?
• If we were starting today, would we launch this programme at its current cost to complete?

A note on independence

Most stalled programmes are visible from inside the business. The difficulty is that the people who can see the stall are often the people who would have to say so publicly, about a programme their leaders have backed. An independent view helps for that reason more than any other: it makes it easier to say what several people already suspect.

Allington Advisors works with founders, CEOs and leadership teams on transformation programmes that have lost pace, from short health checks to a full reset or turnaround. If your programme scores in the stalled range, or your leadership team cannot agree on its score, we would be glad to talk it through.

Companion download: Transformation Stall Test: Diagnostic and 30-Day Reset Pack