part ten · adoption

Adoption

How to start. Which practice first. The first cycle. What resistance looks like. What maturity feels like.

Events in this phase

First cycle is short — a single feature, scoped to fit a real check date. One practice at a time. Resistance is a signal, not a verdict.

The corpus is large. A team that tries to adopt all of it at once adopts none of it. Adoption is not a project. It is a sequence of small commitments, each of which proves the previous one was worth the friction.

This part of the volume is about the practical question every team that meets the corpus eventually asks: where do we begin.

The minimum viable chain

Twenty minutes. Two practices. One cycle.

1. A prediction with a check date. Anywhere on the team's existing work — a feature already in flight is fine. Write down what we expect, what we will measure, when we will check.
2. Run the check on the date. Even if the result is we forgot to wire the metric. The act of running the check is what builds the muscle.

That is the chain. Everything else in the corpus is in service of those two acts being done well. A team that does this for three cycles in a row is already most of the way to having a chain.

Practice sequencing

Once the minimum is holding, layer the practices. The order matters — each one assumes the previous is in place.

Order	Practice	Why this one next
1	Prediction + check	The chain's spine. Without this, nothing else updates.
2	Feature Brief (one sheet)	Where the prediction lives so it doesn't drift.
3	Amigos before code	The smallest unit of shared meaning between phases.
4	Retrospective with one change	Compounding rather than listing.
5	Model update	Where the cycle's learning becomes the next cycle's starting point.
6	ADRs for constrained choices	The technical-side artifact that survives the developer leaving.
7	The full Discovery walk	Five stations. Vision through Decision.
8	Postmortem with chain levels	The structural-fix discipline.
9	Portfolio review with VRI	The view above the cycle.
10	The full corpus	Everything else, gradually.

Skipping ahead is allowed if the team is ready. Skipping the chain's spine — prediction and check — is not. Without it, nothing learns.

What resistance looks like

Resistance is not opposition. It is the team's honest signal about where the chain is asking for something the conditions don't yet support.

Common shapes, with what's actually underneath:

Resistance sounds like	What is actually true
We don't have time for amigos.	Amigos save time on the story they cover. The team has not yet seen the saving, because they have not yet held one.
Predictions are too risky to write down.	The team has been measured on getting predictions right rather than on running the check. The fix is structural — make not checked the only outcome with no value.
The clients won't let us do Discovery.	The clients have been sold execution. The fix is in the contract and the financial translation, not in the cycle.
We're too small for all this overhead.	The corpus does not require all of it. See the minimum viable chain above. The team has heard the corpus as a checklist, not a sequence.
Our work is different.	Sometimes true. Often the fix is to translate the corpus into the team's domain language, not to abandon the practices.

Resistance handled well produces a smaller, more honest version of the practice. Resistance ignored produces silence and ceremony.

What maturity feels like

A mature chain is not a busy chain. It is a quiet one.

Signs the chain is mature:

• The retro produces small changes, not big ones, because the big ones already happened.
• Postmortems are uneventful — runbooks held, structural fixes are obvious.
• Predictions land within a small distance of measured reality, more often than not.
• New people onboard quickly because the artifacts hold the knowledge.
• The portfolio review produces kill decisions occasionally, without drama.
• Leadership reads the chain artifacts and knows what is happening without asking.

Signs the chain is not yet mature:

• The retro produces a list and the list grows.
• Postmortems describe what people felt and not what changed.
• Predictions are made loosely or not at all.
• Onboarding takes months because the knowledge lives in heads.
• Kill decisions are dramatic and rare.
• Leadership is briefed in conversations rather than informed by artifacts.

Maturity is not a destination. It is a condition that has to be re-earned each cycle. The team that takes it for granted has already started losing it.

Artifact lifecycle

A corpus is not a museum. Artifacts go stale. The chain has a small, honest discipline for that.

• Every artifact has a last_reviewed date. The corpus surfaces ones over six months old.
• Deprecated artifacts are marked, not deleted. Future readers need to know the practice was tried and what replaced it.
• A lightweight track exists for changes that don't warrant the full chain — typo fixes, documentation tweaks, minor refactors. They go through CI but not through Discovery.
• The chain itself is reviewed annually. Where is friction structural? Where is the corpus describing a world that has moved?

Chain evolution

The chain is meant to change. A chain that hasn't changed in two years is either complete (rare) or asleep (common).

Chain evolution is itself a chain operation:

• A change to the chain begins as a brief — same template, witnessed problem in the team's own working life.
• It is scoped, sliced, predicted — same shape as any feature.
• It runs as a cycle — the team practices the new way for one full cycle.
• It is checked — did the change produce what we predicted?
• It joins the corpus — or it doesn't, and the artifact records why not.

The chain evolves the way features do, on itself, with the same discipline. Anything else is fashion.

Resolution gate — adoption is underway

Enough to know the chain is alive.

At least one cycle has been run with prediction + check. At least one practice from the sequencing list has been added. At least one model update has been written. The team can name what is mature, what is still draft, and what is gap.

---

End of Volume V

The cycle closes here — and reopens. The model update from this volume is the input to the next cycle's Volume II. The portfolio decision from this volume is the input to the next cycle's Volume I.

Back to the volume cover → · Back to the five volumes → · The map →