What needs to be finished first
Team understands systems thinking in loops and delays, ideally with a developed diagram of the relevant dynamics.
What needs to be ready before start
List of 12 leverage points from Meadows; whiteboard or Miro board with hierarchical template (low leverage at bottom, high at top); current initiative action list; causal loop diagram or systems view as reference; pens.
A facilitator with systems thinking background; strategy or change lead; 3-12 participants from impacted areas; one scribe for leverage mapping and actions.
Description of the initiative or transformation effort; current action list; system dynamics map; Meadows article as pre-read; prior change attempts and their outcome.
Half day (4 h)
Template with 12 levels arranged vertically, low leverage at bottom (1: Parameters), high at top (12: transcending paradigms). Provide short definition per level. Keep action cards ready.
The one question this method answers
Which leverage levels address our planned actions, and which higher-level levers would produce stronger impact?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Introduce 12 leverage points | 30-40 min | Briefly explain one leverage with example. Order is important: 1 Numbers (Parameters), 2 Buffers, 3 Stock-Flow Structure, 4 Delays, 5 Balancing Loops, 6 Reinforcing Loops, 7 Information Flow, 8 Rules, 9 Self-Organization, 10 Goals, 11 Paradigms, 12 Transcending Paradigms. | If the leverage concept is unclear, mappings become arbitrary. Bring one concrete example known to participants per leverage. Abstract theory is not enough. |
2Phase 2: Collect current actions | 20-30 min | List planned or ongoing actions from the initiative. For each action include clear description: what changes, how does it impact. | If only 3-4 actions exist, the action set is too small for a leverage discussion. Collect at least 8-12 actions before the workshop. |
3Phase 3: Assign actions to leverage levels | 60-90 min | Discuss and assign leverage level for each action. Document rationale. If multiple levels apply, choose the highest. | Most actions are actually low-leverage (Parameters, Buffers) in practice. That is often the first learning shock. Goal-level or Paradigm-level action is often missing entirely. |
4Phase 4: Add higher-leverage actions | 45-60 min | For each high leverage level not yet covered (for example Rules, Goals, Paradigms) propose actions that address that level. Not every level must be covered, but decisions must be explicit. | Higher-level leverage is harder to build but has stronger long-term effect. Teams with only low-level leverage optimize the system without changing it. |
5Phase 5: Action strategy across multiple levers | 30-45 min | Formulate strategy: which mix of low, medium, and high leverage. Deliberately combine quick wins (low) and long-term levers (high). Define owner and deadline per action. | Pure high-leverage strategy is risky (long-term, difficult to measure). Pure low-leverage strategy does not change fundamentals. A balanced mix is the goal. |
What comes out at the end
Leverage map with all 12 levels, mapped actions, and rationale. Action strategy with owner and deadline, sorted by leverage level. Visualized as pyramid or hierarchy. Linked with initiative documentation.
New entry per strategy iteration. Maintain action status continuously. Create a new map when the initiative pivots. Archive prior version with date and rationale.
Compact working template for Leverage Points with context, input, output artifacts, and next step.
What is this method used for?
Which question should be answered at the end?
Which data, observations, or materials are available?
Owner, date, success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Initiative context: Engineering throughput should increase by 30% without doubling hiring.
Actions and leverage assignment
| Action | Leverage level | Rationale |
|---|---|---|
| Reduce CI build time from 35 to 10 minutes | 1 Numbers | Parameter optimization, fast effect, no system shift |
| Set WIP limit to 3 per engineer | 1 Numbers | Parameters |
| Introduce 10% documentation sprint quota | 2 Buffers | Build knowledge buffer |
| Increase on-call rotation from 3 to 5 people | 1 Numbers | Load buffer |
| Split order service into bounded contexts | 3 Stock-Flow Structure | Structural change; team ownership moved |
| Self-service identity platform | 7 Information Flow | Consumers no longer depend on direct communication |
| Change code review norm to pair-programming tolerance | 8 Rules | Rule change enables alternative practice |
| Tech Talk program 30 min/week | 6 Reinforcing Loop | Skill-building that generates more skill-building |
| OKR goal: "Outcome > Output" | 10 Goals | Goal shift drives behavior and reprioritization |
| Engineering career model with senior track without management | 8 Rules | Structural rule |
Gaps
Proposed high-leverage actions
Strategy: Secure quick wins through low levers (CI, WIP, on-call) in Q3 while building high-leverage actions for sustainable change in Q3-Q4.
Recognize symptoms and steer against them
Action list contains only parameter changes while goals and paradigms are not addressed.
Consciously ask for high-leverage options. “What goal change would make the system behave differently?” High leverage is harder but more effective. Balance is the target.
A small action is assigned to a high level (for example paradigm) because it is phrased inspiringly.
Determine leverage level by actual system impact, not by inspiration. A workshop slogan is not a paradigm shift. Apply substance test: what changes in practice?
Paradigm change is decided without concrete next steps or measurable action.
High leverage needs longer time scale and concrete sub-actions. Require at least three sub-actions with owner and deadline per high leverage. Otherwise it remains lip service.
Participants do not know loops and delays, so leverage discussion stays superficial.
Make Meadows pre-read mandatory. If team is new to systems thinking, run a workshop on Causal Loop Diagram or Systems Mapping first.
Workshop produces a long list but no strategy across leverage levels.
Phase 5 is mandatory. Strategy logic: quick wins (low) and sustainable impact (high). Workshop must end with a strategy statement, not just a list.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.