Skip to content

Chain Maturity Assessment

A mature chain is quiet, not busy. The practices are habitual. The artefacts are automatic. The conversations are shorter because the shared vocabulary is already there. Maturity is invisible discipline — not visible process.

Owners: PO, Leadership, Tech Lead Phase it lives in: After We Build (Volume V) The corpus principle this enacts: Five volumes of invisible discipline, not five volumes of visible process.

Where it lives in the chain

How to assess

Read the chain by what the team does by reflex, not by what they describe in meetings:

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 artefacts hold the knowledge.
  • The portfolio review produces kill decisions occasionally, without drama.
  • Leadership reads the chain artefacts 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 artefacts.

What good assessment looks like

A leader who wants to know whether the chain is healthy does not ask the team how things are going. They read the last cycle's signal reading, the last postmortem, and the current model file. If the signal reading is short and specific, the postmortem produced a structural fix, and the model file has new evidence — the chain is alive. If any are missing or padded, the chain has a gap that the team is currently performing around.

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.

200apps · How We Work · NWIRE