Systems Thinkingi. What Is a System?
0%

Systems Thinking

Most problems that resist simple fixes are system problems. Understanding the structure changes what you do about them.

SkillsRead time11 minLast updatedJune 2026LevelIntermediateSections9
In this module

Systems have stocks, flows, and feedback loops. Reinforcing loops compound; balancing loops seek equilibrium. Delays cause overshoot. Second-order effects undo well-intentioned fixes. Compounding rewards patience; present bias makes patience hard.

By the end you'll

  • Describe any system using stocks, flows, and feedback loops
  • Anticipate second-order effects and delay-driven overshoot before acting
  • Apply pre-mortems, the 10/10/10 rule, and root-cause thinking to long-horizon decisions
9 sections≈ 29 min total

iWhat Is a System?

What Is a System?

A system is any set of elements connected by flows and feedback. Most things you care about changing (your savings, your fitness, your skills) behave like systems. Treating them as isolated events rather than as ongoing processes with structure is one of the most common reasons improvement efforts stall.

Donella Meadows identified three core components. Stocks are accumulations that change slowly: the money in your account, the muscle in your body, the trust in a relationship. Flows are the rates that change stocks: income and spending, training and recovery, honesty and breach. Feedback loops are the information that causes a response: a falling balance triggers spending cuts; rising fatigue signals the need for rest.

The key insight

You cannot change a stock instantly. You can only change the flows into and out of it, and then wait for the stock to respond. This delay between action and visible result is the source of most frustration in self-improvement.
iiFeedback Loops

Feedback Loops

There are two types. A reinforcing loop amplifies change in the same direction: more savings earns more interest, which grows savings further; a consistent habit builds identity, which makes the habit easier to maintain. Reinforcing loops can be virtuous or vicious: the same structure drives both compound growth and debt spirals.

A balancing loop resists change and seeks a set point. Body temperature, blood glucose, and market prices all have balancing feedback: the system detects a gap between its current state and its target, then acts to close it.

Delays are where most systems go wrong. The feedback arrives after the condition has already changed. A driver overcorrects on ice because the car responds late. A company hires aggressively after a boom that has already peaked. Recognising delays turns frustration into patience: the lag is the system, not your failure.
iiiSecond-Order Effects

Second-Order Effects

A second-order effect is the consequence of a consequence. The first-order effect of a rent cap is lower rents for current tenants. The second-order effect is reduced housing supply as landlords exit the market and developers stop building. The policy solves the symptom while worsening the underlying stock.

The cobra effect: colonial administrators offered bounties for dead cobras to reduce the population. Residents bred cobras to collect the bounty. When the programme ended, the bred cobras were released, increasing the population. Attaching incentives to a proxy metric detaches the metric from what it was meant to measure.

Thinking in second-order effects is a habit, not a talent. Before acting, ask: what does this make more likely to happen next? What group has an incentive to respond in a way that undermines the intended outcome? What stock does this intervention deplete that is not currently visible?

ivPresent Bias

Present Bias

Humans discount the future at an inconsistent rate. The gap in perceived value between now and one week from now feels much larger than the gap between four weeks and five weeks from now, even though both are one-week gaps. This is hyperbolic discounting, and it is a documented feature of human cognition, not a character defect.

The practical consequence is that starting tomorrow is a structural prediction. Each tomorrow also has a today that will feel more urgent. The solution is not stronger willpower but better system design: commitment devices, implementation intentions, and reducing friction on the desired behaviour while adding friction to the competing one.

The 10/10/10 rule: before a decision, ask how you will feel about it in 10 minutes, 10 months, and 10 years. The asymmetry between these three answers reveals how much present bias is distorting the choice. Decisions that feel urgent now and irrelevant in 10 years are often present-bias driven.
vCompounding Over Time

Compounding Over Time

Compounding is what happens when a stock's growth feeds back into itself as a flow. A 1% daily improvement for one year produces roughly 37.8 times the starting value. A 1% daily decline produces roughly 0.03 times the starting value. The same structure drives both. The difference is direction, not complexity.

The arithmetic

1.01 to the power of 365 is approximately 37.78. 0.99 to the power of 365 is approximately 0.026. Most people underestimate exponential growth because human intuition reasons in linear steps. A habit that improves by 1% per session looks flat for months, then does not.

The frustrating property of compound systems is that visible results lag far behind inputs. Progress feels absent until it feels sudden. This is the delay property, not evidence that the system is not working. Persistence through the invisible phase is what separates compounding outcomes from flat ones.

viLong-Term Thinking in Practice

Long-Term Thinking in Practice

Abstract awareness of compounding and second-order effects is not enough by itself. Four tools make long-term thinking concrete and repeatable.

  • Pre-mortem: imagine a future failure has already occurred, then work backward to identify what caused it. This removes the optimism bias that distorts forward planning and surfaces risks that standard analysis misses.

  • 10/10/10 rule: before a significant decision, ask how you will feel about it in 10 minutes, 10 months, and 10 years. The gap between these three answers shows how much present bias is distorting your view.

  • Root-cause analysis: when something is not working, ask what system property is maintaining the problem, not just what the most visible symptom is. Fixing a symptom without changing the underlying structure produces temporary results.

  • Scenario planning: identify two or three plausible futures rather than one expected one. Design responses that work reasonably across all of them rather than one that is optimal for a single predicted outcome.

viiA System in Practice

A System in Practice

Product development from idea to shipped feature is a feedback system. Requirements are the stock: accumulated understanding of what needs to be built. Inputs are discovery work such as interviews, analysis, and observation; outputs are scope decisions such as approve, cut, or defer. Feedback loops close when built features are reviewed against requirements, and the gap drives revision.

The stock that matters most is often not the one being measured. Teams track velocity while neglecting requirement quality, the stock that determines whether velocity produces value. Increasing flow speed without improving stock quality produces poor outputs faster.

Delays are the most consequential property of this system. Requirements written early inform code written weeks later. By the time feedback arrives, the team has moved far ahead of where the error was introduced. Short feedback loops (incremental delivery, early review, frequent integration) are structural responses to delay. They do not eliminate it; they reduce the distance between error and correction.

viiiFlashcards

Flashcards

All cards
ixModule Quiz
Module Quiz

Answer correctly to complete the module. Pass mark: 4/5.

Loading...

Sources & inspiration

See the full library →
Learn & Grow