A system area to map is bounded (for example logistics chain, onboarding process, platform ecosystem) with start and end criteria.
Systems Mapping
Prerequisite
What needs to be finished first
Essential stakeholders in system area are identified.
Preparation
What needs to be ready before start
Whiteboard or Miro board with large open space; stickies in several colors for components, actors, flows, boundaries; labeled arrows; visible legend.
One facilitator; 4-10 participants with different perspectives (internal, external, technical, business); one scribe; optional outsider as challenger.
Description of system area; known components, actors and relationships; current pain points; data on flows (material, information, money); external influencing factors.
3-4 h
Define system boundaries in writing (what is inside, what outside). Add legend. Rule: different element types use different colors. Label arrows (what flows).
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?
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Boundaries and purpose | 30 min | System 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 min | Stickies 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 min | Arrows 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 min | Mark 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 min | Identify 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. |
Artifact
What comes out at the end
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.
One version per iteration with date. Document changes to boundaries or components. Reference previous map in follow-up workshops.
- 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.
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).
Pitfalls
Recognize symptoms and steer against them
Boundaries blur
Map grows, discussion drifts, nobody knows what still belongs.
Decider chooses boundary before start. On drift, facilitator interrupts. External elements clearly marked at edge.
Only technical components
Actors missing, map looks like architecture diagram.
Mandatory actor phase. Ask per component: who interacts. At least five actors per map.
Arrows without label
Lines between components without clear flow type, map unreadable.
Labels mandatory on arrows. What flows, in which direction, at which frequency. Colors for flow types.
Pain points skipped
Map is clean, nobody feels addressed, no follow-up action emerges.
Explicit pain-point phase. Ask directly: where does friction emerge, where waiting time, where duplicate work. At least three red-marked spots.
Actions outside boundary
Recommended levers affect factors that cannot be influenced.
Check each lever: is it inside boundary. If no, either cut boundary anew or discard action.
Stop criteria
Done signals checkable in under a minute
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.