methodatlas
Session Builder

Plan my session

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

Method session3-4 hWorkshop or asyncSystem Map

Session: Systems Mapping

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 System Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Boundaries and purpose

    30 min

    System purpose and boundary in writing. What belongs to system (inside), what is environment (outside). Define time horizon. Hint: If boundaries blur, map is political. Clear decision with decider, otherwise every stakeholder draws boundary differently.

    FacilitatorSystem Map
  2. 2

    Phase 2: Components and actors

    45 min

    Stickies for components (for example systems, tools, processes) and actors (for example teams, customers, suppliers). Arrange inside and outside boundary. Hint: If 50 components appear, aggregation is needed. Group similar components, detail in sub-map.

    FacilitatorDependencies
  3. 3

    Phase 3: Flows and relationships

    60 min

    Arrows between components. Arrow label: what flows (material, information, money, trust). Color per flow type. Hint: If all arrows look same, map is unreadable. Differentiate at least three flow types, colored or dashed.

    FacilitatorLeverage Points
  4. 4

    Phase 4: Pain points and constraints

    30 min

    Mark pain points (red): bottlenecks, conflicts, duplicate work. External constraints (for example regulation, market situation) at boundary edge. Hint: Pain points make map action-relevant. Map without pain points is inventory. At least three pain points mandatory.

    FacilitatorSystem Map
  5. 5

    Phase 5: Levers and actions

    30 min

    Identify leverage points inside boundary. For each top pain, one lever and concrete follow-up action with owner and deadline. Hint: Levers outside boundary are not influenceable. If all levers are outside, boundary is cut wrong.

    OwnerDependencies
  6. 6

    Publish artifact

    10 min

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

    OwnerSystem Map
Usable artifact

Session Brief

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

session-brief.md

Session Brief: Systems Mapping

Goal

Artifact: System Map

Working Question

Which components, actors and relationships form the system, where are boundaries, and which levers are changeable inside boundary?

Context

Description of system area; known components, actors and relationships; current pain points; data on flows (material, information, money); external influencing factors.

Setup

  • Format: Method session
  • Duration: 3-4 h
  • Mode: Workshop or async
  • Participants: One facilitator; 4-10 participants with different perspectives (internal, external, technical, business); one scribe; optional outsider as challenger.
  • Owner: One facilitator
  • 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 System Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with large open space; stickies in several colors for components, actors, flows, boundaries; labeled arrows; visible legend.

Preparation

Define system boundaries in writing (what is inside, what outside). Add legend. Rule: different element types use different colors. Label arrows (what flows).

Agenda

  1. Phase 1: Boundaries and purpose (30 min) Owner: Facilitator Action: System purpose and boundary in writing. What belongs to system (inside), what is environment (outside). Define time horizon. Hint: If boundaries blur, map is political. Clear decision with decider, otherwise every stakeholder draws boundary differently. Output: System Map

  2. Phase 2: Components and actors (45 min) Owner: Facilitator Action: Stickies for components (for example systems, tools, processes) and actors (for example teams, customers, suppliers). Arrange inside and outside boundary. Hint: If 50 components appear, aggregation is needed. Group similar components, detail in sub-map. Output: Dependencies

  3. Phase 3: Flows and relationships (60 min) Owner: Facilitator Action: Arrows between components. Arrow label: what flows (material, information, money, trust). Color per flow type. Hint: If all arrows look same, map is unreadable. Differentiate at least three flow types, colored or dashed. Output: Leverage Points

  4. Phase 4: Pain points and constraints (30 min) Owner: Facilitator Action: Mark pain points (red): bottlenecks, conflicts, duplicate work. External constraints (for example regulation, market situation) at boundary edge. Hint: Pain points make map action-relevant. Map without pain points is inventory. At least three pain points mandatory. Output: System Map

  5. Phase 5: Levers and actions (30 min) Owner: Owner Action: Identify leverage points inside boundary. For each top pain, one lever and concrete follow-up action with owner and deadline. Hint: Levers outside boundary are not influenceable. If all levers are outside, boundary is cut wrong. Output: Dependencies

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

Closeout

  • Update result artifact: System 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

System Map: Systems Mapping

Working Question

Which components, actors and relationships form the system, where are boundaries, and which levers are changeable inside boundary?

Context

Description of system area; known components, actors and relationships; current pain points; data on flows (material, information, money); external influencing factors.

Participants

  • Owner: One facilitator
  • Participants: One facilitator; 4-10 participants with different perspectives (internal, external, technical, business); one scribe; optional outsider as challenger.

Input

Whiteboard or Miro board with large open space; stickies in several colors for components, actors, flows, boundaries; labeled arrows; visible legend.

Template

Systems Mapping 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

  • System Map:
  • Dependencies:
  • Leverage Points:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • System 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

Systems Mapping Working Template

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

systems-mapping-working-template.md

Compact working template for Systems Mapping with context, input, output artifacts, and next step.

Systems Mapping 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

  • System Map:
  • Dependencies:
  • Leverage Points:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits System Map.
  • One version per iteration with date. Document changes to boundaries or components. Reference previous map in follow-up workshops.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet