18. Rollout Sequence: Triage Then System

Friday, 11:12 a.m., customer presentation already on the projector, someone still writing "full rollout — week one" on the shared doc.

The program is already behind, with unresolved blockers accumulating every cycle.

Someone proposes a full OS rollout with new templates, role changes, and weekly governance meetings starting immediately.

That sequence usually collapses adoption before controls stabilize.

Start with triage, not broad transformation

When a program is unstable, first objective is to stop bleed rate:

  • unresolved decision pileup,
  • truth-state contradictions,
  • late risk discovery,
  • blocked dependencies with no owner.

Do not launch 20 controls at once.

Install the minimum loop that restores decision quality.

Triage phase (first 2-4 weeks)

Timebox triage and keep it narrow.

Core controls:

  1. ownership map for top active decisions,
  2. one-page truth on fixed cadence,
  3. risk register with named owners and triggers,
  4. gate output discipline (decision/owner/date/artifact delta).

If these four controls stay stable for two cycles, leaders can shift from firefighting to planned execution.

Entry/exit criteria

Define triage done criteria before starting:

  • top decision backlog reduced below the threshold declared at triage start,
  • one-page and source records aligned for two consecutive cycles,
  • escalation path functioning with response SLA,
  • no unresolved "which value is live" conflicts on critical threads.

Without exit criteria, triage becomes permanent emergency mode.

System phase (after triage)

Once stable, layer deeper controls:

  • requirement lifecycle rigor,
  • technical evidence loops,
  • supplier capability discipline,
  • training and cadence for durability.

Sequence matters: stabilize triage controls before layering system controls.

System controls without triage stability feel like overhead and trigger resistance.

Common rollout mistakes

  • launching policy before proving value on one thread (no documented evidence package from a first-thread pilot in the rollout log),
  • adding templates without owner behavior change (template completion rate rising while decision closure time unchanged),
  • measuring activity count instead of decision quality (rollout metric is document count or meeting attendance, not closure rate or surprise rate),
  • ignoring local context and forcing one-size sequence (single triage plan applied identically across programs with different distress patterns).

Each mistake lowers trust in the OS.

Adoption metric that matters

Track behavior change, not document count:

  • decision closure time (timestamp delta between decision logged and decision closed in the decision log),
  • late surprise rate (count of risk register additions made after the last gate without prior flagging),
  • one-page/record mismatch rate (comparison of one-page status to source record at weekly cadence),
  • reopen rate on closed decisions (count of items returned to open status in the decision log).

If these are improving, adoption is real.

Six programs, one rollout, eight weeks. Every program manager had the new templates. Every weekly status included the required artifact fields. By week six, template completion was above 90% across all six programs.

Decision closure time was unchanged. Late surprise rate was unchanged. One team had started filling in the prior week's templates retroactively to show compliance. Another was holding weekly governance meetings and closing them with no decisions recorded. The rollout had produced activity, not adoption.

The team stopped the six-program effort and ran a triage pass: which two programs had the worst unresolved decision backlogs? Those two received the four-control minimum — ownership map, one-page truth, risk register with named owners, gate output discipline — with no additional templates, no governance overhead, no role redesign. Exit criteria were predeclared before work started: two consecutive cycles with decision backlog below the opening count, one-page and source records aligned. Four weeks later, both programs met the exit criteria. The team documented the evidence package and used it with the next two programs. Those programs asked to join; the prior two were visible, auditable proof the sequence worked.

  • Old process: simultaneous rollout to six programs with full template sets, role changes, and governance meeting requirements; no predeclared exit criteria; adoption measured by template completion rate.
  • Artifact changed: a triage sequencing plan applied to the two highest-pain programs first — four core controls, no additional overhead, exit criteria predeclared at triage start, adoption measured by decision closure time and late surprise rate rather than template fill rate.
  • Measured improvement: two programs met adoption exit criteria in four weeks; the next two programs onboarded without a mandate, using the first two as a working model.
  • Cost of the gap: eight weeks of parallel rollout effort produced 90% template completion and zero improvement in decision quality — full restart required, and the compliance-theater period eroded team trust in the OS before the real rollout began.