Systemic Thinking
Systemic thinking looks for the feedback loops that keep producing a result, instead of treating every new instance of the problem as a fresh, unrelated fire.
Arrows loop back on themselves, tracing how a quick fix quietly feeds the very problem it was meant to solve.
Reach for this when…
- The same problem keeps recurring despite repeated fixes.
- A quick fix worked once and now needs applying more often, for less effect.
- Nobody can explain why a change in one part of the business keeps causing surprises elsewhere.
How to run it
- Separate systemic thinking (loops and structure) from systematic thinking (steps and process).
- Start from the outcome you actually need, and work backwards to what's driving it.
- Map the causal loops - what reinforces the problem, what balances it out.
- Identify whether a loop is reinforcing (runs away) or balancing (self-correcting).
- Find the high-leverage point - usually inside a loop, rarely at the symptom itself.
A worked example
Situation. Ivan Horvat ran Jadran Cargo, a haulage and logistics firm in Split, Croatia, where late deliveries kept triggering the same fix: hire another driver.
Applied. Mapping the loop, hiring drivers faster than they could be properly trained fed a reinforcing loop - inexperienced drivers caused more delays, which triggered more urgent hiring.
Result. He paused the emergency hiring and put that budget into pairing new drivers with experienced ones instead. The loop that had been running away started balancing itself.
The catch
Causal loop diagrams are a hypothesis about structure, not a measured fact - two people can map the same system differently. Systemic thinking takes longer to reach an intervention than firefighting does, which makes it unattractive under real pressure. And a genuinely high-leverage point is often politically inconvenient to touch.
If the same fix keeps needing to happen more often for less effect, you're feeding the loop, not solving it.
Origin: Peter Senge / Donella Meadows / Jay Forrester