System Health Review¶
Diagnostic review — instantiates Whole-System Alignment
Puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole.
A System Health Review is the recurring act of placing local scorecards next to whole-system outcomes to detect one specific pathology: every local board is green while the end-to-end result is red. Its defining move is periodic comparison and detection — it consumes existing metrics (a balanced scorecard among them), reroutes lagging signals so they arrive where they can change behavior, and asks "where is a local win exporting harm downstream?" It is a diagnostic ritual, not an artifact and not an authority: it finds suboptimization and names an owner for the fix, but it neither maintains the dashboards it reads nor holds the power to change a rule itself. Its entire value is turning the gap between local green and system red into a discovered, attributable finding.
Example¶
A parcel carrier's sort hubs each hit their local KPIs — packages processed per hour, dock utilization, on-time departures from the building — a wall of green. Yet the end-to-end metric that customers feel, door-to-door delivery time, is drifting red, and complaint volume is climbing. Nothing on any hub's dashboard explains it, because nothing on any hub's dashboard is about the whole.
The monthly system health review puts the hub scorecards side by side with the end-to-end delivery metric and adds a feedback path: late-delivery data that had been living in the customer-service queue is routed back to the sort hubs that generated it. An externality scan then finds the culprit — one high-volume hub hits its throughput target by deprioritizing irregular-shaped parcels, which miss their downstream connections and blow the end-to-end clock several cities away. The review does not fix the routing rule itself; it surfaces the exported harm, attributes it, and hands it to whoever owns that rule. What was invisible in a stack of green dashboards is now a named finding with an owner.
How it works¶
- Juxtapose local against whole. Deliberately pair each unit's local metrics with the end-to-end outcome they are supposed to serve, so a green-local / red-whole divergence becomes visible in one view.
- Reroute lagging signals. Move downstream and cross-boundary consequences back to the actors who caused them, closing the loop the original metrics left open.
- Scan for exported harm. Actively look for local wins achieved by shifting cost, delay, or risk across a boundary — the signature of suboptimization.
- Attribute and hand off. Flag each divergence with a probable owner and escalate; the review detects and assigns, it does not itself decide the remedy.
What distinguishes it is that it is a detection cadence over live behavior — consuming metrics and routing signals — not the artifact that holds the metrics or the body that changes the rules.
Tuning parameters¶
- Cadence — frequent reviews catch drift early but can chase noise; infrequent ones are cheaper but let harm propagate before it is seen.
- Local–whole pairing — which end-to-end outcome each local board is set against. A well-chosen pairing exposes suboptimization; a lazy one just re-shows the green.
- Feedback latency target — how quickly downstream signals must be routed back. Tighter targets act sooner but cost instrumentation; looser ones are cheap but slow.
- Externality-scan breadth — how far across boundaries the review looks for exported harm. Wider scans catch more but risk boiling the ocean each session.
- Escalation trigger — how large a divergence must be before it becomes a named finding. Set low, the review floods owners; set high, real harm hides under the threshold.
When it helps, and when it misleads¶
Its strength is catching suboptimization early and specifically — turning the vague sense that "everyone's numbers look fine but customers are unhappy" into a located, attributed finding while the harm is still cheap to reverse. It is the operations-time complement to the standing scorecard: the scorecard shows the numbers, this review reads them against the whole.
Its failure mode is watermelon reporting — boards that are green on the outside and red on the inside — where the review politely notes the local greens and never confronts the system red, becoming exactly the alignment theater the archetype warns against.[n1] The classic misuse is reviewing without any path to action, so divergences are observed month after month and never owned. The guarding discipline is to pair every red finding with a named owner and a route to a mechanism that can actually act — because detection without a handoff is just a well-documented decline.
How it implements the components¶
alignment_review_cadence— the recurring rhythm at which local metrics are placed beside whole-system outcomes and compared.feedback_path_adjustment— it reroutes downstream and lagging signals back to the local actors who generated them.externality_scan— it actively hunts for local wins achieved by shifting cost or harm across a boundary.
It does not maintain the standing balanced measurement artifact it reads (system_health_dashboard, shared_outcome_metric, local_metric_crosswalk) — that is the Balanced Scorecard; nor does it evaluate design-time interface trade-offs (part_whole_interaction_map) — that is the Systems Engineering Review, its near-name twin: this review watches running behavior over time, that one checks a design at a gate.
Related¶
- Instantiates: Whole-System Alignment — the operations-time detection that catches local wins harming the whole.
- Consumes: Balanced Scorecard — reads its balanced dashboard as the local-side input it sets against whole-system outcomes.
- Sibling mechanisms: Shared OKRs or Cross-Functional Goals · Systems Engineering Review · Integrated Planning Process · Cross-Silo Governance Forum · Ecological Management Plan · Patient Care Team Conference
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: System Health Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole.
Independent corroboration: The frozen evidence defines System Health Review as 'Puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Monitoring, Sensing & Alerting — System Health Review includes features of ongoing observation, sensing, or alerting that detects and surfaces state without itself executing the response, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Systems Thinking & Cybernetics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: System health review derives most directly from systems science's feedback, stock-flow, boundary, and regulation tradition; its defining operation is to puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole.
Related originating lineages:
- Engineering & Design — Engineering's design, reliability, interface, and lifecycle tradition provides a formative adjacent lineage for the same system health review operation.
- Medicine & Healthcare — Clinical medicine, public health, and recovery practice supplies a parallel or contributing lineage for the mechanism's defining operation: puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole.
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole.
Review resolution: Both blind reviewers independently select systems_cybernetics as the primary historical origin for the concrete operation—Puts local scorecards next to whole-system outcomes on a cadence to catch local wins that quietly harm the whole. The queued differences concern alternate origin disagreement, origin mode disagreement, domain reach disagreement, not the primary lineage. I retain every alternate that either reviewer explains, without a numeric cap, and choose origin_mode=cross_disciplinary_synthesis because the reviewers' combined evidence identifies material construction from multiple disciplines. domain_reach=universal records later portability rather than multiplying historical origins; confidence=medium is the conservative shared evidentiary level, and encyclopedia_synthesis=true preserves either reviewer's affirmative synthesis finding.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
The sharpest confusion is with Systems Engineering Review: the names rhyme, but the two never overlap in practice. That one interrogates a design against requirements before build; this one watches live behavior against outcomes after deployment. Design-time versus operations-time is the whole difference.
[n1] Watermelon reporting — an informal industry term for status dashboards that show green on the surface while the underlying reality is red, usually because local indicators are reported without being set against the end-to-end outcome. Naming it is a reminder that a review's job is to cut the melon open, not admire its rind. ↩