Readiness Scorecard¶
Readiness dashboard / decision-support artifact — instantiates Transition Readiness Assessment
Rolls every readiness criterion onto one visible board — each rated, evidence-backed, confidence-tagged, and severity-scored — so a decision-maker sees the whole readiness picture and its worst gaps at a glance.
A Readiness Scorecard is the aggregation artifact of the archetype: it renders the full set of readiness criteria on one visible board, each carrying its rating, the evidence behind it, a confidence tag, and a gap-severity score. Its distinctive property is making the whole picture legible at once — it does not decide and does not reduce anything to pass/fail; it preserves the gradations a checklist throws away (how ready, on what evidence, how sure) and arranges them so the worst gaps stand out. Where the Preflight Checklist collapses each item to yes/no, the scorecard keeps the nuance a real go decision has to weigh.
Example¶
A carmaker is preparing to start volume production of a new model. Its readiness scorecard carries one row per criterion: tooling qualified, supplier quality submissions approved, pilot-build defect rate, line cycle-time achieved, operator training complete, containment plan ready. Each row shows a red/amber/green rating, a link to its evidence (a test report, a supplier submission), a confidence level, and a gap-severity score.
The board reads mostly green — but one supplier's quality submission is red, with high severity (a safety-critical brake component) and low confidence (the data is a week stale). A naive overall roll-up would have averaged that into a comfortable "amber, basically ready." The severity-weighted view does the opposite: it makes the single red the most salient thing on the board. The scorecard does not call go or no-go; it hands the decision-maker a picture in which the one gap that could sink the launch cannot be averaged away, and routes attention to the brake supplier before the start-of-production decision is made.
How it works¶
- One row per criterion, never a bare colour. Each carries rating and evidence link and confidence and gap severity, so a status can always be interrogated.
- Preserve gradations. The point is to show how ready and how sure — the nuance a binary check discards.
- Severity-weight the gaps. Roll-up favours worst-of or severity-weighting over blind averaging, so one critical red is not laundered into a comfortable amber.
- Keep it traceable. Every rating clicks through to its evidence, so a green can be challenged rather than trusted on faith.
Tuning parameters¶
- Rating granularity — binary, red/amber/green, or a numeric scale. Finer shows nuance but invites false precision and rating drift; coarser is legible but blunt.
- Aggregation rule — how row ratings roll into an overall: average, worst-of, or severity-weighted. Averaging hides a fatal red; worst-of over-stalls on a trivial one; severity-weighting is the usual compromise.
- Confidence dimension — whether each rating also carries how sure it is. Separating "green but low-confidence" from "green and proven" stops thin or stale evidence from reading as safe.
- Evidence linkage depth — whether ratings must link to source evidence or may be asserted. Linked is auditable but heavier to maintain.
- Refresh cadence — live-updating versus a snapshot at the gate. Live avoids stale greens but costs upkeep.
When it helps, and when it misleads¶
Its strength is turning a sprawling, multi-owner readiness state into one legible picture and — when severity-weighted — keeping the single fatal gap from disappearing into an average. Because each rating ties to evidence, a suspicious green can be challenged rather than accepted.
Its failure mode is "watermelon" status — green on the surface, red inside — when ratings are optimistic or blindly averaged, and false precision when a colour or number stands in for thin evidence. The classic misuse is managing the colour instead of the readiness: tuning ratings to show green for the gate, or assembling the board after the decision to justify it. The discipline that guards against this is to separate confidence from rating, use worst-of or severity-weighting rather than averaging, require evidence links, and treat the scorecard as decision support — never the decision itself.[n1]
How it implements the components¶
precondition_evidence— each row binds a criterion to its supporting evidence, rating, and confidence, so the board is a legible ledger of what has actually been demonstrated versus merely claimed.gap_analysis— it scores and severity-weights the unmet criteria, surfacing which gaps are worst and how far short they fall, so "not ready" becomes a ranked map rather than a single verdict.
It does not define the must-have criteria or make the binary go/no-go call — that is the Preflight Checklist; it names no cross-functional owners (the Launch Readiness Review) and checks no day-2 operability (the Operational Readiness Review). Turning a gap into a fix is a Gap Remediation Plan, and the proceed / delay / abort decision belongs to the Go / No-Go Meeting.
Related¶
- Instantiates: Transition Readiness Assessment — the artifact that makes the whole readiness picture, and its worst gaps, legible at a glance.
- Consumes: the Preflight Checklist and the readiness reviews supply the per-criterion results this board rolls up.
- Sibling mechanisms: Preflight Checklist · Launch Readiness Review · Operational Readiness Review · Go / No-Go Meeting · Phase-Gate Review · Gap Remediation Plan · Readiness Scorecard variants in a Clinical Discharge Readiness Check
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: Readiness Scorecard operates as a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use because it rolls every readiness criterion onto one visible board — each rated, evidence-backed, confidence-tagged, and severity-scored — so a decision-maker sees the whole readiness picture and its worst gaps at a glance.
Independent corroboration: The frozen evidence defines Readiness Scorecard as 'Rolls every readiness criterion onto one visible board — each rated, evidence-backed, confidence-tagged, and severity-scored — so a decision-maker sees the whole readiness picture and its worst gaps at a glance', so its operative form is Interface, Display & Cue.
Nearest alternative: Representation, Specification & Plan — Readiness Scorecard includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Evidence-backed multi-criterion readiness scorecards are a program and change-management governance artifact.
Related originating lineages:
- Engineering & Design — Risk and assurance engineering contributes blocker severity and evidence discipline.
Review resolution: Both blind reviewers agree that organizational_management is the primary origin. Explicit reconciliation of alternate origin disagreement adopts reviewer_b's classification because evidence-backed multi-criterion readiness scorecards are a program and change-management governance artifact. The resulting lineage records alternates=engineering_design, origin_mode=cross_disciplinary_synthesis, and domain_reach=multi_domain; these describe formative provenance separately from later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
The scorecard is decision support, not the decision, and its gravest sin is being managed to green. Because it aggregates, it can hide a fatal gap the instant averaging replaces severity-weighting — so its whole value hangs on preserving the one red, not on the reassuring colour of the overall roll-up.
[n1] Technology Readiness Levels — the 1–9 maturity scale originated at NASA and adopted by the US Department of Defense and others — are a real example of rating a readiness criterion on a defined, evidence-anchored ladder rather than on subjective confidence; a readiness scorecard often expresses individual criteria in such terms. ↩