How to see a feedback loop
A loop is when an effect circles back and feeds its own cause.
By Denys Kostin · Updated
Late projects lead to rushed work. Rushed work creates bugs. Bugs make projects later. That is a loop, and no single person is the cause.
Two kinds
- Reinforcing: more leads to more (or less to less). It grows or spirals.
- Balancing: it pushes back toward a target, like a thermostat.
Try it
Write the problem in the middle of a page. Draw arrows to what it causes, then back to what feeds it. If you can close a circle, you found a loop.
Full guide: What Are Feedback Loops. Next: leverage points.
Example: the meeting spiral
Work slips, so a manager adds a status meeting. The meeting removes focus time, so work slips more, so another meeting appears. This is a reinforcing loop: the fix feeds the problem. To break it, you do not remove people. You remove one link, for example replacing the meeting with a short written update.
Delays hide the loop
Loops are hard to see because the effect arrives late. A hiring freeze today shows up as burnout in three months, and nobody connects the two. When you map a loop, mark every step that takes more than a few days. Long delays are where teams overcorrect: they push harder, see no change, push harder again, and then overshoot.
A balancing loop you already use
Workload works like a thermostat. When a team is overloaded, quality drops, complaints rise, and someone reduces the load. That is a balancing loop, and it is healthy until the signal is ignored. If complaints are filtered out before they reach decision makers, the loop is cut and the load keeps rising.
A reinforcing loop in growth
A strong product gets good reviews, reviews bring customers, customers fund improvement. The same shape runs in reverse: a weak launch loses trust, loses customers, and cuts the budget that could fix it. Same loop, opposite direction. Asking "which way is this running?" is the most useful question you can ask of any loop.
Mistakes when drawing loops
- Writing people's names instead of things that change, such as "backlog size" or "trust in estimates".
- Drawing a line, not a circle. If nothing returns to the start, it is a chain, not a loop.
- Skipping the delays.
A 15-minute exercise
Pick a problem. Write four things that rise or fall because of it. Draw an arrow from each to the next. Check whether one of them feeds the original problem. If it does, name the loop and decide whether it is reinforcing or balancing. Then continue with leverage points to choose where to act.
Common questions
What is a feedback loop?
A chain of effects that circles back and influences its own cause.
What is the difference between reinforcing and balancing loops?
Reinforcing loops amplify change. Balancing loops pull a system back toward a target.
How do I spot one at work?
Take a repeating problem and ask what it causes, then whether that effect feeds the problem again.