Systems Thinking
Seeing the loops, so you change the structure instead of the symptom.
The behaviour, in one line: I think through second- and third-order effects and feedback loops before I change something.
A thermostat holds a room steady, and no single part of it is doing that — the heater on its own would cook you. The behaviour comes from the loop, and from how long the sensor takes to notice. Most of what you want to change at work is a loop, not a part.
Most problems do not sit still to be solved. They sit inside loops, with delays, where an output comes back round as an input and cause and effect end up far apart in time. Push on one part and the pressure comes out somewhere else, usually later, usually to someone who was not in the meeting. Systems thinking is looking at the structure that keeps producing the problem rather than at the problem. Software has wired the loops tighter. A metric on a dashboard changes behaviour that changes the metric, a recommendation feeds the taste it was trained on, an automation removes the delay that used to give someone time to notice. There are more loops than there were, and they run faster than the meeting cycle.
| What it is | What it isn’t |
|---|---|
| Changing the structure | Fixing the instance |
| Asking “and then what?” | Asking “did it work?” |
| Expecting the delay | Judging on the immediate result |
| Pressure traced to where it went | Pressure assumed to have gone |
What it looks like. Support tickets spike, so the obvious move is more support. Instead you look at where the tickets come from, find one confusing screen in signup, and fix that. Ticket volume falls for reasons that never show up anywhere in the support numbers.
- The fix that creates the next problem. Speed up one team and the bottleneck moves to the next one. If nobody traced it, the second team looks like it got worse on its own.
- Any target attached to a number. People optimise what is measured, including in ways you did not intend. That is a loop, and it is entirely predictable if you look for it.
- Incidents that keep recurring. The same outage in different clothes means the structure is producing it. Fixing instances forever is a choice, usually an unexamined one.
- Ask “and then what?” three times. Most of the damage comes from stopping after the first answer.
- Find where an output comes back round as an input. That loop, rather than any single part, is what sets the behaviour.
- Look for the delay. When cause and effect are weeks apart, people reliably blame the wrong thing.
- Treat a quick fix that moves the pressure elsewhere as a cost rather than a solution. Ask what problem it will create, and when.
- Break it into parts
Three parts: tracing second- and third-order effects, finding the feedback loops, and locating the leverage point.
- The part that carries it
“And then what?”, asked three times. Most systems damage comes from stopping at the first answer.
- The order to learn it in
- Practise “and then what?” on changes you have already watched play out, where you know the ending.
- Then learn to spot loops: where does an output come back round as an input?
- Only then hunt for leverage — the small structural change that moves the whole thing.
- Put something at stake
Before your next process change, write down the second-order effect you expect, date it, and review it with the team in a month.
- Compress it
Trace three steps out, find the loop, find the leverage, and distrust the quick fix.
- The smallest useful dose
One “and then what?” chain written out for every decision that changes how people work.
- Anchor it to something you know
A thermostat. The temperature of the room is not set by the heater — it is set by the loop between the heater and the sensor, and by how long the sensor takes to notice.
“Today’s problems come from yesterday’s solutions.”
— Peter Senge
The interactive version is in the course. The diagram, the simulation and the four-question check for Systems Thinking run in the free course, where your progress across all 24 skills is kept.
Open Systems Thinking in the course →
Not sure where you stand? Take the twelve-minute self-assessment, or see the 30-day course that turns these skills into a roadmap.