01What does the 18-month stall look like in a transformation program?
A stalled transformation program looks active. The first year brings a mandate, a budget and a burst of work. Around 18 months in, the spend is large and visible, the benefits are still some way off, and every status report shows movement and few results.
Signals a board can see without opening the plan:
- The portfolio has grown and the team hasn't. More initiatives than at approval, with key people on three or four at once.
- Milestones slip by weeks, then by months. Each slip has a reasonable explanation.
- Reports describe activity. Milestones such as "platform ready", and little customers or staff can use yet.
- Forums review and rarely decide. The same issue comes back to steering committee month after month.
- The first benefit has no firm date. The answer is a range, or a later phase.
- The leadership keeps changing. A second program director or a new sponsor, each followed by a re-plan.
The Sequencing Reframe describes the outcome plainly: no decisions made, and nobody moved to the work that matters.
02Why do transformation programs stall?
Transformation programs stall for structural reasons, and five of them usually act together.
- The Alignment Trap. Every initiative has a sponsor and a rationale, and each one is defensible on its own. When stopping or delaying anything needs everyone to agree, continuing is always the easier path, so the portfolio keeps growing.
- Everything is sequenced at once. New priorities from regulators, markets and new executives are added on top, until five projects share the same twelve people.
- Value sits past the horizon. When most of the portfolio is six months or more from anything the business can use, the board sees spend and no return.
- Decision rights are unclear. Decisions stall wherever there is ambiguity over who decides, as Paul Rogers and Marcia Blenko argued in Harvard Business Review. A steering committee without the authority to move work back can only record progress.
- Fatigue sets in. People spread thin for 18 months lose pace, the best become bottlenecks, and each change of leader brings another re-plan.
In McKinsey's 2021 global survey, less than one-third of respondents said their transformations both improved performance and sustained the gains, and 55 percent of lost value was lost during and after implementation, where a stall happens.
03What should a program health check ask at month six and month 18?
A program health check should ask eight questions, answered on one page by the people running the program. The questions stay the same at month six and month 18; the healthy answer changes.
| # | Question | A healthy answer at month six | A warning sign at month 18 |
|---|---|---|---|
| 1 | What can the business use today because of this program? | Something specific is in use or close to it | Only milestones such as "platform ready" |
| 2 | When does the next real result land, and what is the evidence for that date? | A named result, a date, and a confidence level | A date that has moved more than once |
| 3 | Is the portfolio larger than the one approved, and what moved back to make room? | Same size, or every addition paired with a named delay | More initiatives, nothing moved back |
| 4 | How many people are working on things that won't deliver for six months or more? | A minority, and known | Most of the team, and nobody has added it up |
| 5 | Who can move a project back, and when did they last do it? | A named forum that has used that authority | Nobody, or never |
| 6 | Who owns each benefit, and has the date of the first benefit moved? | A named owner, a baseline, an unchanged date | Benefits owned by the program, dates pushed to a later phase |
| 7 | What is stuck for reasons more people won't fix? | Vendor, data, approval and ownership blockers listed with owners | Blockers raised repeatedly and still open |
| 8 | Are the key people still in place, and how many projects is each one on? | Leaders in place, key people on one or two projects | Leadership changed, key people on several projects |
Three or more warning signs at month 18 is the 18-month stall. Question 4 often changes the conversation: The Sequencing Reframe's example is a room finding that 40% of its engineers are on work nine months or more from any result.
04How do you restart a stalled program?
You restart a stalled program by re-sequencing it around value: people move to the work closest to a real result, and every other project keeps its place on the plan with a new start date. Following The Sequencing Reframe, the restart runs in six steps.
- Build the one-page view. Every project on one page: team size, monthly cost, the next real result, when it lands and how confident the team is. A real result is something the business can use and measure. A milestone such as "platform go-live" counts only when it leads to a result such as "the first 500 customers using the new platform".
- Brief the most senior person first. One on one, so they take in the picture without an audience.
- Run a portfolio sequencing review. A 60 to 90 minute meeting with the people who own the portfolio. Put the one-page view on screen and let the room read it before anyone speaks. The name matters: "project rationalisation" puts every sponsor on the defensive.
- Work through the Reframe's four questions in order. They move the room from what is closest to delivering, through where people are spread too thin, to what can safely start later. Projects that can't wait because of a regulation, a contract or a market window stay where they are.
- Give every project a decision. Speed up (move more people here), keep going (on track), push back (release the people to other work), or rethink (the original reason has changed since approval).
- Share the new order with the teams affected. Delayed teams hear that their work is on the plan and when it starts: "Still important, just sequenced after [project], which delivers [result] sooner."
A worked example: a regional bank has eleven initiatives sharing one change team. The one-page view shows four producing something usable within three months and five more than nine months from any result. Two of those five move back a quarter, their people join the two initiatives closest to launch, and one is flagged for a rethink because the regulation behind it has changed.
05How do you reset governance and decision rights after a stall?
Reset governance by giving one forum the authority to set and hold the order of work, with input kept broad and authority kept narrow. The Transformation Office is usually that forum.
- New work enters through the same test. Every request faces the same questions as the work already in the order, "urgent" requests included.
- When something goes first, something named moves back. The forum says which project moves, tells the affected team and gives them a new start date. The person asking for the new work sees exactly what it delays before they commit to it.
- People are the limit. New projects wait until people are available, or something less important moves back. They are never added to a team that is already full.
- The order is reviewed every quarter, with the same questions, whether or not anything feels urgent.
A sequenced portfolio can be agreed quickly once the forum exists: in one $2B+ banking simplification program, 100+ leaders aligned behind 24 initiatives across five business lines within eight weeks.
To protect momentum, report results the business can use, keep key people on one or two projects and show the board a first result within months. Reordering has limits: when a project is stuck on unclear ownership, vendor delays or old technology, the one-page view shows the problem and someone with the authority to fix it has to act.
Read the case study →Explore Transformation Office & Strategic Orchestration →Explore TxO Mobilisation →How to manage a large-scale transformation →
06How does transformation program recovery work under regulator or audit scrutiny?
Recovery under scrutiny follows the same method with less room to move: regulator and audit commitments become fixed items in the order, and every claim of progress needs evidence an outsider can test.
The public record shows the pattern. The Audit Office of New South Wales reported in May 2026 that a state agency's core technology program is forecast to finish four years late, with a further $493 million in forecast funding; after its main supplier contract ended, the agency lacked effective governance, capability and financial controls, until a reset stabilised the program. Tasmania's Auditor-General found that one agency spent about $47 million over four years on an HR system without delivering any of the planned components; known problems were raised repeatedly and never fixed, and the program lead lacked the power to resolve some of them.
Recovery under scrutiny adds four things to the restart:
- One accountable executive with authority over the order, named to the regulator or auditor.
- The commitments at the front of the order. Anything a regulator, auditor or court has required is in the "can't wait" group from day one.
- Independent assurance that reports to the board, separate from the people delivering the work.
- A test that the changes last. Before the program closes, the regulator or auditor sees evidence that the new controls have held through several cycles of normal operation.
07Where should a board start with a stalling program?
Start by asking the eight health check questions this month and scoring the program alongside them. The Transformation Maturity Assessment takes 5 minutes and gives a scored baseline in an instant, confidential PDF report: where the program is strong, where risks are emerging and what to fix first.
Take the Transformation Maturity Assessment →
Notes and sources
- Less than one-third of transformations improve performance and sustain it; 55 percent of value loss during and after implementation: McKinsey & Company, "Losing from day one: Why even successful transformations fall short", 7 December 2021 (McKinsey Global Survey, 1,034 participants)
- Decision rights: Paul Rogers and Marcia Blenko, "Who Has the D? How Clear Decision Roles Enhance Organizational Performance", Harvard Business Review, January 2006
- Core technology program four years late and a further $493 million forecast: Audit Office of New South Wales, "Upgrades to core policing technology", 11 May 2026
- HR system, about $47 million over four years with none of the planned components delivered: Tasmanian Audit Office, "Planning and early implementation of the Human Resource Information System", 2026
- The one-page view, the four questions, the portfolio sequencing review, the scorecard decisions and the 40% example: Transformativ, The Sequencing Reframe
- Banking simplification figures: Transformativ case study


