Edited by Russell Larke, Friday 6 November 2026 at 19:50
You step into the shower. The water is freezing. You turn the dial slightly to the left. Nothing happens. You wait a few seconds, still cold. So you turn the dial further. Still cold. You crank it all the way to the red zone.
Suddenly, the water turns scalding hot. You jump back, burned, and frantically spin the dial back to the cold side.
This is the mechanical reality of a feedback delay.
There is a physical distance between the shower dial and the boiler. It takes time for the water to travel through the pipes. When you turn the dial, you are making an input into a system. But because the system doesn't give you an immediate output, you overcorrect. You push the system past the point you actually wanted it to go.
We do this constantly in the real world. A business faces a drop in sales, so they slash prices to boost demand. But it takes six months for the new pricing strategy to show up in the financial reports. Because the data hasn't arrived yet, they slash prices again. By the time the feedback finally arrives, the business has destroyed its profit margins entirely.
A government sees crime rising and introduces a harsh new policy. The policy might actually work, but it takes years to show results. Because the public doesn't see an immediate change, the government introduces even harsher measures. The system swings wildly back and forth.
The structural lesson is simple: when you intervene in a complex system, you have to account for the delay. You cannot judge the result of your action instantly.
If the water is still cold, do not crank the dial all the way to red. Wait for the pipes to catch up.
The Shower Dial Problem
You step into the shower. The water is freezing. You turn the dial slightly to the left. Nothing happens. You wait a few seconds, still cold. So you turn the dial further. Still cold. You crank it all the way to the red zone.
Suddenly, the water turns scalding hot. You jump back, burned, and frantically spin the dial back to the cold side.
This is the mechanical reality of a feedback delay.
There is a physical distance between the shower dial and the boiler. It takes time for the water to travel through the pipes. When you turn the dial, you are making an input into a system. But because the system doesn't give you an immediate output, you overcorrect. You push the system past the point you actually wanted it to go.
We do this constantly in the real world. A business faces a drop in sales, so they slash prices to boost demand. But it takes six months for the new pricing strategy to show up in the financial reports. Because the data hasn't arrived yet, they slash prices again. By the time the feedback finally arrives, the business has destroyed its profit margins entirely.
A government sees crime rising and introduces a harsh new policy. The policy might actually work, but it takes years to show results. Because the public doesn't see an immediate change, the government introduces even harsher measures. The system swings wildly back and forth.
The structural lesson is simple: when you intervene in a complex system, you have to account for the delay. You cannot judge the result of your action instantly.
If the water is still cold, do not crank the dial all the way to red. Wait for the pipes to catch up.