methodatlas
RunsheetSystems Thinking

Systems Mapping

ComplexityMedium
Time1-3 h
Participants3-12
FormatWorkshop + async
MaturityEstablished
01

Prerequisite

What needs to be finished first

Complete firstProblem areanot in catalog

A system area to map is bounded (for example logistics chain, onboarding process, platform ecosystem) with start and end criteria.

Without: Without boundary, group maps "the world" and delivers unusably large diagram.
Complete firstStakeholder Mapping

Essential stakeholders in system area are identified.

Without: Without stakeholder inventory, actors are missing and map becomes one-sidedly technical.
02

Preparation

What needs to be ready before start

Materials

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

People / roles

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

Pre-read

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

Time needed

3-4 h

Setup

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

03

Core question

The one question this method answers

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

04

Flow

Marker: Phase

StepDurationActionHint
1Phase 1: Boundaries and purpose
30 minSystem purpose and boundary in writing. What belongs to system (inside), what is environment (outside). Define time horizon.If boundaries blur, map is political. Clear decision with decider, otherwise every stakeholder draws boundary differently.
2Phase 2: Components and actors
45 minStickies for components (for example systems, tools, processes) and actors (for example teams, customers, suppliers). Arrange inside and outside boundary.If 50 components appear, aggregation is needed. Group similar components, detail in sub-map.
3Phase 3: Flows and relationships
60 minArrows between components. Arrow label: what flows (material, information, money, trust). Color per flow type.If all arrows look same, map is unreadable. Differentiate at least three flow types, colored or dashed.
4Phase 4: Pain points and constraints
30 minMark pain points (red): bottlenecks, conflicts, duplicate work. External constraints (for example regulation, market situation) at boundary edge.Pain points make map action-relevant. Map without pain points is inventory. At least three pain points mandatory.
5Phase 5: Levers and actions
30 minIdentify leverage points inside boundary. For each top pain, one lever and concrete follow-up action with owner and deadline.Levers outside boundary are not influenceable. If all levers are outside, boundary is cut wrong.
05

Artifact

What comes out at the end

Form

Systems Map as image plus Markdown companion with boundaries, component list, actor list, flow list, pain points, constraints, levers and action list with owner and deadline.

Versioning / ownership

One version per iteration with date. Document changes to boundaries or components. Reference previous map in follow-up workshops.

Tool alternatives
  • Miro or FigJam with stickies and frames
  • Kumu for interactive visualizations
  • draw.io or Lucidchart for more formal representation
  • Mentimeter or Mural for collaborative collection
  • Whiteboard.fi or Stormboard for remote setups

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.

06

Example output

Concrete filled scenario, fictional example

systems-mapping-beispiel.md

Concrete filled scenario, fictional example

Systems Map - Receipt intake tax firm Bertram, May 2026

Boundary: From client's receipt sending to DATEV booking. Time horizon 12 months.

Components (excerpt)

  • Client inbox (email, mailbox, app).
  • Firm receipt intake mailbox (5 sources).
  • DATEV Unternehmen Online.
  • Internal filing system (folder structure on NAS).
  • Receipt recognition (manual by Jana).

Actors

  • Clients (inside relationship, outside firm boundary).
  • Sabine (owner).
  • Jana (clerk).
  • DATEV support (external).

Flows

  • Material (paper receipts): client -> mailbox -> Jana.
  • Information (digital): client -> email -> Jana -> DATEV.
  • Money: client -> firm (fee).
  • Trust: bidirectional, dependent on response time.

Pain Points

  • Five receipt sources, no canonical intake point.
  • Manual sorting takes 4 h/week.
  • Clients often do not know which receipt is missing.

Constraints (external)

  • GDPR retention obligation.
  • DATEV interface format.

Levers and actions

  • SM-01: Canonical intake app for clients (Owner: Sabine, by 2026-07-31).
  • SM-02: Receipt checklist per client (Owner: Jana, by 2026-06-30).
  • SM-03: Quarterly review of intake points (Owner: Sabine).
07

Pitfalls

Recognize symptoms and steer against them

Trap

Boundaries blur

Symptom

Map grows, discussion drifts, nobody knows what still belongs.

What to do

Decider chooses boundary before start. On drift, facilitator interrupts. External elements clearly marked at edge.

Trap

Only technical components

Symptom

Actors missing, map looks like architecture diagram.

What to do

Mandatory actor phase. Ask per component: who interacts. At least five actors per map.

Trap

Arrows without label

Symptom

Lines between components without clear flow type, map unreadable.

What to do

Labels mandatory on arrows. What flows, in which direction, at which frequency. Colors for flow types.

Trap

Pain points skipped

Symptom

Map is clean, nobody feels addressed, no follow-up action emerges.

What to do

Explicit pain-point phase. Ask directly: where does friction emerge, where waiting time, where duplicate work. At least three red-marked spots.

Trap

Actions outside boundary

Symptom

Recommended levers affect factors that cannot be influenced.

What to do

Check each lever: is it inside boundary. If no, either cut boundary anew or discard action.

08

Stop criteria

Done signals checkable in under a minute

Boundaries cannot be defined, map becomes generic description.
Essential stakeholders not in workshop, outside perspective missing.
Decider unreachable, recommendations without mandate.
Map covers several independent systems, workshop loses focus.
Pain points cannot be articulated, method yields no action logic.
Timebox under 90 min, map remains incomplete.

Finished the runsheet?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.