The Eight-Stage Redesign Sequence
The reference version of Chapter 11's sequence — the strategic roadmap from Chapter 9, in stage detail. Read it as one design deployed in stages, not as eight projects. The early stages are the whole-design work: the design gets drawn, tested for fit, and validated before serious money moves. The later stages are the managed deployment — pieces of one design released in strategic priority order, gate by gate, around a business that keeps serving customers the whole way.
Lessons learned at a gate may re-order what comes next — in writing, owned, inside the design. The destination doesn't move.
Stage 0 — Classify the door
Purpose: decide, before anything else, whether this redesign is reversible.
Entry: a specific redesign candidate that has passed the Five-Question Screen.
Exit: a written classification — two-way door (revertible without lasting damage) or one-way door (core process, brand promise, customer relationship, or a stage's design assuming one vendor's current roadmap, at stake) — and the rigor level that follows from it.
The judgment call: drifted companies walk through one-way doors at two-way speed. When in doubt, classify up.
Stage 1 — Assemble the Three Sources
Purpose: put Depth, Distance, and Delivery in place before direction is set.
Entry: Stage 0 classification done.
Exit: named Depth individuals with extraction sessions scheduled; a vetted Distance source under a time-boxed engagement; AI positioned only to execute and narrow options, never to set direction.
The judgment call: resisting the pull to let the tool set the direction. Delivery is necessary just to keep up — parity, not advantage — and it is never the source of the edge.
Stage 2 — Draft against the fit test
Purpose: design the redesign as a system, not a features list.
Entry: Depth extraction complete; Distance sessions run.
Exit: a draft that shows at least second-order fit — the new process reinforces other activities, and they reinforce it back.
The judgment call: killing the draft that is merely a better single activity. First-order fit is the copyable kind.
Stage 3 — Validate the delta
Purpose: prove the advantage is real to customers before scaling into it.
Entry: a fit-tested draft.
Exit: a pilot with a small, tolerant customer group has moved a perception or loyalty metric — not an internal efficiency metric — and the pilot was explicitly allowed to fail.
The judgment call: distinguishing validation from enthusiasm. This is a delta test against your existing baseline, not a discovery test. Test for negative surprises, not the happy path.
Stage 4 — Stage the capital
Purpose: commit to the destination while capping the exposure.
Entry: validated delta.
Exit: gated tranches — discovery, then proof, then production — each released only when the prior gate's evidence clears. Budget multiples of the pilot, not increments. Each gate doubles as a scheduled moment to brief lenders or a board against pre-seen thresholds.
The judgment call: holding the gate when the team is excited and the evidence is thin.
Stage 5 — Pre-write the failure conditions
Purpose: write, before scaling, what result means “this failed” and what happens when it appears.
Entry: tranche structure agreed.
Exit: a complete IF/BY/THEN set — see Pre-Written Failure Conditions — with a named kill owner.
The judgment call: writing conditions sharp enough to trigger. A failure condition nobody could ever hit is a decoration.
Stage 6 — Lock in the protection
Purpose: make the validated advantage legally and contractually hard to take.
Entry: a redesign worth protecting — the Moat-vs-Parity Test says moat, not parity.
Exit: trade secrecy treated as the default approach to IP protection; NDAs and confidentiality agreements tightened rather than reliance on the collapsing non-compete; exclusivity formalized in contract for any data partnership the moat depends on; engagement-letter consent and vendor data-use terms confirmed before any pilot touches live data; and a named plan for retaining the people who hold the Depth.
The judgment call: accepting that this stage decays. AI is lowering the cost of reverse-engineering, which erodes trade-secret defensibility itself.
A note that is not a formality. This stage describes strategy, not counsel. Nothing in it is legal advice. Engage qualified counsel before acting on any of it.
Stage 7 — Govern the risk tier
Purpose: apply governance proportional to what the system can break.
Entry: a scaled, protected redesign in production.
Exit: a written risk classification — light-touch for low-stakes, heavy for anything touching safety, compliance, or customer trust — with the bulk of the business kept in safe, proven operation and the stages under active deployment capped and contained.
The judgment call: this stage never exits. It hands off to the Cadence: the calendar, signal, and decay-rate triggers in Chapter 12 are what re-open Stages 1–3 when the melt begins.
How to use it: This is anatomy, not instructions. The sequence matters as much as the stages: most redesigns die in the transitions, not inside them. Print this page →