Whole-System Impact Map¶

Consequence-mapping artifact — instantiates Migration-Resistant Hazard Control

Lays a control's full field of consequences — direct, indirect, delayed, and cross-boundary — on one artifact, so a local win can be netted against the system-wide effect that hides the displaced burden.

A Whole-System Impact Map lays out the full field of consequences of a control or change — direct and indirect, immediate and delayed, on-boundary and cross-boundary, across every stakeholder — on a single artifact. Its distinguishing job in this archetype is to net a local win against its system-wide effect: by drawing the consequences that fall outside the acting unit, it lets a claimed success be checked against what happens two and three steps away, where a displaced hazard lands. Where a mass balance counts one conserved quantity and a fault tree traces one failure, the impact map is deliberately broad — its value is catching the delayed, indirect, cross-boundary consequence that no single-metric view is even looking at.

Example¶

A general hospital, under budget pressure, plans to close its inpatient psychiatric ward; its own dashboard shows the move as a clear saving and a shorter average length of stay. A whole-system impact map is drawn before the decision, extending past the hospital's ledger. Immediate and direct: beds and cost removed. One step out: patients in crisis now present to the emergency department and board there for days; police become the de-facto first responders for mental-health calls; the county jail's population of unwell people rises. Delayed: more readmissions to other hospitals, more strain on families and community clinics. Laid on one canvas, the map enables the crosscheck the dashboard cannot: the hospital's local metric improved, but the burden did not disappear — it moved to the ED, the police, the jail, and neighbouring providers. The saving is real within the boundary and largely displaced across it, and the map is what makes that comparison visible.

How it works¶

Extend past the acting unit's ledger. The map's discipline is to keep drawing consequences after they cross the boundary where the deciding unit stops counting.
Cover the four kinds of consequence. Direct/indirect and immediate/delayed — the displaced burden usually hides in the indirect-and-delayed quadrant.
Attach each consequence to a stakeholder. Naming who inherits each effect turns a diffuse "externality" into a specific, addressable destination.
Net local against system. Place the deciding unit's own metric beside the system-wide picture so the two can be compared rather than conflated.

Tuning parameters¶

Breadth (hops out) — how many steps of indirect consequence to follow. Too few misses the destination; too many makes everything connect to everything.
Time horizon — how far delayed effects are chased. Short horizons flatter interventions whose harm is lagged.
Stakeholder set — whose consequences count. Omitting the party that inherits the burden is how a map launders displacement.
Evidence grading — whether links are marked evidenced versus plausible. Without it, a speculative harm and a measured one carry equal visual weight.
Quantified vs. qualitative — whether effects are sized or merely named. Sizing sharpens the crosscheck but invites false precision on soft links.

When it helps, and when it misleads¶

Its strength is that it is the widest-angle lens in the set, and the only one whose explicit purpose is to net a local success against its whole-system consequences — surfacing the delayed, indirect, cross-boundary harm that a single metric is structurally blind to.

Its failure mode is that breadth is also its weakness. Everything connects to everything, so an unbounded map drowns in speculative links and can be used to manufacture either a comprehensive-looking blessing or an endless objection; left unquantified, it cannot say which displaced effect actually dominates. Its classic misuse is selective scope — drawing in only the consequences that flatter (or only those that damn) the decision. The discipline is to fix the boundary and stakeholder set before the analysis, to grade links by evidence, and to treat the cross-boundary consequences as externalities to be counted rather than assumed away.^[1]

How it implements the components¶

whole_system_impact_map — the artifact itself: direct, indirect, delayed, and cross-boundary consequences laid on one canvas.
local_vs_system_outcome_crosscheck — placing the acting unit's own metric beside the system-wide picture is the crosscheck that catches a displaced "win."

It does not measure these consequences over time — that instrumentation is Before–After–Elsewhere Evaluation — nor does it enforce a single conserved unit of account across the boundary, which is Mass Balance.

Instantiates: Migration-Resistant Hazard Control — the map supplies the system-wide picture a local outcome must be checked against.
Consumes: Causal Loop Diagram — the migration field that tells the map which destinations to trace consequences toward.
Sibling mechanisms: Before–After–Elsewhere Evaluation · Causal Loop Diagram · Fault Tree Analysis · Mass Balance · Hazard Analysis · Adaptive Circumvention Red Team · Agent-Based Experiment or Simulation · System-Wide Net-Risk Dashboard · Boundary Expansion Review · Cross-Boundary Hazard Ledger · Cross-Jurisdiction Incident Review · Intervention Displacement Stress Test · Migration Sentinel Network · Pressure-Absorption Redesign Workshop · Source-Reduction or Safe-Dissipation Plan

References¶

[1] An externality is a cost (or benefit) that falls outside the boundary of the actor who created it. Migration of a hazard across a boundary is precisely the creation of a negative externality, which is why the impact map's core discipline is to keep drawing past the acting unit rather than stopping at its ledger. ↩