Complete firstClear scope
Agree the subject, boundary and decision before filling the model.
A broad or mixed scope produces a misleading model.
Method guideSystems Thinking
Wardley Mapping
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
Time1-3 h
Participants2-10
FormatWorkshop + async
MaturityEstablished
01
Prerequisite
What needs to be finished first
Complete firstAccess to relevant evidence
Bring source material and people who know the work; distinguish facts from assumptions.
Unverified interpretations become false certainty.
02
Preparation
What needs to be ready before start
Materials
Shared visual workspace, source evidence, and an agreed decision question.
People / roles
Mapper, domain experts, users or service owners, strategy decision-maker.
Pre-read
Collect existing data, examples, constraints and relevant stakeholder perspectives.
Time needed
2–4 h for one strategic domain; gather evidence and review separately.
Setup
State the user, user need and strategic purpose before drawing capabilities. Trace dependencies from user need down through capabilities; label links. Place components on visibility and evolution axes using evidence, not aspiration. Discuss environmental climate and applicable doctrine against map positions. Choose small strategic plays, assumptions, owners and signals to revisit.
03
Core question
The one question this method answers
How does user need connect to components, and how evolved are they?
04
Flow
Phases with goal, actions, output and pitfall
Maps user needs, value-chain dependencies and component evolution to inform strategic choices.
Wardley map: components and evolution
Fictional worked example
Fictional, online appointment booking: user need “find an available follow-up” (top, visible). Dependencies: slot selection → availability → practice calendar → cloud infrastructure. Evidence-based positions: slot selection Custom, calendar integration Product, cloud infrastructure Commodity. Strategic question: does slot selection demonstrably differentiate, or should effort go into reliable calendar data?
| Scenario | User need | Component | Dependency | Evolution | Strategic play |
|---|---|---|---|---|---|
| Component 1Record an observation or example for this row. | Find follow-up | Slot selection | Practice calendar | Custom (fictional position) | Check differentiation with usage evidence |
1. User need
- Component 1
- Find follow-up
2. Component
- Component 1
- Slot selection
3. Dependency
- Component 1
- Practice calendar
4. Evolution
- Component 1
- Custom (fictional position)
5. Strategic play
- Component 1
- Check differentiation with usage evidence
Fictional, online appointment booking: user need “find an available follow-up” (top, visible). Dependencies: slot selection → availability → practice calendar → cloud infrastructure. Evidence-based positions: slot selection Custom, calendar integration Product, cloud infrastructure Commodity. Strategic question: does slot selection demonstrably differentiate, or should effort go into reliable calendar data?
- 1
Purpose
State purpose and user need
Goal
Purpose statement
Inputs for this step
- Strategic question, beneficiaries and users
Actions
- Name who benefits, the need being met and the decision the map should support.
Output
Purpose statement
Purpose statement
Quality check
Is the need stated from the user’s perspective?
Pitfall
A product idea is presented as a need. Ask what outcome users need without the proposed solution.
Timing: Allow time according to scope and evidence; no universal duration.
- 2
Chain
Draw value chain and dependencies
Goal
Labelled value chain
Inputs for this step
- Purpose and people who know the landscape
Actions
- Trace capabilities needed to meet the user need and connect actual dependencies from top to bottom.
Output
Labelled value chain
Labelled value chain
Quality check
Is each component needed for the user need?
Pitfall
The map becomes an unconnected component list. Remove irrelevant elements and add missing dependencies.
Timing: Allow time according to scope and evidence; no universal duration.
- 3
Evolution
Place visibility and evolution
Goal
Wardley Map with justified positions
Inputs for this step
- Value chain, market signals and technical evidence
Actions
- Place user need on the visibility axis and capabilities from Genesis through Custom and Product to Commodity using evidence.
Output
Wardley Map with justified positions
Wardley Map with justified positions
Quality check
Does evidence support evolution rather than aspiration?
Pitfall
Strategic importance is confused with market maturity. Record observation and uncertainty for each position.
Timing: Allow time according to scope and evidence; no universal duration.
- 4
Plays
Derive climate, doctrine and plays
Goal
Strategic options with review signal
Inputs for this step
- Map, relevant market forces and organizational capabilities
Actions
- Assess climate and doctrine against the map; state a few plays and the signal that would disconfirm each assumption.
Output
Strategic options with review signal
Strategic options with review signal
Quality check
Does each play lead to a testable action?
Pitfall
The map remains a static illustration. Name movement, owner and observation date.
Timing: Allow time according to scope and evidence; no universal duration.
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Maps user needs, value-chain dependencies and component evolution to inform strategic choices. Record scope, evidence, assumptions, owner and next review in the versioned artifact.
Versioning / ownership
Record scope, date, participants, source version and owner. Note changed assumptions and the reason for each revision.
Tool alternatives
- Shared whiteboard or paper template
- Source links, records or measurement data
wardley-mapping-working-template.md
Prepare the decision, source evidence and next review.
Wardley Mapping: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Run the method Time: See catalog planning range; no universal duration.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Shared visual workspace, source evidence, and an agreed decision question.
- Roles: Mapper, domain experts, users or service owners, strategy decision-maker.
- Advance information: Collect existing data, examples, constraints and relevant stakeholder perspectives.
- Overall time needed: 2–4 h for one strategic domain; gather evidence and review separately.
- Setup: State the user, user need and strategic purpose before drawing capabilities. Trace dependencies from user need down through capabilities; label links. Place components on visibility and evolution axes using evidence, not aspiration. Discuss environmental climate and applicable doctrine against map positions. Choose small strategic plays, assumptions, owners and signals to revisit.
Prepare for the work steps
Purpose: State purpose and user need
- Strategic question, beneficiaries and users
Chain: Draw value chain and dependencies
- Purpose and people who know the landscape
Evolution: Place visibility and evolution
- Value chain, market signals and technical evidence
Plays: Derive climate, doctrine and plays
- Map, relevant market forces and organizational capabilities
Wardley map: components and evolution
| Scenario | User need | Component | Dependency | Evolution | Next question |
|---|---|---|---|---|---|
| Component 1 |
- Component 1: Record an observation or example for this row.
Evolution positions are hypotheses until supported by market evidence.
Introduction · Learn Wardley Mapping
Purpose: State purpose and user need
Expected artifact: Purpose statement
Purpose statement
Entry:
...
- Is the need stated from the user’s perspective?
Chain: Draw value chain and dependencies
Expected artifact: Labelled value chain
Labelled value chain
Entry:
...
- Is each component needed for the user need?
Evolution: Place visibility and evolution
Expected artifact: Wardley Map with justified positions
Wardley Map with justified positions
Entry:
...
- Does evidence support evolution rather than aspiration?
Plays: Derive climate, doctrine and plays
Expected artifact: Strategic options with review signal
Strategic options with review signal
Entry:
...
- Does each play lead to a testable action?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/wardley-mapping/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
wardley-mapping-beispiel.md
Concrete filled scenario, fictional example
Fictional, online appointment booking: user need “find an available follow-up” (top, visible). Dependencies: slot selection → availability → practice calendar → cloud infrastructure. Evidence-based positions: slot selection Custom, calendar integration Product, cloud infrastructure Commodity. Strategic question: does slot selection demonstrably differentiate, or should effort go into reliable calendar data?
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- State purpose and user needA product idea is presented as a need.View in phase
- Draw value chain and dependenciesThe map becomes an unconnected component list.View in phase
- Place visibility and evolutionStrategic importance is confused with market maturity.View in phase
- Derive climate, doctrine and playsThe map remains a static illustration.View in phase
Trap
State purpose and user need
Symptom
A product idea is presented as a need.
What to do
Ask what outcome users need without the proposed solution.
Trap
Draw value chain and dependencies
Symptom
The map becomes an unconnected component list.
What to do
Remove irrelevant elements and add missing dependencies.
Trap
Place visibility and evolution
Symptom
Strategic importance is confused with market maturity.
What to do
Record observation and uncertainty for each position.
Trap
Derive climate, doctrine and plays
Symptom
The map remains a static illustration.
What to do
Name movement, owner and observation date.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Stop if the decision question or scope is disputed; align it first.
Stop if key inputs are unavailable; list what evidence is needed.
Stop if the group treats assumptions as observed facts.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.