In short
- There are 4 kinds of done: delivered, adopted, performing and owned.
- Most transformations only plan for the first.
- Boards are shifting the finishing line towards performing and owned.
- Write your definition of done – with baselines – before work starts.
Ask a programme team when their transformation will be done and you’ll usually get a date. Ask the board and you may get a different answer: when it’s working. Ask the people whose jobs it changes and you may get a third: when it stops being a programme and becomes how we work.
Those 3 answers describe 3 very different finishing lines. Most transformations only plan for the first – and that’s a big part of why measuring transformation success is so often contentious.
The 4 kinds of done
It helps to separate 4 meanings that usually get bundled together.
1. Delivered. The thing has been built and switched on. Systems are live, processes are documented, people have been trained. This is where most programmes declare victory and most contracts end.
2. Adopted. People are actually working the new way – not alongside the old way, not with workarounds, but as their default. Adoption is often assumed and rarely measured.
3. Performing. The business measures the transformation was meant to move have moved, against a baseline taken before it began. This is what the investment was for.
4. Owned. The organisation can run, improve and extend what was built without the people who built it. The capability has transferred; the dependency hasn’t.
A transformation that’s delivered but not adopted is an expensive pilot. One that’s adopted but not performing is a change of habit, not of results. And one that’s performing but not owned will slowly decay once the outside team leaves.
“Delivered but not adopted is an expensive pilot. Performing but not owned slowly decays.”
Why the definition is shifting
For a long time, delivered was enough. Boards approved investments on the strength of a business case and judged programmes on time and budget.
That’s changing, for 3 reasons.
Boards want evidence of value. After years of investments that landed on time and changed little, boards are asking whether money created the value it promised – not just whether it was spent as planned.
Costs now continue after go-live. Subscription and consumption-based technology means finance teams track the cost of change long after delivery. That puts pressure on the benefits side of the ledger.
Organisations want to stop renting capability. Many have relied on external partners for years and are asking why, after so much investment, they still can’t run things themselves.
The result is a slow but clear move towards defining success as performing and owned – and towards contracts, governance and partners judged on those terms.
YESTERDAY’S FINISH LINE
On time, on budget, live.
TOMORROW’S FINISH LINE
Performing against a baseline, and owned in-house.
What this means for how transformations are run
If done means performing and owned, several things about how programmes are set up have to change.
Baselines come first. You can’t show performance without a before. Baselines need to be taken before work starts, not reconstructed afterwards.
Adoption is measured, not assumed. Usage, workarounds and the persistence of old processes need tracking alongside delivery milestones.
Capability transfer is designed in. Knowledge, methods and tools move to the client throughout the work, not in a handover pack at the end.
Partners are judged differently. The question shifts from “did they deliver?” to “did it work, and can we run it without them?” Some engagements will include a modest at-risk element once baselines and controllable outcomes are clear.
Assurance continues after delivery. Independent measurement of whether value is being realised becomes a service in its own right, rather than an afterthought.
Agreeing done on day 1
The most useful thing a leadership team can do at the start of a transformation is write down what done means. Specifically:
1. Which business measures should move, by how much and by when – with a baseline taken before work starts.
2. What adoption looks like – who will be working differently, and how you’ll know.
3. What capability must be left behind – which skills, methods and knowledge must sit inside the organisation at the end.
4. When outside help should step back – and what would justify it staying, if anything.
These questions are easy to defer and expensive to answer late. A programme that hasn’t agreed them will default to “delivered”, because that’s the only finishing line anyone can see.
Built to leave
We think the right ambition for any transformation partner is to be needed less over time. That means designing the exit into the engagement from the start: transferring methods and knowledge as the work happens, and remaining only where independent assurance continues to add value.
Done, properly defined, is the point at which the organisation no longer needs you to keep the result going. It’s a harder finishing line to reach. It’s also the only one that justifies the investment.
How to measure each kind of done
Each finishing line needs its own evidence. A simple scorecard keeps all 4 in view.
| Kind of done | Example measures | When to check |
|---|---|---|
| Delivered | Scope complete, systems live, people trained | At go-live |
| Adopted | Active usage, workarounds remaining, old processes retired | 1–3 months after go-live |
| Performing | Movement in business measures against baseline | Quarterly, from go-live |
| Owned | Internal team running and improving it; external support reduced | Before external partners step back |
The point isn’t to measure everything. It’s to make sure the programme can’t declare victory at the first line when the investment was made for the third and fourth.
Common questions
How do you measure transformation success?
Against 4 tests: was it delivered, is it adopted, is it improving the business measures it was meant to move (against a baseline), and can the organisation run and improve it without the people who built it?
What are good transformation success criteria?
Specific business measures with baselines and targets, explicit adoption indicators, defined capability to be transferred, and an agreed point at which external support steps back.
What is capability transfer in a transformation?
Moving the skills, methods, tools and knowledge needed to sustain and extend a change into the organisation, so results persist after external partners leave.
What this looks like in practice
For a UK gas distribution network, we built a Board-ready modernisation investment case – and then stood up a permanent Transformation Office and coached the team to run it themselves. The work was designed from the start to reduce the client’s dependence on external consultants. Read the case study →



