Thinking in Systems
Structure drives behaviour
Stop blaming the parts
Thinking in Systems, chapters 1 and 4
The same problem has now survived three different people. This is Meadows on why that is the moment to stop blaming anyone.
What actually happened?
Meadows builds the whole book on one sentence: system structure is the source of system behavior. She demonstrates it with a car dealer who orders new stock from what he sold last week. Deliveries take three days, he waits a few days before believing a change is real, and the result is a showroom that swings between empty and overflowing. Nothing in the model is a bad decision. Every order is sensible on the day it is placed; the oscillation lives in the delays. Replace the manager and the same graph comes back. Stocks, flows and loops decide what a system does, whatever the parts are made of.
A problem that keeps returning is a structural signal
A one-off can be put down to a person or to luck. A problem that recurs and survives a change of personnel cannot: it means a loop in the structure is producing it reliably. Handling the person is swapping a part, and the part goes back into the same machine.
Three people have left this role inside a year. Before the fourth advert goes out, draw who this job answers to and what it is allowed to decide.
Look at the pattern, not at the events
Events are waves on the surface; patterns are the current beneath. Meadows tells you to stretch the time axis and ask what shape this number has made over two years — oscillation, exponential rise, an S-curve, overshoot and collapse. Each shape belongs to a particular arrangement of loops.
Stock keeps swinging from famine to glut. Auditing orders one by one never ends. Plot two years, recognise the standard oscillation, and go looking for the delay.
Structure is not an alibi
No separate villains is easily heard as nobody is accountable. Meadows means the reverse. Precisely because structure produces behaviour, whoever can change the structure carries the most responsibility: whoever sets targets, writes the process and decides what information reaches whom is writing what this system will do.
Salespeople keep overpromising and no amount of policing stops it. The person most responsible is whoever made signed revenue this quarter the only measure.
How do I use it today?
Where you are: the same problem has been handled several times, the people have changed, and it is still here.
Ask first: which loop produces this behaviour, and who has the authority to change that loop?
Where it goes wrong: using structure to excuse everybody; or drawing the diagram and then still intervening only at the level of the parts.
Lines to keep
System structure is the source of system behavior.
A system's behaviour cannot be known from its elements alone.
A chronic problem is not a bad person. It is a loop.
Same situation, other people are asking
We fell into the same hole again.New people, same mistakes.I have replaced the people and the same fight came back.We punished the person who did it and it happened again.The same mistakes keep happening · all 9 questions →If this one named what you are going through,
send it to someone who needs it, or keep it somewhere you will find it again.