Five models. One chain.

The Digital Maturity Pyramid

AI is the top of a pyramid, not a shortcut. Each layer consumes what the one below it produces, so the least-built layer underneath AI caps the value of everything above it.

The order is physics, not stage theory. Every layer's reason you cannot skip it is a specific input dependency — a model cannot read what was never captured, and it cannot learn from a process that only ever happened in an email thread. The pyramid measures capacity: what your organisation is currently able to convert investment into.

Which is why it goes first, and why it is a prioritisation instrument rather than an orientation one. It does not tell you how good you are. It tells you which layer is holding the ceiling down, so the next pound goes at the constraint — and it is very common for that to be two layers below where the budget is currently pointed.

The five layers

1. 05 AI
2. 04 Automation & Intelligence
3. 03 Interoperability
4. 02 Digitalisation
5. 01 Digitisation

1. 01

   Digitisation

   Getting out of the analogue world: paper, filing cabinets and tribal knowledge become digital records that are searchable and machine-readable.

   Why you can't skip it AI cannot read what was never captured. Every unscanned contract and undocumented process is simply invisible to every layer above this one.

2. 02

   Digitalisation

   Work moves out of inboxes and spreadsheets into systems, so processes produce structured data as a side effect of running.

   Why you can't skip it Models learn from structure and history. A process that lives in email threads has neither.

3. 03

   Interoperability

   Systems start talking. APIs, pipelines and shared schemas turn islands of data into one navigable map, and a customer is the same customer everywhere.

   Why you can't skip it AI's value comes from joined context. Siloed systems cap every model at a single department's view — answers that are locally right and globally wrong.

4. 04

   Automation & Intelligence

   Systems begin to act and to learn. Rote work is automated, decisions get model support, and outcomes feed back in.

   Why you can't skip it AI without actuation is just advice. The feedback loops built here generate exactly the labelled history serious AI needs to learn from.

5. 05

   AI

   Language models, vision and prediction working inside real workflows on your own data, with measured return — not a demo searching for a use case.

   Why you can't skip it This layer multiplies whatever the stack below provides. On structured, connected foundations it compounds; on silos and scans it hallucinates confidently.

The mechanic

What you get out is set by your weakest layer, not your average one. A strong average cannot buy off a weak layer, which is exactly why most maturity models cannot tell you what to do on Monday. Raising the weakest layer moves the number. Raising the AI budget barely does.

And the refusal is in the name: you can't leapfrog the layers — you can speed-run them.

The two foundations

Both are reported alongside the score and neither is ever named as the ceiling, for a stated reason: "fix your culture" is not an actionable next layer to climb. A foundation explains; it does not instruct.

The failure modes

• The leapfrogger. A maximum AI budget on a hollow pyramid. The weakest layer gates the whole investment and a shaky foundation taxes whatever gets through, so most of the spend produces demos rather than capability.
• The laggard. Nothing to leapfrog from and nothing compounding. The good news is that the bottom of the pyramid is the cheapest place to start, and the work starts paying immediately.
• The speed-runner. The one that is not a failure — same order as everyone else, built in quarters instead of decades, with both foundations solid so a moderate AI budget compounds instead of leaking.

Live: the model, with the leapfrog simulator and the 28-statement self-assessment, which names your weakest layer and refuses to defend its own arithmetic.

What this creates Capacity, and nothing else. A pyramid with a raised ceiling and no change in how fast the organisation moves is an expensive way to have the same year twice → The Loop

The Loop

You do not go faster by working faster. You go faster by being wrong sooner.

Every choice that looks like a delivery decision — batch size, branch lifetime, slice shape, release cadence, how much is in flight, whether it ships behind a flag — turns out to be the same choice wearing different clothes: how long you are willing to be wrong without finding out. This is not a claim about care. Careful work and careless work are equally wrong when the thing being built is not what was needed, and careful work stays wrong for longer.

Which is why the model names its own misreading up front. "Slow is smooth, and smooth is fast" is a claim about execution under known-correct intent, and in delivery the target is exactly what is in dispute. Smoothness is real and it belongs here — but slow is not what makes you smooth. Cheap is.

The five segments of the loop

1. 01
   Commit
2. 02
   Slice
3. 03
   Expose
4. 04
   Observe
5. 05
   Correct

risk = how much
× how long

1. 01

   Commit

   Deciding what you are going to be wrong about, in a form that can lose. Not "if adoption is poor" — "if fewer than a third of branches use it by March".

   Why you can't skip it A loop with no commitment cannot close. If nothing was claimed, no observation can contradict it and every result reads as partial success. The trap: a goal is what you want; a bet is what you would accept as evidence that you were wrong to want it.

2. 02

   Slice

   The shape of the thing you will build before you look. Thin and whole: one narrow journey running end to end, in production, for someone real, with everything else honestly absent rather than half-present.

   Why you can't skip it This is the size term of the area, and it is the term people actually control. The test is brutal and simple: can a real person get a real outcome from this, today? If the answer needs a "once we also…", it is not a slice.

3. 03

   Expose

   Getting it in front of reality. Deploy and release are separate events: the code is out, and who sees it is a decision you can change in seconds and reverse without a meeting.

   Why you can't skip it Reality is the only instrument that answers this question. Internal review, however senior, is a simulation of the answer produced by people who already share the assumption being tested.

4. 04

   Observe

   Whether reality can actually answer the question you committed to. The measure existed before the release, and it can move against you — a metric that only goes up is a scoreboard, not an instrument.

   Why you can't skip it This is where most loops silently fail to close. The thing shipped, nobody was lying, and no one ever established whether it worked — so the bet never resolves, it just stops being discussed.

5. 05

   Correct

   Acting on the answer, including — especially — stopping. Something has actually been killed: not descoped, not paused. Stopped, on the evidence, by the people who wanted it.

   Why you can't skip it A loop that cannot change the plan is a reporting cycle, and running it faster produces reports faster. Agree at segment 01 who decides and on what date, or the kill decision becomes a referendum on somebody's judgement and never gets taken.

The mechanic

Your risk is how much you built, multiplied by how long you went before reality answered. It is an area, not a point — which is why cutting either side matters far more than it feels like it should.

Both terms are yours. Halve the slice and halve the cycle and the area falls to a quarter — which is the whole mechanism behind small batches, and why the effect feels disproportionate to the change. Craft does not appear in the formula: it governs how often you are wrong, not how long you stay wrong. Neither does velocity. An organisation can raise its correction rate while shipping less, and frequently should.

The two foundations

Neither is ever the verdict. "Invest in your pipeline" is not a next move for a team that has just been told its loop is open; it is a budget conversation, and it belongs in a different meeting from this one.

The failure modes

• The Careful Disaster. High craft, huge batch, long cycle. Recognise it by how defensible everything is: the process was followed, the work is good, and the thing is not wanted.
• The Open Loop. Shipped, never observed. Recognise it by the absence of anyone who can say whether the last three releases worked — asked directly, people describe what was delivered rather than what changed.
• The Unkillable Bet. Segment 01 was written as an aspiration, so no evidence can retire it. Recognise it by a project that has been "nearly there" through two changes of sponsor.
• The Smooth Runway. A beautifully automated loop around a question nobody asked. Recognise it by excellent delivery metrics and a flat business.
• Motion Without Correction. Short cycles, small batches, no observation. Recognise it by teams who are exhausted, shipping constantly, and cannot name a decision that changed because of something they learned.
• The Simulated Answer. Reality replaced by internal review. Recognise it by "we walked the exec team through it" standing where a user would be.

What this creates Breakage, at a higher rate than before, and that is the trade rather than a defect. An organisation that raises its loop rate without raising its diagnosis rate has bought itself faster chaos → The Narrowing

The Narrowing

Diagnosis is a search, and the only legal move is one that eliminates territory.

Everything that feels like progress and is not — the theory that explains the symptom, the meeting where four people offer four causes, the fix that ships on Friday — has the same property. It adds an explanation without removing a possibility. The search space is exactly as large as it was before, and now there is a story attached to it. Hypotheses are free. Elimination is the work.

"Show me" is not rudeness. It is the cheapest experiment available. You have not found the cause until you can switch it on and off.

The 3 Misses — why the model is needed at all

Before any of the moves, the reason for having a method. A large share of what arrives as a fault is not a fault: it is a failure of transmission between people, and it comes in exactly three kinds.

All three feel identical from the inside: everyone involved is certain they were clear. That is the whole reason this needs a method rather than a conversation — a room of certain people, with no way to eliminate anything, will narrow confidently toward a fault that was never there. The 3 Misses are not a step you complete and move past. They are the standing reason the moves below have to be run on evidence rather than on agreement.

The five moves

1. 01 See it
2. 02 Draw it
3. 03 Frame it
4. 04 Root cause
5. 05 Fix it for good

1. 01

   See it

   Making the fault happen on demand, in front of you — and watching the state just before, during, and just after. Most of the information is in the transition, not the wreckage, which is why a description after the fact is worth so much less than thirty seconds of watching.

   Why you can't skip it Without reproduction you cannot draw a boundary, confirm a cause, or ever know your fix worked. The trap: "it's intermittent" is not a property of the fault. It is a statement that you have not yet found the variable that makes it deterministic.

2. 02

   Draw it

   The path, end to end, around the point where the fault appears — including the parts nobody owns. There is a drawing, it fits on one page, and the people who own each segment agree it is accurate.

   Why you can't skip it A boundary needs something to be drawn on. Without the path there is only a list of suspects, and a list has no inside and outside. Where two teams draw the path differently, stop — the gap between their drawings is where faults live.

3. 03

   Frame it

   Two columns on one page: what the problem is, and beside it what it is not. Same categories down both sides — which sites, which customers, which times of day, which kinds of transaction. It is the Toronto branch; it is not Montreal. It is invoices over ten thousand; it is not the ones under.

   Then the question the whole move exists for: what is different about the things inside the box from the things just outside it? That difference is a very short list, and the cause is on it.

   Why you can't skip it This is the move that makes the problem smaller, and every entry in the "is not" column is territory removed without running a single test. It is the cheapest elimination available and the one a room can do together in twenty minutes. The trap: an empty "is not" column. If the answer to every question is "everything, everywhere", the problem has not been specified — it has only been restated as the fact that something is wrong.

4. 04

   Root cause

   Demonstrating control, not explanation. You can turn it on. You can turn it off. You can turn it on again. The room has gone quiet because there is nothing left to argue about.

   Why you can't skip it This is the falsifiability gate. Without it you have a hypothesis that survived, which is not the same as one that is true and behaves identically until the fault returns. One direction is a correlation with better lighting.

5. 05

   Fix it for good

   Fixing the thing that allowed the fault to exist rather than the instance of it. You can say what class of fault is now impossible, not just which ticket is closed.

   Why you can't skip it Skipping it is not free; it is a loan. The same structure will produce a different-looking fault later, and the diagnosis will start from zero because nobody connects the two.

The mechanic

Every step must eliminate territory. Progress is measured in what has been ruled out, not in what has been proposed.

Four plausible theories and no eliminations is not four times the progress of one theory. It is zero progress, four times. A diagnosis therefore has a measurable state at any moment — the size of the remaining space — and if nobody in the room can say roughly how much smaller it got today, the diagnosis is not being run, it is being attended.

The elimination does not have to be clever to count. Most of it is done at move 03 by writing down what the problem is not, which needs no instrumentation and no specialist — only the discipline to answer the question rather than move past it.

The two foundations

Neither is ever the verdict. "Improve your culture" and "buy observability" are not next moves, and a model that ends there has stopped being useful precisely where it started being needed.

The failure modes

• The Phantom Fault. One of the 3 Misses, diagnosed as a fault. Weeks of genuine engineering aimed at something that was never broken. Recognise it by a root cause that, written down, is a sentence about what somebody thought they had asked for.
• The Plausible Story. A cause that explains the symptom, has never been tested, and stops the search. Recognise it by how good it feels: the room relaxes, the explanation is coherent, and nobody can say what would prove it wrong.
• The Unreproduced Fix. Closed without ever having been seen to fail. Recognise it by "we think it was" and the absence of a before-and-after. It will be back, and it will not be recognised as the same fault.
• Solving the Reported Problem. Move 02 skipped, so the place the symptom appeared is mistaken for the place the fault lives. Recognise it by a fix in the component that raised the error rather than the one that produced the condition.
• The Fix That Ships. Move 05 skipped. The instance is repaired, the structure reloads. Recognise it by a team that is good at firefighting and cannot say why there are so many fires.
• The Everything Box. Move 03 attempted with nothing in the "is not" column — every site, every user, every time of day. Recognise it by a diagnosis that has been busy for a week and cannot say what it has ruled out.
• The Committee. Four people, four theories, no tests, and a decision by seniority. The loudest hypothesis wins and nobody notices that no information was added.

What this creates A system that gets fixed properly, and an organisation whose judgement is untouched. Move 06 kills recurrence in the machinery; it does nothing about a leadership team that reliably prices its own changes wrong → Orders of Consequence

Orders of Consequence

A change is not an event. It is a propagation — and two things travel in opposite directions.

What you meant gets lost. It leaves your mouth whole and arrives in fragments, a little weaker at every hand-off, until the person who actually has to do something differently has received a rumour of a priority. What it causes gets bigger. The first effect is the one you planned; the fourth is what becomes possible because all of it happened, and it arrives late enough that nobody connects it to you. Almost every change that fails, fails in the gap between those two.

You are judged at Order 2 and paid at Order 4. At Order 2 the costs are visible, specific and attached to named people; the benefits are not there yet, and when they arrive they will be diffuse and attached to nobody. Judge in between and you get a decision that feels rigorous, is supported by real evidence, and is wrong.

Two ways to use it

The orders run in one direction, but the model is worth two different things depending on when you pick it up, and most people only ever learn the second.

The five orders

What you meant What it caused

1. 4 The Compounding paid here
2. 3 The Adaptations
3. 2 The Workarounds judged here
4. 1 The Mechanics
5. 0 The Decision

1. 0

   The Decision

   What was actually decided, as opposed to what was announced, discussed or minuted. Somebody can state it in one sentence without using the word "strategy", and the sentence has a verb in it.

   Why you can't skip it Every order above is a consequence of something. If the decision is a direction rather than a change, there is nothing for the orders to be consequences of.

2. 1

   The Mechanics

   What changes in the work itself — the system, the process, the form, the step added or removed. There is a date, a budget line and a person.

   Why you can't skip it Nothing propagates from an intention. Until something concretely changes, there is nothing for anyone to work around. The trap: this is the part with a Gantt chart, so it is the part that gets managed, and it is rarely the part that decides the outcome.

3. 2

   The Workarounds

   What people do to keep the work moving while Order 1 lands on them. The parallel spreadsheet, the WhatsApp group, the one person who still knows the old way and is quietly doing it for everybody.

   Why you can't skip it This is where the real cost of every change sits, and it is never in the business case. The trap: workarounds are read as resistance. They are almost always competence — treat them as misbehaviour and you lose both the information and the informant.

4. 3

   The Adaptations

   The new habits, norms and informal structures that form around the change and then outlive it. Who people ask now. What the meeting is for now. What "done" means now.

   Why you can't skip it This is where a change becomes irreversible. Below it, removing the mechanic removes the change; above it, the organisation would have to be changed back on purpose.

5. 4

   The Compounding

   What becomes possible because the change happened. Not the benefit you promised — the second thing, the one that was unaffordable before and is now routine.

   Why you can't skip it You cannot skip it, but you can fail to claim it, and organisationally that is the same thing. An Order 4 benefit nobody attributes buys no credibility for the next change.

The mechanic

Your change horizon is the deepest order at which you can name a concrete instance that has already happened. Not one you can imagine. Not one you can argue for. One you can name, with a person attached.

Most organisations, measured honestly, have a horizon of Order 1. A change judged below the order where its benefit lives will be killed — not by short-termism, but by rigour applied to a truncated dataset. The mechanic has no opinion on the merits: it scores the observer, not the change.

The two foundations

Call it half lost per hand-off. That number is a teaching claim, not a measured coefficient — if someone wants to argue about the fraction, agree immediately and ask the question it was standing in for: how many genuinely different forms has the person who has to change actually received this in?

The failure modes

• The Rigorous No. Killed at Order 2, where all cost and no benefit is visible, by people doing exactly what good governance asks of them. Recognise it by evidence that is genuinely strong, genuinely relevant, and entirely about cost.
• The Announcement. Transmitted once, in one form, and mistaken for landed. Recognise it by "we've communicated that" said in the past tense, and by a leadership team who can all state the change while nobody two levels down can.
• The Saturated Org. Every change individually sensible, collectively nothing sticking, and the diagnosis lands on culture. Ask how many active changes are landing on the same forty people and watch nobody know.
• The Unclaimed Win. Order 4 arrives and nobody connects it to the decision that caused it. Recognise it by an organisation that has plainly improved and a leadership team who still say "we're not good at change".
• The Order-1 Manager. Runs the mechanic superbly and believes that is the job. Recognise it by an implementation that came in on time and on budget and changed nothing.

What this creates Changes that survive long enough to reach Order 4 and get credited for it. One change reaching Order 4 is not compounding, though — it is one payoff. What happens when many of them start reinforcing each other is a different model → The Flywheel

The Flywheel

Compounding is a threshold, not a rate. Below it every turn is a cost; above it the same turn is an engine.

This is the only model here that is not a thing you do. It is what happens to an organisation that has been doing the other four correctly for long enough — and the reason it needs stating separately is that the curve is flat for a long time and then is not, and almost every organisational decision about it gets taken during the flat part on evidence drawn entirely from the flat part.

It is also the model most likely to be misused, so the refusal goes in the name: a flywheel is not something you have. It is something you are still pushing. Announcing one does not load one. Every organisation that has declared a flywheel in a deck and not named a single turn that made the next turn cheaper has described a wish with a diagram attached.

The five elements

1. 01The repeatable unit
2. 02The retained gain
3. 03The reinforcing link
4. 04The turning point
5. 05Value in the connections

1. 01

   The repeatable unit

   Something that happens again, in a recognisable form. A release, an onboarding, a claim, a store opening, a model retrain — the turn of the wheel.

   Why you can't skip it Compounding is a rate applied over periods. With no period there is nothing for a rate to apply to. The trap: every initiative being a special case is not evidence that your business is unusually complex. It is the reason nothing it does ever accumulates.

2. 02

   The retained gain

   What each turn leaves behind. The template, the cleaned dataset, the pipeline, the integration, the decision nobody has to relitigate.

   Why you can't skip it A turn that leaves nothing behind is exercise. The test is whether the next team starts further along than the last one did — if they start from zero, the previous turn was consumed rather than banked, however well it went.

3. 03

   The reinforcing link

   The retained gain has to make the next turn cheaper, faster or more valuable. Not adjacent to it — feeding it.

   Why you can't skip it Accumulation is a pile; compounding is a loop. Without the link back you get an impressive inventory of assets and a delivery pace that has not moved in three years. The honest question: name the thing that got cheaper, and by how much.

4. 04

   The turning point

   Where what you are building back up finally outpaces what is wearing it down. Every loop has decay working against it: turnover, re-orgs, systems ageing, knowledge leaving, the platform nobody has patched.

   Why you can't skip it Before it, the wearing-down wins and the investment reads — correctly — as not working. The trap: this is precisely where most of these programmes are cancelled, on evidence that is entirely accurate, by people applying exactly the rigour they are paid for.

5. 05

   Value in the connections

   Where the worth stops being in the pieces and starts being in what joins them. The tenth integrated system is worth more than the first nine were, because it can reach all of them.

   Why you can't skip it This is where returns stop being linear. You cannot skip it, but you can fail to build for it: point-to-point integration accumulates cost at the same rate it accumulates value, so it never crosses over — it just gets bigger.

The mechanic

Compounding = reinforcement − friction. Only the sign matters. Not the size. A small positive compounds to everything given enough turns; a small negative decays to nothing over the same turns, and the two are indistinguishable for the first year.

Which is what makes this expensive to get wrong in either direction. The same investment reads as visionary or as waste depending only on which side of zero it is sitting, and that is not visible in the numbers early — it is only visible in whether anyone can name the thing that got cheaper. Ask for the last three turns and what each one left behind. If the answer is three achievements and no inheritance, the sign is negative and more funding will not change it.

The two foundations

Neither is ever the verdict. "Be more patient" is not a next move for anyone, and a model whose recommendation is a personality trait has stopped working. The next move is always at element 02 or 03: what did the last turn leave behind, and what did it make cheaper.

The failure modes

• The Announced Flywheel. Named in a deck before a single turn has been retained. Recognise it by a diagram with four arrows and nobody who can point at an instance.
• The Pile. Real assets, genuinely accumulating, no reinforcing link. Recognise it by a platform team that can list everything it has built and cannot say what got cheaper.
• Cancelled at the Bottom. Killed just short of the turning point, on accurate evidence, by people doing their jobs properly. This is the Rigorous No from Orders of Consequence, arriving on a longer timescale and with better numbers behind it.
• The Point-to-Point Estate. Integration count rises, value rises with it, cost rises slightly faster, and it never crosses over. Recognise it by a team that describes itself as "very integrated" and an integration backlog that has never once been shorter than last year.
• The Restart. Each new leader begins their own wheel rather than pushing the one already turning. Recognise it by three half-loaded flywheels, none above threshold, and an organisation that has been "on a journey" for a decade.

What this creates A raised ceiling — which is a different constraint, not the absence of one. Above the threshold, the layer that limits you is rarely the layer that limited you before → back to the Pyramid