Use this when the same problem keeps returning despite repeated fixes — when growth stalls for reasons nobody can articulate, when well-intentioned interventions make things worse, or when teams are trapped in patterns they can feel but can't name. System archetypes are recurring structural patterns that show up across industries, scales, and centuries. Learn eight to ten of them and you'll start recognising the architecture of dysfunction before it fully manifests.
Section 1
What This Tool Does
A startup scales aggressively, hiring fast to meet demand.
Quality drops. Customers churn. The company hires faster to replace lost revenue. Quality drops further. Everyone works harder. Nobody asks why working harder keeps making things worse. A city builds a new highway to relieve congestion. Traffic improves for eighteen months. Then it's worse than before — the new capacity induced new demand, and now there's a wider highway full of more cars. A pharmaceutical company discovers that its blockbuster drug is losing market share. It increases the sales force. Margins compress. It cuts R&D to protect margins. Five years later, there's no pipeline. The sales force has nothing new to sell.
These aren't three different problems. They're the same problem wearing different costumes. Peter Senge, drawing on decades of system dynamics work at MIT — Jay Forrester's pioneering simulations, Donella Meadows' leverage point analysis, the modelling tradition that stretches back to the 1950s — codified roughly a dozen recurring structural patterns in
The Fifth Discipline in 1990. He called them system archetypes. Each one describes a specific configuration of feedback loops, delays, and unintended consequences that produces a characteristic behaviour over time. Fixes that Fail. Shifting the Burden. Limits to Growth.
Tragedy of the Commons. Escalation. Success to the Successful. Eroding Goals. Growth and Underinvestment. The names are plain because the patterns are universal.
The mechanism is pattern recognition at the structural level. Most diagnosis operates on events — what happened, who did what, what went wrong last quarter. Slightly better diagnosis operates on trends — the error rate has been climbing for six months. System archetypes operate on the level of structure: the arrangement of feedback loops, delays, and incentives that generates those trends and events. This is the cognitive shift. You stop asking "what happened?" and start asking "what structure would produce exactly this pattern of behaviour?" Once you identify the archetype, you inherit decades of accumulated knowledge about where the leverage points are — and, critically, where the obvious interventions will backfire.
The reason human intuition fails here is that most systemic structures contain delays and feedback loops that make cause and effect non-obvious. The action that caused the problem may have occurred months or years ago. The intervention that feels most urgent — hire more people, cut costs, add capacity — often reinforces the very dynamic it's trying to fix. Senge's archetypes are a library of these traps. They function like a diagnostic manual: you observe the symptoms, match them to a known pattern, and the pattern tells you both why your current approach isn't working and what a structural intervention would look like. You don't have to derive the system dynamics from scratch every time. Someone has already mapped the territory.
The practical power is in the speed of diagnosis. A team that knows the archetypes can look at a deteriorating situation and say, within minutes, "This is Shifting the Burden — we're treating the symptom with a quick fix that's atrophying our capacity to address the fundamental problem." That sentence, spoken in a meeting, changes the entire conversation. It moves the group from arguing about tactics to examining structure. That's the whole trick.
