Interactive graph
Systems Thinking
Table of Contents
Trace the loop behind the fire - inputs, delays, feedback - and fix the process, not tonight's patch.
Key Concept
- Systems thinking traces inputs, delays, and feedback behind the symptom.
- Level 1: Look past the visible problem - ask what feeds it, what slows it, and what keeps it coming back.
- Level 2: Symptoms flare in the open; systems thinking traces inputs, delays, and feedback loops behind the fire.
- Level 3: Patching tonight's symptom fails when the same fire returns next week - the loop that produces the fire is the real target.
- Level 4: Before the next fix, map one input and one feedback path that could be restarting the problem.
- Level 5: Delays hide cause from effect - trace feedback before you celebrate a quiet week; same lens as Normalization of Deviance when the loop still runs.
- Change the process that keeps producing the fire - do not only patch tonight's symptom.
- The same fire coming back next week is the tell you patched the symptom and left the loop untouched.
Examples
- We lost every third possession on turnovers - systems thinking traced it to the warmup drill, not “focus harder tonight.”
- The restaurant ran out of rice on a busy Friday - systems thinking traced it to prep checklist and par levels, not “cook faster tonight.”
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| contradicts | Low Hanging Fruit | when patching the symptom beats fixing the loop that keeps producing it |
| extends | Continuous Improvement | Loop fixes are small upgrades repeated |
| extends | People-Centered Design | Fix the loop humans actually run - not only the chart |
| extends | Process Over Outcomes | Trust the repeatable loop, not one heroic save |
| extends | Second-Order Thinking | Second moves and side effects are part of the system |
| implements | Systems for Growth | Growth hub indexes the loops this lens is for |
| implements | Transformation Principles | Systems lens lever the transformation hub indexes |
