Recognize system archetypes: the recurring plots
Learn the handful of common structural patterns that produce the same behaviors in very different settings.
Why it works
Senge identified a set of "system archetypes" — recurring structural patterns that produce recognizable behavior, such as "fixes that fail," "shifting the burden," "tragedy of the commons," and "escalation." Once you recognize an archetype, you know what the system will do next without having to simulate it — because the structure, not the people or the context, determines the behavior. Pattern recognition at the structural level is the core competency systems thinking builds.
How to do it
- When a problem persists despite repeated fixes, ask: "Is this ‘fixes that fail’?" — a fix that relieves symptoms without addressing the root cause, which then rebounds.
- When two parties keep escalating in competition, ask: "Is this ‘escalation’?" — a reinforcing loop where each side’s increase triggers the other’s.
- When you find yourself going back to a workaround repeatedly, ask: "Is this ‘shifting the burden’?" — dependence on a symptomatic fix that grows over time.
- Name the archetype, then trace the structural fix: what would break the reinforcing loop?
Evidence
System archetypes are derived from system dynamics modeling and have been extensively documented in organizational case studies by Senge and others. They are conceptual tools rather than empirically tested intervention protocols. (mechanistic)
Archetypes are useful pattern-recognition heuristics, but any given situation may not fit neatly into one, and forcing a fit can lead to misdiagnosis.
Sources
- Senge (1990), The Fifth Discipline, Chapter 6 — system archetypes
Common mistake
Using the "escalation" archetype as an explanation that implies no solution — archetypes do not just explain behavior, they reveal the structural lever: in escalation, a unilateral de-escalation step can break the loop.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Systems Thinking
- See at three levels: event, pattern, and structure
Ask "what pattern produced this event?" and then "what structure is producing that pattern?"
- Identify the reinforcing and balancing loops
Find whether behavior is driven by amplification (R loops) or by correction toward a goal (B loops).
- Account for delays between action and effect
Identify where the time lag is between cause and consequence before you diagnose a problem.
- Find the high-leverage intervention point
Look for the structural change that produces large effects for small effort.
- Surface and test the mental models driving behavior
Make the assumptions behind decisions explicit — they are often the root structural cause.