Transformation run as a sequence of small bets you can stop after any one of them
Big bang transformation is for organisations that can afford to be wrong. This is the other approach: change sequenced so that every stage pays for itself, nothing depends on the stage after it, and stopping is a legitimate outcome rather than a failure.
Book a free 30-minute conversationThe programme is usually designed so that stopping is the most expensive option
A conventional transformation programme is scoped as a whole, funded as a whole and justified by a benefits case that only arrives at the end. Eighteen months in, the honest assessment is that two of the six workstreams were wrong. But the case was written as one thing, so stopping means admitting the whole thing failed, and continuing means spending more on the parts nobody believes in.
That is a design flaw, not bad luck. If the programme had been sequenced so that each stage was independently worth doing, the same eighteen months would have produced two stopped workstreams, four delivered ones and a board that trusted the reporting.
What this is
Programme-level change where the operating model has to move as well as the technology, run alongside your team rather than instead of it, and sequenced so that authority to continue is re-earned at every stage.
It covers both halves of the job title deliberately. Digital transformation without business transformation produces better systems running the same broken process. The reverse produces a redesigned process that no system supports.
The sequence, and the points at which you can stop
Five stages. After each one there is a decision point where continuing is a choice, the work so far still stands on its own, and stopping costs you nothing beyond what you have already had.
-
01
Establish the facts
3 to 4 weeksWhat is actually there, what it costs to run, and where the operating model and the technology already contradict each other.
Stopping pointWhat you keep
A documented current state and a costed baseline, useful to any supplier, including one who is not me.
If you stop here
You have an independent picture of your own operation. Many organisations should stop at exactly this point.
-
02
Prove one thing
4 to 6 weeksOne process, changed end to end, in production, with the operating model moved alongside it. Small enough to fail safely and real enough to count.
Stopping pointWhat you keep
One improved process, live, with the measurement in place to show whether it worked.
If you stop here
You keep a working change and hard evidence about whether this approach suits the organisation.
-
03
Fix what the first one exposed
6 to 10 weeksThe first change always uncovers a constraint: data, integration, an unwritten process, a supplier who cannot move. This stage is fixing that rather than pressing on past it.
Stopping pointWhat you keep
A constraint removed that would otherwise have limited everything after it.
If you stop here
The organisation is measurably easier to change later, whoever does it.
-
04
Repeat across the two or three that matter
3 to 6 monthsThe same pattern applied to the small number of processes that carry real cost or risk. Sequenced one at a time, not run in parallel.
Stopping pointWhat you keep
The material improvements, each independently justified and independently reversible.
If you stop here
You can stop after any single one. The sequence is designed to be interrupted without stranding anything.
-
05
Hand it over
4 to 6 weeksThe internal team running what was built, the measurement in their hands, and the next two stages written up so they can be done without me.
Stopping pointWhat you keep
An operation your team runs, and a documented sequence for whatever comes next.
If you stop here
This is the intended end. If it arrives earlier than planned, that is a good outcome.
No stage assumes the next one is funded. Each is scoped, priced and justified on its own, and the decision to continue is taken by you at a point where you have new evidence rather than new optimism.
Why an independent adviser sells delivery at all
The implementation conflict test
Independence is only real until there is delivery revenue on the table. So the conditions are published, they are the same five that govern every piece of delivery work I take, and you can hold me to them. All five must be met before I accept delivery work arising from advice I was paid to give. If any one of them fails, I help you find someone else and take nothing for the referral.
-
1
The recommendation came first, and in writing
The advice exists as a dated document written before any delivery conversation. You can read what was recommended and when, and check that the delivery scope follows it rather than the other way round.
-
2
You were given a genuine alternative
At least two other credible suppliers are named, with an honest view of where each would be stronger than me. Not a courtesy list. A real one.
-
3
The delivery scope is smaller than the advice
If the recommended programme is larger than the piece I would build, I take the piece and you keep the programme. I do not use advisory access to win the whole thing.
-
4
No ongoing dependency is created
The engagement ends with your team able to run what was built. If the work would only function with me still attached to it, it is the wrong work for me to do.
-
5
The board or its equivalent has seen this test
Whoever approves the spend has been shown these conditions and has agreed the delivery work on that basis. This is not a page you have to find. It gets put in front of them.
If you think a piece of delivery work failed this test, say so and I will withdraw from it.
What you get
- A costed baseline: what the current operation costs to run, documented well enough to be handed to anyone
- Changed processes working in production with the operating model moved alongside them, not a pilot in a sandbox
- A stage-by-stage decision record of what was decided, on what evidence, and by whom
- The measurement that shows whether each change worked, in your hands rather than mine
- A documented next sequence, written so your team or another supplier can run it
- A named handover date, agreed at the start. The engagement is designed to end
How this is scoped
Priced by stage, not as a programme. You approve stage one and nothing else. Each subsequent stage is scoped and priced at its decision point, when both of us know considerably more than we did at the start.
How many processes matter
Most organisations have two or three that carry real cost or risk. If the answer is eleven, the first piece of work is narrowing it.
How far the operating model has to move
Changing a system is one job. Changing who does what, and who reports to whom, is a considerably larger one.
What state the data and integrations are in
This determines stage three, which is the most variable stage in the sequence.
There is no total figure on this page, deliberately.
A credible total does not exist before stage one is finished. Anyone offering you one is guessing, and building the guess into the fee. Every stage is fixed scope and fixed fee, with a named end date. No open-ended time and materials, on any stage.
Who this is for, and who it is not for
This is for you if
- The operating model and the technology are visibly in conflict
- Your board has approved a large programme before and would rather not do it that way again
- You have an internal team worth building on rather than working around
- You need a credible first stage you can approve without committing to a programme
This is not for you if
- You want a single supplier to own an entire multi-year programme
- You need a large delivery team. This is run alongside your people, not instead of them
- The decision is already made and what is wanted is execution capacity
- Stopping after stage two would be treated internally as a failure
Independence
No software to sell
I do not own, licence or resell a product. Nothing in a recommendation points at something I profit from.
No reseller agreements
No partner tiers, no referral fees, no vendor relationships that need feeding.
No platform commissions
If the right answer is the system you already have, that is what I will tell you.
Evidence
Delivery accepted, and what it produced.
Case study · housebuilder
A multi-year programme run in stages, each defensible on its own
Operating model and technology moved together, with the option to stop retained throughout.
Housebuilder digital transformation »Case study · charity
Fragmented activity turned into one integrated engine
Sequenced so each stage funded the next rather than the whole thing waiting on a final benefits case.
Fragmented activity to integrated engine »Case study · financial services
A platform migration delivered without a big bang cutover
Staged migration with a working rollback at every point.
Halo Financial migration »What happens next
Book a 30-minute conversationRelated services
AI implementation sprint
If the work is one defined build rather than a sequence of operating model changes.
AI implementation sprint »Fractional digital leadership
If the pattern is that good work keeps stalling because nobody senior owns delivery.
Fractional digital leadership »Independent reviews
If you would rather establish the facts independently before committing to any change at all.
Diagnose »Not sure where to start?
Most clients begin with a conversation. No pitch, no hard sell.
Just a straightforward discussion about where you are and whether I can help.
Book a free 30-minute call