What is systems thinking? The founder’s guide to seeing the whole board.
Your hardest problems keep coming back because you’re fixing what you can see, not the structure underneath. Systems thinking is the skill of seeing that structure — and it’s learnable. Here’s the plain-English version, built for people running things.
A Nerd Knots initiative · Books · Coaching · Community
Systems thinking is a way of understanding a problem by looking at how its parts connect and influence each other over time — instead of examining each part in isolation.
The word “system” sounds technical, but Donella Meadows put it plainly: a system is “a set of things… interconnected in such a way that they produce their own pattern of behavior over time.” A startup is a system. So is your pipeline, your team, your churn. Systems thinking is simply the habit of asking how the pieces produce the result — rather than blaming the piece that happens to be on fire.
It has real lineage. MIT’s Jay Forrester founded system dynamics in the 1950s–60s; Donella Meadows made it accessible in Thinking in Systems; and Peter Senge put it at the center of The Fifth Discipline (1990) as the core skill of a learning organization. You don’t need the academic version to use it — you need the founder version.
The iceberg model: why your fix didn’t hold
Most early problem-solving happens at the level of events: signups dipped, so run a promo; support is drowning, so hire a rep. Each move is locally correct and globally useless — the event is the smoke, the structure is the fire.
The iceberg model is the fastest way to see it. A problem shows itself above the waterline; most of what’s driving it sits below. Read from the top down:
1. Events
What happened“Two engineers quit this month.” Visible, urgent, and where about 95% of a founder’s attention goes. Also where the least leverage lives.
2. Patterns
What keeps happening“We’ve lost a senior hire every quarter for a year.” Events viewed over time. The recurrence is the signal — a pattern is pointing at a structure.
3. Structures
What produces the patternNo path to promotion, comp set below market, siloed teams. Change something here and the pattern changes — this is where real fixes live.
4. Mental models
The beliefs holding it in place“External hires bring fresh blood.” “People are motivated mainly by money.” Left unexamined, these quietly rebuild the structure you just fixed.
The deeper you intervene, the more leverage you get — and the more courage it takes. Most founders spend their week at the very top.
Three ideas that do most of the work.
Systems thinking has a lot of vocabulary. These three ideas carry most of the value for someone running a company — each with a plain-English essay.
Why your fix made things worse
Reinforcing loops amplify (vicious and virtuous cycles); balancing loops pull toward a goal. Most “my fix backfired” moments are a reinforcing loop you accidentally fed.
Read the essayPatterns over eventsStop reacting to the same problem twice
The same fire three times a quarter isn’t a busy season — it’s a structure advertising itself. Zoom out far enough to see the ones that rhyme.
Read the essayLeverage pointsThe one change that moves the whole system
Meadows ranked twelve places to intervene, from weak (tweak a number) to powerful (change the system’s goal). Founders push hardest on the weakest ones.
Read the essayFree field guide
Get the Systems Thinking Field Guide for Founders.
One page. The core moves — stocks and flows, feedback loops, leverage points — translated into plain language you can use on your business this week. Drop your email and we'll send it over, plus the occasional systems-thinking note.
Systems thinking, answered.
- What is systems thinking in simple terms?
- Systems thinking is a way of solving problems by looking at how the parts of a situation connect and influence each other over time, rather than examining each part on its own. Instead of asking “what’s broken?”, you ask “what structure keeps producing this?”
- What is a simple example of systems thinking?
- A support team is always overwhelmed. The event-level fix is hiring another rep. A systems view notices the pattern (tickets keep rising) and the structure behind it (a confusing onboarding flow generating the tickets) — so you fix onboarding and the ticket volume falls at the source.
- What are the main principles of systems thinking?
- Seeing interconnections, spotting feedback loops (reinforcing and balancing), looking below events to patterns and structures (the iceberg model), and finding leverage points — the few places where a small change moves the whole system.
- Who created systems thinking?
- It grew from MIT professor Jay Forrester’s work on system dynamics in the 1950s–60s, was popularized by Donella Meadows in Thinking in Systems, and reached the business world through Peter Senge’s The Fifth Discipline (1990).
- How is systems thinking useful for founders and business?
- It explains why problems recur despite constant effort, keeps you from “fixing” symptoms in ways that backfire, and points to high-leverage changes — so you spend energy where it actually moves the business instead of firefighting.
- How do I start practicing systems thinking?
- Start small and keep it constant. Next time a problem shows up, ask “how many times have I solved this exact thing?” Then read one founder essay, or join the Systems Thinking Studio to practice with other builders.
Make it a practice, not a one-time read.
Systems thinking sticks when you use it every week, together. Join the Systems Thinking Studio — a free community of builders trading maps, questions, and real examples. Not ready? Leave your email for the occasional systems-thinking note.