Thinking in Systems: what founders should steal

Thinking in Systems by Donella Meadows is the most useful business book that never mentions sales, marketing or founders. It is a short primer on stocks, flows, feedback loops, delays and leverage points, and nearly every chapter maps cleanly onto why a B2B service firm grows, stalls or oscillates. Four ideas are worth stealing outright: stocks versus flows, delays, the leverage-point hierarchy, and the trap of seeking the wrong goal.

What is the book, in one paragraph?

Meadows was the lead author of The Limits to Growth and spent her career modelling complex systems. Thinking in Systems, published in 2008 after her death, distils that work into plain language: a system is a set of elements, interconnections and a purpose, and behaviour comes from structure — not from the effort or virtue of the people inside it. That sentence is the premise of everything in A Systems-Thinking Guide for Founders: when your growth is erratic, the structure is erratic, and pushing harder does not fix structure.

Steal one: stocks and flows

Meadows insists you separate stocks (accumulations) from flows (rates). Revenue is a flow. Pipeline is a stock. Reputation, documented process, a verified prospect database — all stocks. Founders manage flows obsessively and stocks accidentally, which is how a record quarter coexists with an empty pipeline: you drained the tub to fill the bucket. I map this fully in Stocks and flows: why your pipeline is a bathtub; the practical discipline is to name your three or four load-bearing stocks and check their levels weekly, not just the flows on the P&L.

Steal two: delays, or why feast-and-famine is structural

Meadows shows that delays in feedback loops produce oscillation, and the feast-and-famine cycle is exactly that. It works like this. When you stop prospecting in March because delivery is busy, then nothing visible happens in March — pipeline is a stock, and it drains slowly. When the drained pipeline finally surfaces as a quiet June, then you restart prospecting in a hurry. When you restart, then results arrive on the system's timetable, not yours — typically a sequence of four emails over fourteen days before replies cluster, and weeks more before deals form. When those deals land together, then delivery is slammed and prospecting stops again. The oscillation is not a motivation problem; it is what any system with delayed feedback does. Meadows' fix is not faster reaction but steadier input — which is the whole argument for a fixed daily sending volume that continues however busy delivery gets.

Steal three: the leverage-point hierarchy

Meadows' most quoted essay ranks twelve places to intervene in a system, from weakest — adjusting parameters — to strongest, changing the system's goal or paradigm. The business translation: rewriting a subject line is a parameter tweak. Adding a feedback loop that did not exist — reply data feeding targeting, delivered work feeding proof feeding outbound — sits far higher on the list, which is the entire case made in Flywheels vs funnels: pick your physics. In most firms the distribution of effort inverts the distribution of leverage: parameter-fiddling absorbs the optimisation hours because parameters are easy to touch, while loop-level design goes untouched because nothing urgent demands it.

Steal four: seeking the wrong goal

A system will faithfully produce whatever its goal actually is — not what the mission statement says. If the number everyone watches is "emails sent" or "meetings booked", you will get sending volume and calendar clutter, whether or not revenue follows. Meadows' rule of thumb: look at what the system produces, and assume that is its real goal. Uncomfortable, and commonly accurate.

What should you not steal?

Some honesty about limits. The book offers almost nothing on implementation; the worked examples are thermostats, fisheries and national economies; and Meadows is more interested in humility before complex systems than in shipping anything by Friday. Read it for the lens, not the playbook. You will still have to build the loops yourself, and Goldratt's The Goal sits much closer to the operational floor if constraints are your immediate problem.

Where do you start on Monday?

Three moves. Name your stocks — pipeline, database, reputation, documented process — and decide who checks their levels each week. Find one delayed feedback loop that is causing oscillation, and steady the input rather than reacting harder to the output. Then apply the same lens to yourself: your energy and attention are stocks with flows and delays too, which is the premise of The Personal Operating System. Meadows' deeper point survives every application: you do not change a system's behaviour by exhorting the people inside it. You change the structure.

---

Keep the thinking coming: The Format — a fortnightly letter on business and personal systems. Subscribe by email.