// Recognize Senge's Systems Archetypes to diagnose recurring organizational and technical problems, identify why fixes keep failing, and design interventions that address root structure.
| name | thinking-archetypes |
| description | Recognize Senge's Systems Archetypes to diagnose recurring organizational and technical problems, identify why fixes keep failing, and design interventions that address root structure. |
Systems archetypes, developed by Peter Senge in "The Fifth Discipline," are recurring patterns of behavior in organizations and systems. Like design patterns in software, once you recognize them, you see them everywhere—and more importantly, you can predict where they lead and intervene effectively.
Core Principle: Most organizational problems aren't unique. They follow predictable patterns with predictable consequences. Recognizing the pattern reveals the leverage points.
Decision flow:
Problem keeps recurring despite fixes? → yes → APPLY ARCHETYPES
Growth hit invisible ceiling? → yes → APPLY ARCHETYPES
Competition escalating destructively? → yes → APPLY ARCHETYPES
Shared resource degrading? → yes → APPLY ARCHETYPES
Pattern: A quick fix addresses symptoms but creates side effects that eventually make the original problem worse.
Problem
│
▼
┌─────────────┐
│ Quick Fix │──────────────┐
└─────────────┘ │
│ │
▼ │
Symptom Relief │
(short-term) │
▼
Unintended
Consequence
│
│ (delay)
│
▼
Problem
Worsens
Recognition Signs:
Software Examples:
Leverage Points:
Pattern: A symptomatic solution is used instead of a fundamental solution, reducing pressure to address the real problem and creating dependency.
Problem Symptom
┌─────┴─────┐
▼ ▼
┌──────────┐ ┌──────────────┐
│Symptomatic│ │ Fundamental │
│ Solution │ │ Solution │
└────┬─────┘ └──────┬───────┘
│ │
│ (quick) │ (slow, hard)
│ │
▼ ▼
Relief + Actual
Dependency Resolution
│
▼
Fundamental
Solution Atrophies
Recognition Signs:
Software Examples:
Leverage Points:
Pattern: A reinforcing loop drives growth, but eventually encounters a balancing constraint that slows or stops growth.
┌───────────────────────────────────┐
│ │
▼ │
Growing ────(+)────▶ Results
Action │
│
│
┌────────────────────┘
│
▼
┌───────────┐
│ Limiting │
│ Condition │
└─────┬─────┘
│
│ (-)
▼
Slowing
Action
Recognition Signs:
Software Examples:
Leverage Points:
Pattern: Individuals gain by using a shared resource, but collective overuse depletes the resource for everyone.
┌──────────────┐ ┌──────────────┐
│ Actor A's │ │ Actor B's │
│ Activity │ │ Activity │
└──────┬───────┘ └──────┬───────┘
│ │
│ (individual gain) │ (individual gain)
│ │
▼ ▼
┌────────────────────────────────┐
│ Shared Resource │
│ (depletes over time) │
└────────────────────────────────┘
│
│ (delay)
▼
Resource Degradation
Affects All Actors
Recognition Signs:
Software Examples:
Leverage Points:
Pattern: Two parties perceive their success as relative to each other. Each side's actions provoke response, leading to escalating competition that harms both.
┌─────────────┐ ┌─────────────┐
│ Actor A │ │ Actor B │
│ Action │ │ Action │
└──────┬──────┘ └──────┬──────┘
│ │
│ ┌───────────────┐ │
└────▶│ Relative │◀─────┘
│ Standing │
└───────────────┘
│
│ (perceived threat)
┌─────────────┴─────────────┐
▼ ▼
A Increases B Increases
Action Action
│ │
└───────────────────────────┘
(cycle repeats)
Recognition Signs:
Software Examples:
Leverage Points:
Pattern: If success gives access to more resources, initial advantages compound while others are starved, creating winner-take-all dynamics.
┌─────────────┐ ┌─────────────┐
│ Actor A │ │ Actor B │
│ (initial │ │ (initial │
│ success) │ │ struggle) │
└──────┬──────┘ └──────┬──────┘
│ │
▼ ▼
More Resources Fewer Resources
Allocated to A Allocated to B
│ │
▼ ▼
A More Likely B Less Likely
to Succeed to Succeed
│ │
└───────────────────────────┘
(cycle compounds)
Recognition Signs:
Software Examples:
Leverage Points:
Pattern: Growth approaches a limit that could be addressed by investment in capacity, but the investment isn't made until performance degrades, triggering a crisis.
Demand
│
│ (grows)
▼
┌───────────┐
│ Capacity │ (fixed or slowly growing)
└───────────┘
│
│ (demand > capacity)
▼
Performance
Degradation
│
│ (finally triggers)
▼
Investment
Decision
│
│ (but with delay)
▼
Capacity
Increase
(too late, crisis already happened)
Recognition Signs:
Software Examples:
Leverage Points:
Document what's happening without blame:
Draw the causal connections:
Compare your map to the seven patterns:
| If You See... | Consider Archetype |
|---|---|
| Fix that makes problem worse over time | Fixes That Fail |
| Workaround becoming dependency | Shifting the Burden |
| Growth hitting invisible ceiling | Limits to Growth |
| Shared resource degrading | Tragedy of the Commons |
| Competitive spiral harming both sides | Escalation |
| Winner-take-all resource dynamics | Success to the Successful |
| Reactive investment after crisis | Growth and Underinvestment |
Don't push on the obvious—find where small changes have large effects:
Target the structure, not the symptoms:
| Archetype | Pattern | Key Question |
|---|---|---|
| Fixes That Fail | Quick fix creates long-term problems | "What side effects will this create?" |
| Shifting the Burden | Dependency on symptomatic solutions | "What capability are we not building?" |
| Limits to Growth | Reinforcing loop hits constraint | "What will limit us at 10x?" |
| Tragedy of the Commons | Individual gain depletes shared resource | "Who owns the long-term health?" |
| Escalation | Competitive loop worsens both | "Can we change the game?" |
| Success to the Successful | Winner-take-all dynamics | "Are we starving future successes?" |
| Growth and Underinvestment | Capacity lags demand until crisis | "What fails at 50% growth?" |
"Structures of which we are unaware hold us prisoner. Once we can see them, they no longer have the same hold on us."
Recognizing the archetype is the first step to escaping it. The pattern will continue until someone sees it and changes the underlying structure—not the behaviors, but what's driving them.
Update beliefs systematically based on new evidence using probabilistic reasoning. Use when estimating probabilities, learning from data, or making decisions under uncertainty.
Apply Herbert Simon's Bounded Rationality and satisficing to make good-enough decisions under real-world constraints. Use for design decisions under time pressure, recognizing cognitive limits, and setting appropriate stopping criteria.
Know the boundaries of your expertise and operate within them. Use when evaluating opportunities, making decisions outside your domain, or assessing when to defer to experts.
Classify problems by complexity domain (clear, complicated, complex, chaotic) and match approach to domain. Use for choosing methodologies, problem framing, and process design.
Systematic checklist to identify and counteract cognitive biases in decision-making. Use before major decisions, when evaluating recommendations, or when stakes are high.
Apply Kahneman's Dual-Process Theory to recognize when to trust intuition vs engage deliberate analysis. Use for high-stakes decisions, error-prone contexts, or when balancing speed vs accuracy.