--- title: "What can Thinking in Systems teach creators?" description: "Donella Meadows's Thinking in Systems in 7 frameworks with steps, and the five Tom Sharman lessons it backs." canonical: https://tomsharman.com/bookshelf/thinking-in-systems/ updated: 2026-11-03 --- # Thinking in Systems > Donella Meadows's Thinking in Systems in 7 frameworks with steps, and the five Tom Sharman lessons it backs. The frameworks here are Donella Meadows's, from Thinking in Systems. Claude read the book in Tom's Brain and linked it to his lessons. ## How Tom uses this - [Signals show before numbers, and numbers come at month four](https://tomsharman.com/lessons/signals-show-before-numbers-and-numbers-come-at-month-four/index.md): Stocks change slowly and delays hide results, so early signals matter and patience before month four fits the book's warning against giving up too soon. (pp. 37, 38, 125 and 126) - [Macro and micro at the same time](https://tomsharman.com/lessons/macro-and-micro-at-the-same-time/index.md): Meadows says a hierarchy needs enough central control for coordination and enough autonomy for the parts, and that you must watch the short and long term together. (pp. 105, 206 and 207) - [Move the people you have before you hire](https://tomsharman.com/lessons/move-the-people-you-have-before-you-hire/index.md): The book shows a workforce grows by cutting outflow as well as adding inflow, and urges backing the capacities a system already has before bringing in outsiders. (pp. 36, 37 and 202) - [Week one is an audit, and two formats are never up for testing](https://tomsharman.com/lessons/week-one-is-an-audit-and-two-formats-are-never-up-for-testing/index.md): The first guideline is to get the beat of the system by studying its behaviour and history before disturbing it, which is what a week-one audit does. (pp. 194 and 195) - [Assumptions made too fast, and risk avoided](https://tomsharman.com/lessons/assumptions-made-too-fast-and-risk-avoided/index.md): Meadows urges small experimental steps, exposed mental models and error-embracing, and leaning on both intuition and analysis, which matches data plus gut and backing yourself. (pp. 195, 196 and 204) - Author: Donella Meadows - Pages: 237 - ISBN: 9781603580557 - Chapters: 17 - Frameworks: 7 - Categories: Systems and operations, Leadership, Sales and negotiation, Content and packaging - Book 42 of 46 on the bookshelf: https://tomsharman.com/bookshelf/index.md ## What it argues Meadows argues that a system produces its own behaviour through its stocks, flows, feedback loops and delays, so outside events and individual players are rarely the real cause of a problem. Because our mental models are partial and we attend to events instead of structure, systems keep surprising us: delays cause oscillation, growth meets limits, and bounded rationality turns reasonable local choices into results nobody wants. Recurring structures, the eight traps, explain why fixes fail, and each has a way out through changed goals, rules or information. Her ranked list puts parameters at the bottom of the leverage scale and information flows, rules, goals and paradigms near the top. She closes by saying that systems cannot be controlled or predicted but can be designed and danced with, which takes humility, visible models and constant learning. ## Worth keeping - Look to structure for the cause: a system largely causes its own behaviour, and replacing the person in a role rarely changes the result (p. 16, p. 130). - A purpose is read from what a system does, not from what it says (p. 28). - You can fill a stock by cutting the outflow as well as raising the inflow (p. 36). - A delay in a balancing loop makes oscillation likely, and reacting faster can make it worse (p. 72, p. 75). - Systems deliver exactly what you measure, so do not confuse effort with result (p. 162, p. 217). - Escape traps by changing goals, feedback or rules; pushing the same lever harder fails (p. 134 to 165). - Numbers and parameters are the weakest leverage points; information flows, rules and goals are far stronger (p. 170, p. 179, p. 181). - Missing, late or biased information causes most system malfunction (p. 196). - Manage for resilience, not only for productivity or stability (p. 98). - Watch the system's behaviour and history before you disturb it, and put your mental model on paper where others can challenge it (p. 194, p. 196). ## The questions it answers ### What makes a format repeatable, as opposed to a hit that happened once? Events are one-offs, while repeatable behaviour comes from underlying structure, so a repeatable format is a structure with feedback and not a lucky output (p. 108 to 110). ### What does AI actually change about the shape of a content team? New information flows are a high leverage point, so AI matters where it adds or restores feedback to the people making decisions (p. 179). ### What is the smallest team that can produce at the volume I am used to? The watchmaker fable shows stable subassemblies of about ten elements survive interruption, which suggests small autonomous units under light coordination (p. 102 to 103). ## The frameworks 1. [Is it a system or a bunch of stuff](https://tomsharman.com/bookshelf/thinking-in-systems/is-it-a-system-or-a-bunch-of-stuff/index.md): A four-part test for whether you are looking at a system. 2. [Questions for testing the value of a model](https://tomsharman.com/bookshelf/thinking-in-systems/questions-for-testing-the-value-of-a-model/index.md): Three questions to judge a scenario or model before trusting it. 3. [The eight system traps](https://tomsharman.com/bookshelf/thinking-in-systems/the-eight-system-traps/index.md): Common structures that produce persistent bad behaviour, each paired with its way out. 4. [Three ways to avoid the tragedy of the commons](https://tomsharman.com/bookshelf/thinking-in-systems/three-ways-to-avoid-the-tragedy-of-the-commons/index.md): Ways to restore missing feedback on a shared resource. 5. [Helping a system help itself](https://tomsharman.com/bookshelf/thinking-in-systems/helping-a-system-help-itself/index.md): Questions to ask before intervening so you avoid the addiction trap. 6. [Places to intervene in a system](https://tomsharman.com/bookshelf/thinking-in-systems/places-to-intervene-in-a-system/index.md): Twelve leverage points ranked from weakest to strongest. 7. [Guidelines for living in a world of systems](https://tomsharman.com/bookshelf/thinking-in-systems/guidelines-for-living-in-a-world-of-systems/index.md): Fifteen practices drawn from systems thinkers. ## Working with Tom on this Tom works with creators and founders one to one, from a single session to a fractional role. [Work with Tom](https://tomsharman.com/consulting/)