What accumulates?
Inventory, cash, trust, skill, population, backlog and reputation are states carried from one moment to the next.
Side 07
A study of behavior that emerges from relationships rather than isolated parts. Stocks accumulate, flows change them, feedback closes loops, delays distort timing, and interventions often create consequences somewhere other than where attention began.
A system map is not a list of components. It records what accumulates, what changes those accumulations, what information returns, where delays sit and what boundary defines the model.
Inventory, cash, trust, skill, population, backlog and reputation are states carried from one moment to the next.
Hiring and attrition, sales and returns, learning and forgetting, inflow and outflow alter accumulated states.
An effect eventually influences one of its own causes, amplifying or counteracting the original movement.
Production, hiring, perception, learning and policy responses often act after the conditions that triggered them have changed.
Every map is partial. A boundary is a deliberate analytical choice, not a claim that the outside world does not matter.
The useful unit of observation is often behavior over time: what rose, fell, oscillated, saturated, overshot or recovered?
Feedback is causal circularity. The distinction between reinforcing and balancing loops explains much of the behavior that initially appears mysterious.
A change produces effects that push the original variable further in the same direction.
Growth or decline that feeds on itself until another constraint becomes dominant.
A change produces effects that oppose the original movement and pull the system toward a target or constraint.
Goal seeking, stabilization, resistance to change or oscillation when delays are substantial.
Different structures leave different temporal fingerprints. The pattern is a clue to the loop architecture underneath.
A reinforcing loop dominates: growth adds to the base that produces further growth.
Reinforcing growth starts strongly, then a balancing constraint progressively takes control.
A balancing process adjusts action in proportion to the distance from a target.
A balancing loop with delay repeatedly overshoots and undershoots its target.
Growth continues beyond a sustainable level because limits are perceived or acted on too late.
Demand on a resource exceeds regeneration long enough to damage the system’s future capacity.
Archetypes are reusable hypotheses. They are useful as diagnostic prompts, not labels to force onto every situation.
A reinforcing engine succeeds until a balancing constraint becomes binding. Look for the limiting factor before pushing the growth loop harder.
A quick correction relieves the symptom while delayed side effects recreate or worsen the original problem.
A symptomatic solution becomes easier to repeat while the capacity for a fundamental solution weakens.
Individually rational use of a shared resource accumulates into collective depletion.
Early advantage attracts resources, producing stronger results and further resource concentration.
Each actor responds to the other’s move, creating a mutually reinforcing contest around a relative target.
Interventions differ in depth. Changing a parameter is easier than changing the information, rules or goals that generate repeated behavior.
Numbers, thresholds, prices, staffing levels, quotas. Visible and often easy to change; sometimes powerful, often temporary.
Inventory, slack, reserves and time horizons. These affect how shocks travel through the system.
Physical or procedural pathways that determine how material, work or people move.
The time between signal, decision, action and consequence. Shortening or recognizing delays can prevent overcorrection.
Who sees what, when and with what fidelity. New information flows can alter behavior without changing formal authority.
Incentives, permissions, constraints and decision rights that shape local choices.
What the system is optimizing for. A new goal can reorganize lower-level behavior.
The assumptions used to define the problem, the boundary and what counts as success.
The ladder is adapted conceptually from Donella Meadows’ work on leverage points; it is compressed here into study categories rather than reproduced as her original twelve-point list.
Start with behavior, then propose structure. The objective is not to draw a complicated diagram; it is to discover a better hypothesis.
Map backlog as a stock. Add hiring as an inflow to capacity, but also onboarding load as a temporary drain on experienced staff. Add coordination cost as team size grows. Ask which balancing loops are cancelling the intended capacity gain.
Map users, supply and trust as separate stocks. Growth may reinforce liquidity while verification capacity lags. Poor matches increase complaints, reduce trust and eventually slow both sides of the market.
Test “shifting the burden.” The symptomatic response may be improving while investment in root-cause prevention falls because the emergency capability makes recurrence tolerable.
Look for implementation, behavioral and measurement delays. A balancing intervention can seem ineffective early, invite additional intervention, then deliver both waves of effect after the system has already moved.