What needs to be finished first
A clearly formulated strategy question or business decision with 6-24 month horizon exists in writing.
Anchor needs of relevant user groups are documented and prioritized.
What needs to be ready before start
Whiteboard or Miro with Wardley-map template (X-axis Evolution: Genesis, Custom-Built, Product, Commodity; Y-axis Value Chain Visibility); stickies; connecting lines; example maps.
One facilitator with Wardley experience; two to five people with domain knowledge; one strategy owner with decision mandate; optional external sparring partner for bias check.
Strategy question; known anchor users and their needs; component inventory (make/buy/use); market analysis on component maturity; previous Wardley experience.
3-4 h for first map, then 1-2 h per iteration
Y-axis upward means visible to users, downward invisible to users. X-axis evolution. Place anchor top right. Use consistent notation.
The one question this method answers
Which components of the value chain move toward commodity in the next 12-18 months, and which strategic moves follow?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Anchor and users | 20-30 min | Identify user groups and place their top needs as anchors in the upper right of the map. Several anchors allowed, but each needs its own chain. | Anchors are user needs, not product names. Product names belong in the chain, not at the top. |
2Phase 2: Value chain | 45-60 min | From anchor downward, derive components that fulfill the need. One card per component, positioned vertically by visibility. | Components are capabilities or building blocks, not teams. If list maps to org chart, it is too organization-heavy. |
3Phase 3: Classify evolution | 60-90 min | Estimate evolution stage per component: Genesis, Custom-Built, Product, Commodity. Require market evidence. | Evolution is not where we are, but where the market is. Own custom solution for commodity need must still be placed as commodity. |
4Phase 4: Movement and climate | 30-45 min | Add movement arrows to the right per component based on market maturity and climate signals. Name climate patterns. | Movement without evidence is assumption. Each arrow needs indicator: new provider, falling prices, open-source alternative. |
5Phase 5: Strategic moves | 30-45 min | Derive options per movement: build, buy, outsource, pioneer, settle, town plan. Decide one to three moves for next 6 months. | A map without a move is only beautiful inventory. Decider must be present. |
What comes out at the end
Wardley Map as image or Miro board with anchor, value chain, evolution positions, movement arrows, and climate patterns plus report with strategy options, decisions, and next spikes.
Map per strategy question and date. Keep old version archived. Strategic moves receive IDs referenced in OKRs or roadmap.
Compact working template for Wardley Mapping with context, input, output artifacts, and next step.
What is this method used for?
Which question should be answered at the end?
Which data, observations, or materials are available?
Owner, date, success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Strategy question: Should we operate our own vector DB or use managed service, horizon 18 months?
Anchor (users): Enterprise customers need semantic search across internal documents with SLA 99.9% and EU hosting.
Value Chain: Semantic search -> Embedding service -> Vector DB -> Compute -> Electricity.
Evolution:
Moves:
Recognize symptoms and steer against them
Map starts with Platform X instead of user need.
Rewrite anchor as need. Product name belongs in the chain.
Components are placed where own team has them, not where market is.
Require market evidence per component.
Static map shows current state, no arrows, no climate statement.
At least three arrows with evidence. Without movement it is inventory.
Workshop ends with map and no binding move.
Decider mandatory in phase 5. At least one decision with owner and date.
Map contains 80+ components.
Maximum 12 components per anchor. Use sub-maps when needed.
Map confirms a decision already made.
Use external sparring partner or red team. Explicitly reject at least one counter-option with rationale.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.