Thinking in Systems

You step into an unfamiliar shower. The water is cold, so you turn the tap toward hot. Nothing happens, so you turn it more. Then the hot water arrives all at once and you're scalded, so you crank it back toward cold, and a few seconds later you're freezing again.

Nobody in that shower is stupid. The problem is a delay between your action and its effect, and a brain that keeps reacting to the water it feels now instead of the water already on its way. That, in miniature, is what systems thinking is about. The same pattern shows up in supply chains, economies, diets, ecosystems and organisations, and you can learn to spot it.

Three building blocks

Add a fourth ingredient, delay, and things get interesting. A balancing loop with a long delay doesn't settle calmly at its goal. It overshoots, corrects, overshoots the other way, and can end up swinging harder and harder. That's the shower. Try it in a shop.

With a one-week delay, almost any sensible rule works: the shelf dips when demand rises and recovers within a few weeks. Stretch the delay to four weeks and the same rule (correcting 50% of the gap) makes the shelf swing between 25 and 185 units, and the swings keep growing. Nothing outside changed after week 5. Demand was steady. The oscillation is created entirely by the ordering rule meeting the delay.

Two fixes show up when you play. Correcting more gently (try 30%) slows the swings down so they fade. But the real cure is the checkbox: before ordering more, count what's already in the pipeline. That one change in what the manager pays attention to removes the oscillation entirely.

When a system misbehaves, look at what the people in it can see, and how late they see it, before you blame the people.

This isn't just a toy. At MIT around 1960, Jay Forrester, the founder of the field called system dynamics, developed the "Beer Game," in which teams play retailer, distributor and brewery passing orders down a supply chain with delays. Players routinely produce wild swings in orders and stock from a single small change in customer demand. Real companies see the same thing; the term "bullwhip effect" took hold around 1990 when Procter & Gamble noticed wildly erratic ordering of its nappies, a product whose actual use by babies is about as steady as demand gets.

Why fixes backfire

Because systems push back, a fix aimed at one part can produce the opposite of what was intended somewhere else. In 1902, French colonial authorities in Hanoi, fighting the rats that swarmed the city's sewers, paid a bounty for every rat tail handed in. Before long officials were seeing tailless rats running around the city: catchers had been cutting off tails and releasing the rats to breed. The episode is documented by historian Michael Vann.

You may have heard a similar story about a cobra bounty in British India, the "cobra effect." Be careful with that one. A 2025 investigation of colonial records found no contemporary evidence of cobra farming, and the tale seems to trace back to an 1873 newspaper report of something "alleged." The Hanoi rats are the better example, because they actually happened.

Where to push

The environmental scientist Donella Meadows, lead author of The Limits to Growth (1972), spent her career on this question. In a 1999 essay, "Leverage Points: Places to Intervene in a System," she ranked twelve kinds of intervention. A few of them, from weakest to strongest:

She added a warning that is worth remembering: people often find the right leverage point by instinct, and then push it in the wrong direction.

The honest limits

Systems thinking can be misused. "It's all connected" is true and useless; a systems explanation is only worth something when it names specific stocks, loops and delays that you could check. Real systems also have far more moving parts than any diagram, and models built on wrong assumptions can be confidently wrong. Use it as a way to ask better questions, such as what accumulates here, what feeds back, and what's delayed?, not as a machine that hands out answers.