methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method sessionHalf day (4 h)WorkshopHebel-Map

Session: Leverage Points

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 3-12. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Hebel-Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 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. Hint: If the leverage concept is unclear, mappings become arbitrary. Bring one concrete example known to participants per leverage. Abstract theory is not enough.

    FacilitatorHebel-Map
  2. 2

    Phase 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. Hint: 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.

    FacilitatorAktionsstrategie
  3. 3

    Phase 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. Hint: 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.

    FacilitatorHebel-Map
  4. 4

    Phase 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. Hint: 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.

    FacilitatorAktionsstrategie
  5. 5

    Phase 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. Hint: 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.

    OwnerHebel-Map
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerHebel-Map
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Leverage Points

Goal

Artifact: Hebel-Map

Working Question

Which leverage levels address our planned actions, and which higher-level levers would produce stronger impact?

Context

Description of the initiative or transformation effort; current action list; system dynamics map; Meadows article as pre-read; prior change attempts and their outcome.

Setup

  • Format: Method session
  • Duration: Half day (4 h)
  • Mode: Workshop
  • Participants: A facilitator with systems thinking background; strategy or change lead; 3-12 participants from impacted areas; one scribe for leverage mapping and actions.
  • Owner: A facilitator with systems thinking background
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Hebel-Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

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.

Preparation

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.

Agenda

  1. Phase 1: Introduce 12 leverage points (30-40 min) Owner: Facilitator Action: 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. Hint: If the leverage concept is unclear, mappings become arbitrary. Bring one concrete example known to participants per leverage. Abstract theory is not enough. Output: Hebel-Map

  2. Phase 2: Collect current actions (20-30 min) Owner: Facilitator Action: List planned or ongoing actions from the initiative. For each action include clear description: what changes, how does it impact. Hint: 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. Output: Aktionsstrategie

  3. Phase 3: Assign actions to leverage levels (60-90 min) Owner: Facilitator Action: Discuss and assign leverage level for each action. Document rationale. If multiple levels apply, choose the highest. Hint: 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. Output: Hebel-Map

  4. Phase 4: Add higher-leverage actions (45-60 min) Owner: Facilitator Action: 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. Hint: 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. Output: Aktionsstrategie

  5. Phase 5: Action strategy across multiple levers (30-45 min) Owner: Owner Action: 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. Hint: 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. Output: Hebel-Map

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Hebel-Map

Closeout

  • Update result artifact: Hebel-Map
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Hebel-Map: Leverage Points

Working Question

Which leverage levels address our planned actions, and which higher-level levers would produce stronger impact?

Context

Description of the initiative or transformation effort; current action list; system dynamics map; Meadows article as pre-read; prior change attempts and their outcome.

Participants

  • Owner: A facilitator with systems thinking background
  • Participants: A facilitator with systems thinking background; strategy or change lead; 3-12 participants from impacted areas; one scribe for leverage mapping and actions.

Input

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.

Template

Leverage Points Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Leverage map:
  • Action strategy:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Hebel-Map is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Leverage Points Working Template

View templateCompact working template for Leverage Points with context, input, output artifacts, and next step.
canvas

leverage-points-working-template.md

Compact working template for Leverage Points with context, input, output artifacts, and next step.

Leverage Points Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Leverage map:
  • Action strategy:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Hebel-Map.
  • New entry per strategy iteration. Maintain action status continuously. Create a new map when the initiative pivots. Archive prior version with date and rationale.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.