Wardley map
A Wardley map places user needs at the top, the components that serve them underneath, and positions each component by how evolved it is: genesis, custom-built, product, or commodity.
The purpose is strategic argument. Two people who disagree about a map are usually disagreeing about strategy, which is exactly what you want made visible.
#When to reach for one
Strategy conversations that keep going in circles.
Build versus buy decisions, where evolution is the deciding factor.
Explaining why the same component should be treated differently over time.
#How to draw it in Capable
Route | Use when |
|---|---|
draw.io | Precise positioning on both axes, which is the whole point. |
Excalidraw | Workshop mapping where components move during the session. |
#The evolution axis
Stage | What it looks like | How to treat it |
|---|---|---|
Genesis | Novel, uncertain, changing weekly | Experiment; expect waste |
Custom-built | Built for you, still bespoke | Iterate; measure |
Product | Several vendors, differentiated | Buy; configure |
Commodity | Utility, priced by usage | Rent; stop thinking about it |
#A few things that catch people out
Anchor at the user need. A map that starts from your components maps your org chart, not your strategy.
Position is an argument. Record who placed each component and why.
Movement matters more than position. Draw where you expect a component to be in two years.
#Related
Editable during the meeting beats pretty afterwards.
