── ── Startups

Feedback Loops

A system has a feedback loop when its output circles back as input to the next cycle. Reinforcing loops amplify (compound interest, viral growth, bank runs, death spirals). Balancing loops self-correct (thermostats, price discovery, immune response). The critical complication is delay: when delay is long relative to response time, even well-designed balancing loops produce oscillation and overshoot — and operators…

How it works

Run the Feedback-Loop Diagnosis — map structure, find dominant loop, predict behavior, find leverage.

1. Name system + variable of interest. Without a specific variable, analysis becomes vague narrative. 2. List drivers and outputs. What inputs change your variable? What does it change in turn? Stay concrete. 3. Identify loops. Trace chains where a variable feeds back to itself. Most systems have several. 4. Classify each loop (R or B). Count negative signs around the loop — even = reinforcing; odd = balancing. 5. Locate delays. Where does a cause take significant time to produce its effect? Delays are where intuition fails. 6. Identify dominant loop. Growth phase = R dominant; maturity = B catching up; crisis = suppressed R taking over. 7. Map stocks and flows. Stocks = accumulations; flows = rates. A positive flow can still leave a stock dangerously low. 8. Predict behavior pattern. Pure R → exponential growth/collapse. Pure B → equilibrium. R+delay → overshoot/oscillation. R+B competing → S-curve. Mismatch with observed behavior = missed loop. 9. Find leverage (Meadows hierarchy). Parameters → buffers → structures → delays → balancing loops → reinforcing loops → goals → paradigm. Most failed interventions push parameters; move up. 10. Stress-test against system response. Balancing loops fight back; reinforcing loops restore trajectory. Intervention must change structure, not just symptom.

When to use it

• user says "we keep overshooting/undershooting", "the cure is causing the disease", "we're stuck in a loop", "why does this keep happening?", "the system keeps fighting back", "bullwhip effect", "death spiral", "growth flywheel"
• system shows oscillation or sudden collapse
• user is planning an intervention in an org/market/supply chain and wants to predict how it will respond

Worked example

Forrester's Beer Distribution Game & Sterman's 1989 Measurement

The empirical foundation for "operators systematically mismanage dynamic feedback systems" rests on the Beer Distribution Game, a simulation developed by Jay Forrester and his colleagues at MIT Sloan in the early 1960s, and the quantitative experimental work of John Sterman, who in 1989 published the first rigorous measurement of how participants actually behave in it.