Skip to content

Contingency Visibility Across Scales

Compare micro-level detail with macro-level aggregation so local contingency is not erased and broad structure is not ignored.

The Diagnostic Story

Symptom: Every explanation lands in one of two failure modes: the close-up account is vivid and specific but treats local actors as if structural forces did not exist, while the aggregate account smooths everything into trends that make the outcome look inevitable and erase the moments when things could have gone differently. Counterfactual debates multiply because participants are comparing claims at incompatible scales without realising it. Retrospectives end in either scapegoating or fatalism — never in both honest accountability and honest structural understanding.

Pivot: The move is to pair a micro account with a macro account explicitly, marking where they are in tension. Name the branch points at which alternatives were genuinely open, record what aggregation loses when local events become trends, and constrain counterfactuals by the scale at which they are actually plausible.

Resolution: An outcome can now be explained as contingent at the decision level and constrained at the structural level simultaneously, without contradiction. Retrospectives become more honest because stakeholders can see which local choices mattered and which macro constraints would have required deeper change to alter. Learning improves because hindsight smoothing is visible rather than invisible.

Reach for this when you hear…

[organizational postmortem] “We keep blaming the on-call engineer but the incident log shows five teams hit the same failure mode in the same month — this is a structural problem, not a people problem.”

[economic history] “The aggregate chart makes the crisis look inevitable but the archival record shows three separate decision windows where regulators had real options — we need both stories.”

[ecology] “The population collapse looks smooth on the graph but the field notes show three specific drought years where the trajectory could have bent — we are losing those branch points when we aggregate.”

Mechanisms / Implementations

  • Actor-Constraint Map
  • Aggregate Trend Overlay
  • Branch-Pruning Protocol
  • Counterfactual Sensitivity Matrix
  • Hinge-Point Timeline
  • Interpretive Weighting Memo
  • Nested Scale Timeline
  • Paired Micro/Macro Case Study
  • Scale-Shift Review Prompt
  • Source Resolution Table

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

Also references 29 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Hinge-Point Contingency Analysis · temporal variant · recognized

Focuses on specific moments where a local event or choice plausibly redirected a broader path.

Aggregation Erasure Check · scale variant · recognized

Checks which local contingencies disappear when cases are averaged, categorized, periodized, or summarized at macro scale.

Actor/Structure Contingency Balance · other · candidate

Balances actor choice, chance, and structural constraint when explaining why an outcome happened rather than a plausible alternative.

Organizational History Contingency Review · domain variant · recognized

Applies cross-scale contingency analysis to organizations, projects, incidents, restructurings, and strategic decisions.