THE IDEA
Making the invisible machine visible
Most systems are invisible. You see the outcomes - the results, the events, the symptoms - but you don’t see the machinery underneath. Feedback loops, delays, reinforcing cycles, balancing forces - they’re all operating, but they’re operating behind the scenes. A causal loop diagram makes them visible.
A CLD is a map of how things influence each other in a system. Each variable is a node. Each arrow shows a causal relationship: A increases B, or A decreases B. When the arrows form a circle, you’ve found a feedback loop. If the loop amplifies change (more leads to more), it’s reinforcing. If it resists change (more leads to less, which leads to less), it’s balancing. A system’s behaviour over time is largely determined by the interplay of these loops.
The power of CLDs isn’t precision - they’re not mathematical models. Their power is making implicit understanding explicit. When a team draws a CLD together, they’re not learning new information. They’re seeing what they already know in a form that reveals structure. “Oh - that’s why this keeps happening.” The diagram doesn’t create the insight. It creates the conditions for the insight to become unavoidable.
IN PRACTICE
Drawing what you can’t usually see
A product team is stuck in a cycle: bugs lead to hotfixes, hotfixes lead to technical debt, technical debt leads to more bugs. Everyone knows this individually, but it’s never been drawn. When someone puts it on a whiteboard as a reinforcing loop, the conversation changes. The question shifts from “how do we fix more bugs?” to “how do we break the cycle?” The diagram didn’t reveal anything new. It made the existing knowledge impossible to ignore.
A public health team maps the dynamics of childhood obesity. Food marketing increases demand for processed food. Processed food increases obesity. Obesity increases healthcare costs. Healthcare costs reduce budgets for preventive programmes. Reduced prevention increases future obesity. The CLD shows something a list of interventions can’t: the system has multiple reinforcing loops, and any single intervention will be fought by the others. The diagram doesn’t solve the problem. It shows why simple solutions don’t work - and where a combined intervention might.
A couple in therapy draws a diagram of their argument pattern. One partner withdraws when stressed. Withdrawal triggers anxiety in the other. Anxiety leads to pursuit and questions. Pursuit leads to more withdrawal. A balancing loop that produces oscillation: pursue-withdraw-pursue-withdraw. Seeing it drawn out - with arrows and labels - shifts the conversation from “you always…” to “we’re in a loop.” The diagram makes the structure visible, and visible structures are easier to interrupt than invisible ones.
WORKING WITH THIS
How to draw one
Start with the thing you’re trying to understand - the outcome, the problem, the pattern. Write it in the centre. Then ask: what makes this increase? What makes this decrease? For each answer, ask the same questions again. When you find yourself arriving back at something you’ve already written, draw the arrow and close the loop. You’ve found a feedback structure.
Label each arrow with a ”+” (same direction: if A goes up, B goes up) or a ”-” (opposite direction: if A goes up, B goes down). A loop with all ”+” signs, or an even number of ”-” signs, is reinforcing. A loop with an odd number of ”-” signs is balancing. This tells you what the loop does: reinforcing loops amplify, balancing loops stabilise.
The most important rule: draw to learn, not to be right. A CLD is a thinking tool, not a finished product. It should be messy, debated, and revised. The value is in the conversation it produces, not the diagram it leaves behind. If the diagram makes someone say “wait, that’s not how it works” and start redrawing - that’s not failure, that’s the process working.
THE INSIGHT
The line to remember
You can’t change a system you can’t see. A causal loop diagram doesn’t give you the answer - it gives you the question you should have been asking all along.
RECOGNITION
When this is in play
You need a causal loop diagram when the same problem keeps coming back and nobody can explain why. When a team agrees on the symptoms but disagrees about the causes. When an intervention had the opposite effect to what was intended and nobody saw it coming. When the conversation is going in circles - which is itself a sign that the system’s feedback is going in circles too. When someone says “it’s complicated” and means “I can see the pieces but not how they connect.”