Method guideSystems Thinking

Leverage Points

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityHigh

TimeHalf day

Participants3-12

FormatWorkshop

MaturityEstablished

Plan Leverage Points

Prerequisite

What needs to be finished first

Complete firstBounded subject

The scope and purpose of Leverage Points are stated as a concrete question.

Without scope, leverage point portfolio becomes arbitrary.

Complete firstAccess to relevant perspectives

System boundary and behaviour over time, feedback loops and delays, existing interventions and domain decision makers are available.

Without these perspectives, central claims in leverage point portfolio remain unsupported.

Preparation

What needs to be ready before start

Materials

System boundary and behaviour over time, feedback loops and delays, existing interventions, shared workspace, source links, and decision log.

People / roles

System owner · affected actors · analyst · decision owner

Pre-read

Collect System boundary and behaviour over time, feedback loops and delays, existing interventions in advance and mark open assumptions.

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.

Core question

The one question this method answers

At which place in the system can a small justified change sustainably influence behaviour?

Flow

Phases with goal, actions, output and pitfall

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.

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.

leverage point portfolio
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.

Donella Meadows: Leverage Points

1
Map behaviour
Map behaviour
Goal
Produce system picture so the core question “At which place in the system can a small justified change sustainably influence behaviour?” can be answered with stronger support.
Inputs for this step
- System boundary and behaviour over time
- feedback loops and delays
- existing interventions
Actions
- Map boundary, behaviour over time, feedback, and delays.
- Record source, rationale, and open uncertainty directly in system picture.
Output
system picture
system picture · source · uncertainty · next decision
Quality check
Does the model explain the observed pattern?
Pitfall
A high-sounding leverage level is chosen without a feedback model or side-effect check. Make behaviour pattern, loop, delay, and expected side effect visible and test small.
Timing: 10–20 minutes
2
Locate leverage
Locate leverage
Goal
Produce leverage options so the core question “At which place in the system can a small justified change sustainably influence behaviour?” can be answered with stronger support.
Inputs for this step
- system picture
- feedback loops and delays
- existing interventions
Actions
- Generate interventions across several of the twelve levels.
- Record source, rationale, and open uncertainty directly in leverage options.
Output
leverage options
leverage options · source · uncertainty · next decision
Quality check
Are parameters and rules clearly distinguished?
Pitfall
A high-sounding leverage level is chosen without a feedback model or side-effect check. Make behaviour pattern, loop, delay, and expected side effect visible and test small.
Timing: 10–20 minutes
3
Test effects
Test effects
Goal
Produce effect hypothesis so the core question “At which place in the system can a small justified change sustainably influence behaviour?” can be answered with stronger support.
Inputs for this step
- leverage options
- feedback loops and delays
- existing interventions
Actions
- Anticipate loop effect, delay, side effect, and resistance.
- Record source, rationale, and open uncertainty directly in effect hypothesis.
Output
effect hypothesis
effect hypothesis · source · uncertainty · next decision
Quality check
Is feedback direction justified?
Pitfall
A high-sounding leverage level is chosen without a feedback model or side-effect check. Make behaviour pattern, loop, delay, and expected side effect visible and test small.
Timing: 10–20 minutes
4
Test intervention
Test intervention
Goal
Produce intervention experiment so the core question “At which place in the system can a small justified change sustainably influence behaviour?” can be answered with stronger support.
Inputs for this step
- effect hypothesis
- feedback loops and delays
- existing interventions
Actions
- Plan a small reversible test with measure and stop rule.
- Record source, rationale, and open uncertainty directly in intervention experiment.
Output
intervention experiment
intervention experiment · source · uncertainty · next decision
Quality check
Are learning goal and safety boundary explicit?
Pitfall
A high-sounding leverage level is chosen without a feedback model or side-effect check. Make behaviour pattern, loop, delay, and expected side effect visible and test small.
Timing: 10–20 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Leverage Points · Systemhebel nach Wirkungshöhe ordnenGeplante Eingriffe von Parametern bis Paradigmen einordnen und bewusst höhere Hebel ergänzen

Form

Versioned leverage point portfolio with date, sources, owners, and next review.

Versioning / ownership

Retain date, source, assumption state, and decision for every version of leverage point portfolio.

Tool alternatives

leverage point portfolio as board or document
Source and evidence register
Decision and action log

leverage-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

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

leverage-points-beispiel.md

Concrete filled scenario, fictional example

Parameter idea: add two agents. Information flow: product teams see weekly ticket causes. Feedback rule: top causes receive a product owner within 14 days. Test: eight weeks, share of recurring tickets. Expected counter-reaction: better visibility initially increases reporting volume.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Map behaviourA high-sounding leverage level is chosen without a feedback model or side-effect check.View in phase
Locate leverageA high-sounding leverage level is chosen without a feedback model or side-effect check.View in phase
Test effectsA high-sounding leverage level is chosen without a feedback model or side-effect check.View in phase
Test interventionA high-sounding leverage level is chosen without a feedback model or side-effect check.View in phase