Systems Thinking · Lesson 1 of 3

Parts, relationships and feedback loops

When replacing the parts does not fix it, the structure is producing the behaviour.

7 min read · Free — no account needed to read

A system is a set of parts whose behaviour comes mostly from how they are connected, not from what the parts are individually. Replace every person on a struggling team and the same problems often reappear, because the structure was producing them.

Feedback loops are the engine. A reinforcing loop amplifies: more users, more content, more users. A balancing loop resists: hire more people, coordination cost rises, output does not rise proportionally. Most stubborn situations are a reinforcing loop you want and a balancing loop you had not noticed.

Delay is what makes loops hard to see. The effect arrives long after the cause, so the two never get connected — and people conclude the intervention did nothing, or blame whatever happened to be nearby when the effect finally showed up.

See it happen

Three different people have now owned the weekly update, and it is late every time.

The read that arrives on its own

We keep picking the wrong person for it. Find someone more organised next time.

The same situation, with this idea

Three people, same result. The update needs numbers that are not ready until Thursday, and it is due Thursday. Whoever holds it inherits a deadline that cannot be met.

What changed

When replacing the parts does not change the behaviour, the structure is producing it. That is the moment to stop looking at people.

The takeaway

When replacing the parts does not fix it, the structure is producing the behaviour.

Easy to take the wrong way

Using "it is the system" as somewhere to put the blame instead. It is a claim about where the leverage is, and it is only worth making if it points at something you can change.

Try this

Draw one loop in your own life where an action makes more of itself.