Purpose
Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.
Systems Thinking Mapping tool
Leverage Points
Finds interventions at different levels of a system, from parameters to paradigms.
Meadows roughly orders twelve places to intervene by leverage. Higher levels can be more powerful but harder to change. The ranking is a thinking aid, not a guarantee.
At which place in the system can a small justified change sustainably influence behaviour?
- Participants
- 3-12
- Time
- Half day
Leverage Points uses map interventions to the twelve leverage levels and test them through feedback effects. Assessments remain justified and context-bound.
Map behaviour
Map behaviour
Map boundary, behaviour over time, feedback, and delays.
Locate leverage
Locate leverage
Generate interventions across several of the twelve levels.
Test effects
Test effects
Anticipate loop effect, delay, side effect, and resistance.
Test intervention
Test intervention
Plan a small reversible test with measure and stop rule.
Observe the intervention as an experiment and revise the model when counter-reactions occur.
A good fit when
For a bounded dynamic system with feedback, delays, and observable behaviour.
Ideal for
- Change programs
- Transformations
- Systems coaching
Not good for
- Pure operational detail backlogs
Outputs
leverage point portfolio
leverage point portfolio with traceable sources, assumptions, and domain decisions.
Decision and review trail
Owners, dates, and next review for leverage point portfolio.
leverage point portfolio
Fictional worked example
map interventions to the twelve leverage levels and test them through feedback effects as a precise working structure with a fictional example.
| Subject | System pattern | Leverage level | Intervention | Test |
|---|---|---|---|---|
| leverage point portfolioWorked example | Recurring tickets rise despite more agents. | Information flow and feedback rule. | Weekly ticket causes to Product. | Eight weeks; recurring tickets. |
1. System pattern
- leverage point portfolio
- Recurring tickets rise despite more agents.
2. Leverage level
- leverage point portfolio
- Information flow and feedback rule.
3. Intervention
- leverage point portfolio
- Weekly ticket causes to Product.
4. Test
- leverage point portfolio
- Eight weeks; recurring tickets.
The example demonstrates the domain logic of Leverage Points; worksheets remain blank.
First step
Start with the core question: At which place in the system can a small justified change sustainably influence behaviour?
Good to do first
Deep dive
How it works
First the system is described so that rules, information flows, goals, and structures become recognizable. The team then ranks possible interventions by depth of impact and effort. In the end, a few priorities remain that can unlock change with comparatively little force.
In detail
Donella Meadows describes twelve leverage points, ordered from weak to strong, that can be used to intervene in a system. Low-level levers are parameters or buffer sizes, while high-level levers are goals, paradigms, and the ability to transcend paradigms. The method helps expose common false assumptions, such as believing small parameter changes are enough.
Facilitation
Explain the twelve leverage points briefly and give examples. Have the team classify actions one by one and discuss what higher-level levers would address.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Leverage Points: WorksheetPlan Leverage Points around its domain steps and the concrete decision question.markdown
Leverage Points: WorksheetPlan Leverage Points around its domain steps and the concrete decision question.
markdownleverage-points-working-template.md
Plan Leverage Points around its domain steps and the concrete decision question.
Leverage Points: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Full workshop Time: 90–120 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: System boundary and behaviour over time, feedback loops and delays, existing interventions, shared workspace, source links, and decision log.
- Roles: System owner · affected actors · analyst · decision owner
- Advance information: Collect System boundary and behaviour over time, feedback loops and delays, existing interventions in advance and mark open assumptions.
- Overall time needed: 90–120 minutes
- Setup: Prepare map interventions to the twelve leverage levels and test them through feedback effects visibly and calibrate assessment terms before starting.
Prepare for the work steps
Map behaviour: Map behaviour
- System boundary and behaviour over time
- feedback loops and delays
- existing interventions
Locate leverage: Locate leverage
- system picture
- feedback loops and delays
- existing interventions
Test effects: Test effects
- leverage options
- feedback loops and delays
- existing interventions
Test intervention: Test intervention
- effect hypothesis
- feedback loops and delays
- existing interventions
leverage point portfolio
| Subject | Behaviour · loop · delay | Meadows place · rationale | Change · expected effect · counter-reaction | Duration · measure · stop rule |
|---|---|---|---|---|
| leverage point portfolio |
- leverage point portfolio: Worked example
Enter only real input, sources, and decisions.
Donella Meadows: Leverage Points
Map behaviour: Map behaviour
Expected artifact: system picture
system picture · source · uncertainty · next decision
Entry:
...
- Does the model explain the observed pattern?
Locate leverage: Locate leverage
Expected artifact: leverage options
leverage options · source · uncertainty · next decision
Entry:
...
- Are parameters and rules clearly distinguished?
Test effects: Test effects
Expected artifact: effect hypothesis
effect hypothesis · source · uncertainty · next decision
Entry:
...
- Is feedback direction justified?
Test intervention: Test intervention
Expected artifact: intervention experiment
intervention experiment · source · uncertainty · next decision
Entry:
...
- Are learning goal and safety boundary explicit?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/leverage-points/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Systems Thinking
Iceberg Model
Instead of Leverage Points, choose Iceberg Model when you want to visibly go beneath the surface and examine patterns, structures, and mental models.
Systems Thinking
Stock and Flow Diagram
Models stocks, inflows and outflows, and delays to understand dynamics, bottlenecks, and capacity.
Systems Thinking
Rich Picture
Makes an unclear problem situation visible with actors, tensions, and flows before premature solutions emerge.
Systems Thinking
System Dynamics Simulation
Moves relationships, patterns, and leverage toward a concrete result through "define the question and time horizon", "define stocks and flows", and "run scenarios and vary assumptions".
Systems Thinking
Behavior Over Time Graph
Traces developments over time and reveals turning points, patterns, and possible causes of a trend.
Systems Thinking
Futures Wheel
Arranges direct and indirect consequences of a change radially, so future impacts and cascades of consequences become visible.
Constraints and origin
HighWorkshopHalf day
Profile
- Method form
- Mapping tool
- Participants
- 3-12
- Time
- Half day
- Maturity
- Established
- Origin
- Donella Meadows
Next up: System Archetypes