Scoring launch readiness without losing the audit trail

The problem

Launch readiness was reported as narrative status. Each function described its own progress in its own terms, which masked the dependencies between them — content waiting on evidence, systems waiting on training, governance waiting on all three.

What we did

Created a six-domain scorecard where every score had to point at objective evidence, with published threshold definitions, named milestone owners, and a cross-domain dependency log that made one function’s blocker another’s risk.

What changed

Readiness improved from 61% to 82%. Three red dependencies were escalated, and the executive committee approved targeted recovery actions against them rather than a general instruction to go faster.

How it was measured

Each domain score is the proportion of its threshold criteria met, with a link to the evidence for every criterion. The overall figure is the unweighted mean of the six domains — deliberately not weighted, so no domain can be argued down.

Artifacts

Launch scorecard · risk register · dependency log · launch-readiness deck