Systems & Hidden Structure

Feedback Loops and Ripple Effects

Also called: Feedback loops and second-order effects

Personal interest
Formal theory
Observed in experiments
Working interpretation

A fix can help at first and backfire later, because people and processes adjust to it. I want to think past the immediate, visible result.

What happens after everyone reacts to my solution?

The idea

Effects rarely stop where they start. A new rule changes behavior, the new behavior changes the numbers, and the new numbers prompt another rule. When a chain of effects comes back to its cause, it forms a loop. Reinforcing loops amplify change. Balancing loops resist it and pull things back toward a target. Delays between cause and effect make both harder to read, because the response arrives after I have already moved on.

An example

The Constraint & Flow Lab on this site has a setting called "cap work in the line". A new unit starts only when a finished one ships, and never more than a set number are inside. That is a balancing loop: the line's own output controls how fast work enters. Compared with starting work at a set pace faster than the bottleneck can handle, the piles stay small and units get through faster, while output stays about the same.

Where it connects

Habits run on loops too (Small Habits Shape Who I Become): a small repeated action changes what feels normal, which makes the action easier to repeat. Physics and engineering share this pattern of complex behavior arising from simple rules acting on each other over time (Complex Patterns From Simple Rules). Loops are also why systems with learning parts keep shifting (Systems Whose Parts Learn and Adapt).

Questions I am still carrying

Which effects of my work will only show up a year from now?
When is it wiser to wait and watch than to correct again?

Questions I'm still exploring

How far ahead is it reasonable to trace the effects of a change?
How can I spot a reinforcing loop early, before it grows large?
Which of my own habits are quietly feeding a loop I did not choose?

Sources and further reading

Donella Meadows, "Leverage Points: Places to Intervene in a System" (1999)
John D. Sterman, Business Dynamics: Systems Thinking and Modeling for a Complex World (2000)

Working interpretation: drafted from my notes and interests for review. It is not a direct quotation, and I may still change it.

In short

A feedback loop is a chain of cause and effect that circles back on itself. In a reinforcing loop, a change feeds itself and grows, like interest building on savings. In a balancing loop, a change triggers a push back toward a target, like a thermostat. Second-order effects are the consequences of the consequences: what happens after people and processes respond to the first change.

Why this matters to me

I am wary of solutions judged only by their first result. In systems work, the second and third effects are where the surprises live, because people adapt to whatever is measured or rewarded. Thinking in loops helps me ask what a change will set in motion, not just what it does today. It applies to my own habits too, which can build on themselves in either direction.

Connections

Small Habits Shape Who I BecomeMechanism

Habits and feedback can form loops: a repeated action can build on itself and grow, or set off a push back that keeps things steady.

Complex Patterns From Simple RulesShared pattern

In physics and in engineered systems alike, complex behavior grows out of simple parts interacting and feeding back on each other over time.

Seeing Connections, Not Just PartsPart of

Feedback loops and ripple effects are how systems thinking looks past the first result to what happens after people and processes respond.