Readiness Gate Scorecard without Averaging¶
Metric or dashboard — instantiates Necessary-Condition Closure Design
Displays condition status without collapsing hard blockers into a composite score.
A Readiness Gate Scorecard without Averaging displays the status of every necessary condition side by side against the success predicate, with an ironclad rule that hard conditions are never rolled up into a composite score. Its identity is honest non-aggregation: a single red or unknown condition keeps the whole gate red no matter how many greens surround it, and "unknown" is shown as its own state, never quietly counted as a pass. Where a limiting-factor board spotlights the one binding condition, the scorecard's job is the opposite — keep the entire conjunction visible so nothing can hide inside an average.
Example¶
An intensive-care unit uses a Readiness Gate Scorecard to decide whether a patient is safe to transfer to a general ward. The criteria are hard and conjunctive: stable vitals off pressors, adequate oxygenation on ward-appropriate support, a secured airway plan, pain controlled, and a receiving bed with the right monitoring. A tempting "readiness score" might read the patient as 90% ready and move them. The scorecard refuses to average: oxygenation is still "unknown" pending a repeat blood gas, so the gate stays red on that one row even though everything else is green. Displaying readiness this way is a non-compensatory[n1] rule — a strong score on four criteria cannot compensate for one unresolved requirement — and it keeps the missing gas from being smoothed into a comfortable aggregate.
How it works¶
One row per necessary condition, each with an explicit status — green, red, or unknown, and never a blended number. The gate's overall state is the logical AND of the rows, so it reads green only when every row is green. Unknown and waived are shown as distinct non-green states rather than folded into the green count. The display's central discipline is that no widget anywhere collapses the rows into a single percentage that could let one red disappear.
Tuning parameters¶
- Status vocabulary — binary (met / not) versus richer (met / at-risk / unknown / waived). Richer vocabularies inform better but must still resist collapsing to a number.
- Unknown handling — whether "unknown" is visually equated with "red" or given its own treatment. Its own color preserves information; equating it with red is more conservative.
- Gate scope — one predicate per scorecard versus nested sub-gates. Nesting handles complex outcomes but reintroduces roll-up temptation at each level.
- Refresh source — manual attestation versus a feed from live evidence. Live feeds stay current; manual entry risks staleness.
When it helps, and when it misleads¶
Its strength is that it is the direct structural cure for aggregate-readiness masking, the archetype's most common failure; anyone glancing at it sees the AND-gate, not a flattering average. Its failure mode is green-sea complacency, where a wall of green trains people to stop reading individual rows, so a lone red gets rubber-stamped — and it shows status without telling anyone what to do about a red. The guarding discipline is to make reds and unknowns visually loud, to require that the single red be addressed rather than overridden by a glance at the surrounding greens, and to route reds to a decision process rather than leaving the scorecard to imply one.
How it implements the components¶
success_predicate— the scorecard is defined against one stated outcome; the gate reads green only when the conjunction backing that predicate holds.necessary_condition_set— it shows the complete hard set, one visible row each, never collapsed.condition_evidence_record— each row's status reflects that condition's current evidence, with "unknown" honestly shown rather than colored green.
It does not identify or remediate the single binding condition (weakest_condition_margin, limiting_factor_remediation_path) — that bottleneck-and-fix focus is its dashboard twin Limiting-Factor Board; the scorecard instead shows all conditions at once, refusing to average any of them away.
Related¶
- Instantiates: Necessary-Condition Closure Design — it is the display form that keeps the AND-gate visible.
- Consumes: All-Conditions Checklist supplies the condition set whose live status it displays.
- Sibling mechanisms: All-Conditions Checklist · Blocker Register · Condition Coverage Test Suite · Dependency Closure Map · Go/No-Go Condition Review · Limiting-Factor Board · Preflight Review · Red-Team Precondition Challenge · Weakest-Link Postmortem
Editorial Notes¶
Form Classification¶
Form family: Interface, Display & Cue
Rationale: Readiness Gate Scorecard without Averaging operates as a user-facing prompt, display, template, or perceptual cue that shapes attention and action at the point of use because it displays condition status without collapsing hard blockers into a composite score.
Independent corroboration: The frozen evidence defines Readiness Gate Scorecard without Averaging as 'Displays condition status without collapsing hard blockers into a composite score', so its operative form is Interface, Display & Cue.
Nearest alternative: Decision, Gate & Allocation — Readiness Gate Scorecard without Averaging includes features of a case-specific gate, selection, routing, prioritization, or resource disposition, 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: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Conjunctive entrance and success criteria that prevent a strong dimension from compensating for a blocker are characteristic systems-engineering readiness-gate practice, with management and decision analysis contributing governance and scoring.
Related originating lineages:
- Operations Research — Constraint logic supplies the noncompensatory treatment of hard blockers.
- Organizational & Management Science — Program scorecards provide the visible governance artifact.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of engineering_design: Conjunctive entrance and success criteria that prevent a strong dimension from compensating for a blocker are characteristic systems-engineering readiness-gate practice, with management and decision analysis contributing governance and scoring. The rejected primary is retained only when it materially shaped the mechanism, and present-day breadth is recorded separately as domain_reach=multi_domain.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] A non-compensatory decision rule is one in which a high value on one attribute cannot make up for a failing value on another — the opposite of a compensatory (weighted-average) model, where strengths and weaknesses trade off. ↩