# Thinking in Systems

Donella H. Meadows · 2008

Open the original and follow its chapters or sections with this study guide. Reading tasks are editorial assignments. Use the points to consider to examine your interpretation.

## Scope of source verification

Structure checked against: Contents or section structure

The publisher preview hosted by authorized bookseller isee systems verifies the edition, introduction, seven chapters and six appendix divisions as page images. Full chapter bodies are unverified. Public essays maintained by the author’s rights organization provide supporting context.

- [Thinking in Systems — publisher preview at isee systems](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Contents
- [The Donella Meadows Project — Thinking in Systems](https://donellameadows.org/systems-thinking-book-sale/) — Bibliography
- [The Donella Meadows Project — Leverage Points](https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/) — Public text

<a id="guide"></a>
## Read the whole work

Whole-work question: How can a changing problem be reconsidered through accumulations, flows, relationships and purpose?

Edition: Chelsea Green 2008 first edition, edited by Diana Wright, ISBN 9781603580557

Native units: Reading divisions of the text

Form: Argument

Scope and divisions: Author/editor prefatory notes, endnotes, bibliography, acknowledgments, biography and index are outside scope. Appendix item numbers are editorial navigation. Original division order is preserved. Descriptive labels, parts and learning units are editorial reading aids.

Checked: 2026-11-17

### Reading paths

Short path: [Drawing accumulations separately from rates of change](#guide-unit-stocks-flows) → [Comparing patterns of behavior with structure](#guide-unit-patterns-feedback) → [Comparing recurring problems through patterns and evidence](#guide-unit-traps-comparison) → [Comparing places to intervene](#guide-unit-intervention-choices) → [Making observation and revision concrete](#guide-unit-living-learning) → [Using equations to examine assumptions](#guide-unit-equations-assumptions)

Full path: [Looking from events toward change over time](#guide-unit-systems-lens) → [Drawing accumulations separately from rates of change](#guide-unit-stocks-flows) → [Comparing patterns of behavior with structure](#guide-unit-patterns-feedback) → [Investigating why a system persists](#guide-unit-persistence-properties) → [Tracing surprises back to assumptions](#guide-unit-surprise-conditions) → [Comparing recurring problems through patterns and evidence](#guide-unit-traps-comparison) → [Comparing places to intervene](#guide-unit-intervention-choices) → [Making observation and revision concrete](#guide-unit-living-learning) → [Revisiting a diagram through definitions and principles](#guide-unit-definitions-principles) → [Moving among traps, intervention points and guidelines](#guide-unit-appendix-crosscheck) → [Using equations to examine assumptions](#guide-unit-equations-assumptions)

### Parts and reading units

<a id="guide-part-structure"></a>
#### Connecting structure with change over time

Native range: Introduction: a systems perspective — Chapter 2: Comparing patterns of change

Read the introduction and chapters 1–2 to distinguish visible events from the accumulations and flows that may generate them.

<a id="guide-unit-systems-lens"></a>
##### Looking from events toward change over time

Native range: Introduction: a systems perspective · Read

Open the introduction and recast an event-based problem as a question involving change over time and a stated boundary.

Question: When a problem recurs, what should be included within the system being investigated?

Points to consider:

- State the time horizon and the people or things included.
- Consider whether widening the boundary requires a different explanation.

Concepts: [System boundary](#guide-concept-boundary), [Model](#guide-concept-model)

Reading tasks to check in the original:

- [Introduction: a systems perspective](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open the introduction and look for changes in the questions asked when moving from events to systems.

<a id="guide-unit-stocks-flows"></a>
##### Drawing accumulations separately from rates of change

Native range: Chapter 1: Reading accumulations and flows · Close reading

Read chapter 1 and construct a diagram that separates amounts present from rates of inflow and outflow, with consistent units.

Question: Does observing a decline in a population or inventory establish that outflow increased?

Points to consider:

- Examine changes in an accumulation through both inflow and outflow.
- Distinguish units of amount and rate and specify the observation interval.

Concepts: [Stock](#guide-concept-stock), [Flow](#guide-concept-flow), [Model](#guide-concept-model)

Reading tasks to check in the original:

- [Chapter 1: Reading accumulations and flows](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open chapter 1, choose a stock-and-flow diagram and check the units of amounts and rates.

<a id="guide-unit-patterns-feedback"></a>
##### Comparing patterns of behavior with structure

Native range: Chapter 2: Comparing patterns of change · Close reading

Read the different systems in chapter 2 and trace how an accumulation affects subsequent flows rather than comparing curve shapes alone.

Question: Before treating similar graphs as evidence of the same cause, what would you investigate?

Points to consider:

- Trace the information and rules affecting the flows.
- Consider differences in initial conditions and external inputs.

Concepts: [Feedback](#guide-concept-feedback), [Stock](#guide-concept-stock), [Flow](#guide-concept-flow)

Reading tasks to check in the original:

- [Chapter 2: Comparing patterns of change](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open chapter 2 and compare paths from accumulations back to flows with the resulting changes over time.

<a id="guide-part-systems-us"></a>
#### Reading persistence, surprises and recurring problems

Native range: Chapter 3: Properties that sustain a system — Chapter 5: Recurring problems and possible escapes

Use chapters 3–5 to compare properties that sustain systems with unexpected behavior, relating both to observable conditions.

Depends on: [Connecting structure with change over time](#guide-part-structure)

<a id="guide-unit-persistence-properties"></a>
##### Investigating why a system persists

Native range: Chapter 3: Properties that sustain a system · Read

In chapter 3, distinguish little visible change from an ability to recover, also examining self-organization and hierarchy.

Question: How would you distinguish a system producing constant outcomes from one persisting by adapting to change?

Points to consider:

- Specify the disturbance and what is maintained or recovered.
- Represent local autonomy and overall coordination as observable relationships.

Concepts: [Resilience](#guide-concept-resilience), [Feedback](#guide-concept-feedback)

Reading tasks to check in the original:

- [Chapter 3: Properties that sustain a system](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open chapter 3, compare resilience, self-organization and hierarchy, and consider observations relevant to each.

<a id="guide-unit-surprise-conditions"></a>
##### Tracing surprises back to assumptions

Native range: Chapter 4: Investigating unexpected behavior · Read

Read chapter 4, examine delays and boundaries, and reconsider whether a one-directional causal account is adequate.

Question: Which assumptions would you revisit after an intervention produces an unwanted change?

Points to consider:

- Compare the delay before effects appear with the observation period.
- Examine omitted relationships and relationships whose strength changes with conditions.

Concepts: [Delay](#guide-concept-delay), [System boundary](#guide-concept-boundary), [Model](#guide-concept-model)

Reading tasks to check in the original:

- [Chapter 4: Investigating unexpected behavior](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open chapter 4, select an unexpected outcome and examine delays, nonlinear relationships and boundary choices.

<a id="guide-unit-traps-comparison"></a>
##### Comparing recurring problems through patterns and evidence

Native range: Chapter 5: Recurring problems and possible escapes · Close reading

In chapter 5, map behavior and outcomes in your own case before assigning a trap label, then check similarities and differences.

Question: What mismatch would prompt you to revise an explanation based on a recurring pattern?

Points to consider:

- Identify participants’ purposes and how their actions affect others.
- Retain facts that do not fit and avoid treating a label as a demonstrated cause.

Concepts: [Recurring system pattern](#guide-concept-archetype), [Feedback](#guide-concept-feedback)

Reading tasks to check in the original:

- [Chapter 5: Recurring problems and possible escapes](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open chapter 5, choose a trap, draw its structure and mark relationships that do not match your case.

<a id="guide-part-change"></a>
#### Considering intervention and ways of learning

Native range: Chapter 6: Choosing where to intervene — Chapter 7: Practices for living with systems

In chapters 6–7, consider where to intervene together with practices for observing changes and revising understanding.

Depends on: [Reading persistence, surprises and recurring problems](#guide-part-systems-us)

<a id="guide-unit-intervention-choices"></a>
##### Comparing places to intervene

Native range: Chapter 6: Choosing where to intervene · Close reading

In chapter 6, compare changes in numbers, information, rules and goals without treating an ordering of intervention points as a guarantee of effects.

Question: What evidence would help compare two interventions addressing the same problem?

Points to consider:

- Specify the relationship changed and the expected change over time.
- Compare feasibility, delays, side effects and observations that would prompt revision.

Concepts: [Leverage point](#guide-concept-leverage), [Delay](#guide-concept-delay), [System boundary](#guide-concept-boundary)

Reading tasks to check in the original:

- [Chapter 6: Choosing where to intervene](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open chapter 6, read the descriptions and qualifications, and propose two different kinds of change for the same case.

<a id="guide-unit-living-learning"></a>
##### Making observation and revision concrete

Native range: Chapter 7: Practices for living with systems · Read

Read chapter 7 and develop practices for learning from information rather than a plan assuming complete control of the system.

Question: Which actions would address the possibility that your diagram or prediction is wrong?

Points to consider:

- Specify how to obtain information from different perspectives and when to update the diagram.
- Check neglected values and effects as well as measurable outcomes.

Concepts: [Mental model](#guide-concept-mental-model), [Model](#guide-concept-model), [System boundary](#guide-concept-boundary)

Reading tasks to check in the original:

- [Chapter 7: Practices for living with systems](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open chapter 7, select a guideline and translate it into concrete acts of observation, dialogue and revision.

<a id="guide-part-appendix"></a>
#### Using the appendix to examine your explanation

Native range: Appendix 1: Checking definitions — Appendix 6: Checking model equations

Use the appendix’s definitions, principles, traps, intervention points, guidelines and equations to check a diagram or explanation you have constructed.

Depends on: [Considering intervention and ways of learning](#guide-part-change)

<a id="guide-unit-definitions-principles"></a>
##### Revisiting a diagram through definitions and principles

Native range: Appendix 1: Checking definitions — Appendix 2: Revisiting principles · Survey

Use the appendix’s definitions and principles to check whether meanings or quantities have shifted within a diagram made during reading.

Question: Which terms are most likely to be misunderstood when explaining the same diagram to another person?

Points to consider:

- Check the use of stock, flow and feedback against their definitions.
- Distinguish using a definition correctly from having verified a relationship in reality.

Concepts: [Stock](#guide-concept-stock), [Flow](#guide-concept-flow), [Feedback](#guide-concept-feedback), [Model](#guide-concept-model)

Reading tasks to check in the original:

- [Appendix 1: Checking definitions](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open the glossary and check each term used in your diagram.
- [Appendix 2: Revisiting principles](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open the principles summary and check for disagreement with statements explaining quantities and relationships in your diagram.

<a id="guide-unit-appendix-crosscheck"></a>
##### Moving among traps, intervention points and guidelines

Native range: Appendix 3: Revisiting traps and responses — Appendix 5: Revisiting practical guidelines · Survey

Use three appendix lists to organize the pattern of a problem, the location of a proposed change and the practice of observation as different roles.

Question: What becomes unclear when a trap explanation, intervention and practical guideline are combined into one statement?

Points to consider:

- Write the explanation, proposal and learning practice as separate statements.
- Return to the relevant chapters to identify conditions that a list alone cannot establish.

Concepts: [Recurring system pattern](#guide-concept-archetype), [Leverage point](#guide-concept-leverage), [Mental model](#guide-concept-mental-model)

Reading tasks to check in the original:

- [Appendix 3: Revisiting traps and responses](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open the trap summary and check the match between the pattern chosen in chapter 5 and your diagram.
- [Appendix 4: Using a list of intervention points](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open the intervention-point list and classify what the proposal developed in chapter 6 would change.
- [Appendix 5: Revisiting practical guidelines](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open the practical guidelines and check whether the actions developed in chapter 7 include opportunities to learn and revise.

<a id="guide-unit-equations-assumptions"></a>
##### Using equations to examine assumptions

Native range: Appendix 6: Checking model equations · Survey

Open the model equations and examine the correspondence among diagrams, variables, units and initial states rather than treating calculation as the only objective.

Question: Which assumptions must become explicit when a diagram is expressed mathematically?

Points to consider:

- Record meanings and units of variables and identify the flows changing an accumulation.
- Distinguish obtaining a computed result from verifying that the model fits reality.

Concepts: [Model](#guide-concept-model), [Stock](#guide-concept-stock), [Flow](#guide-concept-flow)

Reading tasks to check in the original:

- [Appendix 6: Checking model equations](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) — Open the model equations, choose a diagram from chapters 1–2 and match its variables, units and initial state.

### Key concepts

<a id="guide-concept-boundary"></a>
#### System boundary

An analytical choice about what belongs within the system and what is treated as an external condition.

First unit: [Looking from events toward change over time](#guide-unit-systems-lens)

<a id="guide-concept-model"></a>
#### Model

A selective representation of relationships or quantities for a purpose; computability and empirical adequacy require separate checks.

First unit: [Looking from events toward change over time](#guide-unit-systems-lens)

<a id="guide-concept-stock"></a>
#### Stock

An amount accumulated at a time, changed by the difference between inflow and outflow.

First unit: [Drawing accumulations separately from rates of change](#guide-unit-stocks-flows)

<a id="guide-concept-flow"></a>
#### Flow

A rate describing how much enters or leaves a stock per unit of time.

First unit: [Drawing accumulations separately from rates of change](#guide-unit-stocks-flows)

<a id="guide-concept-feedback"></a>
#### Feedback

A connection through which a changed state affects flows via information or action and thereby influences the state again.

First unit: [Comparing patterns of behavior with structure](#guide-unit-patterns-feedback)

<a id="guide-concept-resilience"></a>
#### Resilience

A system’s capacity to maintain or recover important functions in response to disturbance.

First unit: [Investigating why a system persists](#guide-unit-persistence-properties)

<a id="guide-concept-delay"></a>
#### Delay

A time gap among change, information and response, relevant to observation and adjustment.

First unit: [Tracing surprises back to assumptions](#guide-unit-surprise-conditions)

<a id="guide-concept-archetype"></a>
#### Recurring system pattern

A structural pattern for comparing settings; assigning a label alone does not verify a cause.

First unit: [Comparing recurring problems through patterns and evidence](#guide-unit-traps-comparison)

<a id="guide-concept-leverage"></a>
#### Leverage point

A place to intervene in system behavior, with effects examined through direction, conditions and time.

First unit: [Comparing places to intervene](#guide-unit-intervention-choices)

<a id="guide-concept-mental-model"></a>
#### Mental model

An understanding of what matters and how things are connected that can be stated and revised through observation or other perspectives.

First unit: [Making observation and revision concrete](#guide-unit-living-learning)

### Misreadings and corrections (editorial examples)

Possible misreading: Positive feedback is good and negative feedback is bad.

Correction: Distinguish amplification from balancing and assess desirability separately.

Check the passage: [Chapter 2: Comparing patterns of change](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)

Possible misreading: Choosing a higher-ranked intervention point guarantees success with little effort.

Correction: Investigate direction, feasibility, delay and side effects rather than treating an ordering as a guarantee.

Check the passage: [Chapter 6: Choosing where to intervene](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)

Possible misreading: If equations produce a result, the real future is determined.

Correction: Make diagram and equation assumptions explicit and distinguish computation from empirical verification.

Check the passage: [Appendix 6: Checking model equations](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)

<a id="guide-capstone"></a>
### Capstone

Choose a recurring problem, set a time horizon and boundary, and draw stocks, flows, feedback and delays. Develop two interventions and an observation plan, then use the appendix to check terminology and assumptions. State omitted relationships and unresolved questions.

- Are amounts distinguished from rates, events from structure, and explanation from observation?
- Does the analysis connect structure, recurring problems, intervention and learning?
- Are assumptions and revision conditions checked with the appendix without treating the intervention as already successful?

Parts to connect: [Connecting structure with change over time](#guide-part-structure), [Reading persistence, surprises and recurring problems](#guide-part-systems-us), [Considering intervention and ways of learning](#guide-part-change), [Using the appendix to examine your explanation](#guide-part-appendix)

<a id="guide-scope"></a>
### Native scope inventory

1. [Introduction: a systems perspective](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
2. [Chapter 1: Reading accumulations and flows](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
3. [Chapter 2: Comparing patterns of change](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
4. [Chapter 3: Properties that sustain a system](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
5. [Chapter 4: Investigating unexpected behavior](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
6. [Chapter 5: Recurring problems and possible escapes](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
7. [Chapter 6: Choosing where to intervene](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
8. [Chapter 7: Practices for living with systems](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
9. [Appendix 1: Checking definitions](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
10. [Appendix 2: Revisiting principles](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
11. [Appendix 3: Revisiting traps and responses](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
12. [Appendix 4: Using a list of intervention points](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
13. [Appendix 5: Revisiting practical guidelines](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)
14. [Appendix 6: Checking model equations](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf)

### Primary references

- [Thinking in Systems — publisher preview at isee systems](https://iseesystems.com/store/books/thinking-in-systems/preview.pdf) · SHA-256: bbce5a66a260c92de2671036b33fc028161dfbd69f915cce3ce343b25c210778
- [The Donella Meadows Project — Thinking in Systems](https://donellameadows.org/systems-thinking-book-sale/)
- [The Donella Meadows Project — Leverage Points](https://donellameadows.org/archives/leverage-points-places-to-intervene-in-a-system/)


[Return to the learning courses](/en/lab/classics/learn)

[Download Markdown](/classics-data/modern/meadows.en.md)
