The argument so far, in one breath: your pilots work and don’t pay because they simulate conditions your enterprise doesn’t have; the conditions are four, and testable; the place you create them is a capability, not an application; and once created, AI has three real jobs and one it can never take. That leaves the question every executive actually gets paid to answer: how do you run this? Across a real enterprise, with a real board, on a real clock?
Here’s where transformations die a second death. Having accepted everything above, the organization does the instinctive thing: it tries to do it everywhere at once.
Horizontal Is Why Your Last Transformation Failed
You’ve seen the horizontal play. Pick a layer: a new governance model, a new team structure, a new engineering practice. Roll it across the whole organization. Train everyone. Announce the operating model. Measure adoption. We watched this fail for fifteen years in agile transformations, and you’ve watched it fail in ERP rollouts, Six Sigma programs, digital, and cloud. The failure has a signature: everything moves and nothing finishes. Every team is 20% transformed, no team is done, the old system and the new system run simultaneously everywhere, and eighteen months in, the sponsors quietly stop asking.
The alternative is vertical: pick one slice and install the whole system in it. Not one practice everywhere. Everything, somewhere. One capability, cut at its natural seam, with new structure, clean data, a new delivery model, lightweight governance, and AI inside the boundary, all the way to production. When I walk transformation leaders through this, including people who’ve spent careers pushing horizontal change uphill, I have yet to hear a real objection. They’ve lived the alternative.
The Loop
The whole approach fits in one loop.
- Identify the business problem: a real one, with money attached, not a use case hunting for a justification.
- Carve the slice: the capability that owns that problem, cut at the seam, through the org, the application, and the data.
- Create the conditions inside it: the four from earlier in the series, built for real in one bounded place.
- Put AI to work: navigator first to map it, junior engineers under supervision to build it.
- Prove the value: in production, in numbers your CFO accepts, in roughly ninety days.
- Then do it again.
The pattern behind the loop is the strangler fig. The fig doesn’t fight the tree; it grows around it, capability by capability, until one day the old tree is structure, not function. That’s how you get off the legacy platform without the bet-the-company rewrite. Each slice you pull gets a deliberate decision: this piece goes to the ERP you already own, this piece retires, this piece gets built custom because it’s how we win. Slice by value proposition, never lift-and-shift. The backlog of slices burns down over time, and every one of them pays its own way.
Two disciplines keep the carving honest. First, slices are cut from a map, not freehand. The capability map and the end-state picture come before the knife, and every slice is a deliberate move on that map, so the slices accumulate into an architecture instead of a new kind of fragmentation. Second, the backlog is sequenced economically. Inventory the value propositions worth solving and weigh value and cost of delay against effort. Many of you know this as WSJF. Take them in that order, and re-rank as each slice teaches you something. All of which surfaces the thing no transformation program ever says out loud: you only go as far as there’s economic value to be achieved. When the marginal slice stops paying, you stop. The transformation has a bottom.
Ninety Days or It Isn’t a Slice
The economics are the governor on the whole system. If a slice can’t prove its value in about a quarter, it wasn’t scoped as a slice; it’s a project wearing a slice costume. Cut deeper. The ninety-day proof does three jobs at once: it pays for the work, it buys leadership patience with evidence instead of vision, and it de-risks the next slice before you cut it.
It also respects something the transformation industry keeps pretending away: trust is earned in stages. Nobody, no vendor and honestly no internal team either, should be handed production on a promise. The gradient runs: map the estate first, which requires almost no trust. Show the plan. Prove one slice. Widen the aperture. If somebody proposes to transform everything before proving anything, the size of the ask is the tell.
What Compounds
Here’s what the horizontal play never delivers and the vertical play can’t help delivering: each slice leaves the conditions behind. An encapsulated capability. Data that’s clean at the source and stays that way. A team that owns something and knows it. A governance rhythm that funds hypotheses and kills losers. The second slice starts easier than the first; the fifth starts easier than the second. Somewhere along the way, transformation stops being a program you’re running and becomes a thing your organization knows how to do, which was the actual goal all along. Not “we adopted AI.” Not a vendor relationship you can’t exit. A capability that stays when the program ends and the consultants go home.
The Whole Story
We drew a map: pilots live in the quadrant with conditions; enterprises live in the quadrant without them. We read the gauge: twenty working pilots and zero ROI is a measurement, not a mystery. We named the four conditions and gave you the tests. We changed the unit from applications to capabilities, and found the seams. We put AI in its three right jobs and kept judgment human.
And now the ending, which was hiding in the first post all along: don’t move the pilot to the organization. Move the organization, one slice at a time, to where the pilot can live.
Somewhere out there is a CTO with twenty pilots and a board asking where the money went. The next twelve months can be more demos. Or they can be four slices. Clean one boundary. Deliver one slice. Measure it. Do it again.
In my next post, we’ll explore why you can’t bet prodcution on a promise.
This is Part 6 of a seven-part series. Start with Part 1 here.
