The three things a system is made of

Strip any system back and you find the same three ingredients. Parts are the things that exist — a piston, a warehouse, a department. Flows are what moves between them — fuel, goods, information. Feedback is the loop that sends a result back to change the next round of behaviour.

Most people meet a system as a list of parts, because parts are easy to name and photograph. But behaviour lives in the flows and feedback, not the parts. A pump that is perfect in isolation does nothing until flow connects it to a circuit, and a thermostat is only useful because feedback tells the heater what just happened.

Behaviour comes from flows and feedback, not parts alone Parts what exists Flows what moves Feedback what comes back result returns to the start
Figure 1 — Parts, flows and feedback form a loop. Change the feedback and the whole system behaves differently.

Stocks and flows: the everyday version

A stock is anything you can measure right now: water in a tank, cash in an account, stock on a shelf, people waiting in a queue. A flow is the rate that stock fills or drains. Almost every system story you can tell is really a sentence of the form "the stock rose because the inflow beat the outflow".

This single framing explains why a full warehouse is not the same problem as a slow supplier, why a bathtub overflows while the tap is only slightly too open, and why a company can be profitable and still run out of cash. The stock and the flow are different questions, and confusing them is the most common error in system reasoning.

The same lens on a machine

Take a simple pumped water circuit. The parts are the tank, the pump, the valve and the pipes. The flow is the water moving through them. The feedback is the pressure at the outlet, which can open or close a valve to hold the flow steady. Ask where the stock is, which flow changes it, and what feeds the result back — and you have described the machine without naming a single brand or model.

The same lens on an organization

Swap the nouns and nothing about the reasoning changes. The parts are departments and roles; the flows are orders, money and information; the feedback is the report that comes back to change next month's plan. A slow supply chain and a slow reporting loop are the same shape of problem, and the same questions will find both.

Try it: whenever something is behaving strangely, name the stock, name the flows that change it, and find the loop that feeds the result back. You will usually reach the cause faster than by inspecting the parts.

Where system thinking stops

System thinking is a lens, not an answer machine. It tells you where to look and what to measure; it does not predict the numbers or replace specialist knowledge. Used well, it keeps you from blaming a part when the loop is at fault — and that alone solves more than its share of puzzles.