Methods · 10/10
Wardley Mapping
A strategic map that plots user needs, the value chain and each component's stage of evolution—from genesis to commodity.
Purpose
Wardley Mapping answers a question most strategy tools skip: what is the business actually made of, and how is each part changing? A Wardley map arranges the components of a value chain on two axes. The vertical axis shows visibility to the user, from the immediate need down to invisible infrastructure. The horizontal axis shows evolution: genesis, custom-built, product, commodity. It is this second axis that makes the map strategic, because components at different evolutionary stages obey different rules—what is just emerging needs experimentation, while what has become commodity needs efficiency.
Developed by Simon Wardley in the mid-2000s out of his experience running an online photo service, mapping today serves above all as situational awareness before decision-making: where is building in-house justified, where is buying? Which components are predictably drifting towards commodity, and what does that mean for differentiation, sourcing and organisation? The map replaces opinions about strategy with a shared, criticisable representation of the starting position.
Procedure in five steps
- Anchor on user needs
The map's anchor is a concrete user and their needs—not the organisation's own product. Several user groups yield several anchors. Skipping this step produces a map of the organisation chart rather than of the business.
- Build the value chain
Starting from the need, list every component required to meet it, together with its dependencies. Order the chain vertically by visibility: user-facing elements at the top, infrastructure at the bottom. The result is a dependency graph of the business.
- Assess evolution
Place each component on the horizontal axis using observable market evidence—ubiquity, standardisation, number of suppliers—rather than internal self-perception. Mark contested placements; they usually contain the most interesting strategic questions.
- Add movement and patterns
Make the map dynamic: under competitive pressure, all components evolve to the right. Apply climatic patterns—for instance, that commoditisation enables new genesis built on top—and identify points of inertia where the organisation clings to old models.
- Derive the moves
Turn the map into concrete plays: outsource or standardise commodity components, protect differentiating ones, occupy emerging spaces with experiments. Justify decisions with the map, and keep the map current.
Strengths and limits
- The map makes implicit assumptions about the structure of the business explicit and therefore open to challenge.
- The evolution axis prevents one-size-fits-all strategy by showing that experimental logic and efficiency logic are both right—for different components.
- Business and IT share one representation in which sourcing, architecture and strategy questions converge.
- Climatic patterns allow reasoned anticipation where other tools merely describe the status quo.
- Component placement is judgement, not measurement—different teams draw different maps.
- The method has a steep learning curve; to newcomers the maps look hermetic and the vocabulary unwieldy.
- Every map is a snapshot and goes stale quickly without maintenance.
- The focus on components and evolution largely leaves out political, cultural and regulatory dynamics.
With AI and agents
The most expensive step in Wardley Mapping has always been drawing the map itself: reconstructing value chains from interviews and workshops takes weeks. Agents cut this drastically, because the necessary evidence usually already exists—in architecture documentation, contract databases, SaaS invoices, code repositories and process descriptions. An agent working through these sources delivers a draft map of components and dependencies in hours. People then correct and extend instead of starting from zero, and the discussion begins where it belongs: at the contested placements.
Evolution assessment, the method's most error-prone step, gains an independent cross-check. For each component, a language model can compile market evidence—supplier counts, degree of standardisation, open-source and API availability—and propose a reasoned placement. This exposes the common bias of treating one's own custom-built solution as differentiating when the market has long offered it as a product or commodity. Agents also take over maintenance: they watch supplier landscapes and flag evolutionary jumps, for example when a capability previously built in-house becomes available as an API service.
At the same time, AI is not only a tool for mapping but currently the strongest force on the evolution axis itself: language models are pushing whole classes of components—text processing, customer interaction, code generation—towards commodity, forcing a reassessment of almost every existing map. Human judgement remains irreplaceable at the anchor, the question of whose need counts, and in the actual gameplay: where to attack, what to abandon, which bet to place. The map informs those decisions; it does not make them.
Relation to scenarios
Wardley Mapping and scenario analysis handle uncertainty in complementary ways. The map anticipates, through climatic patterns, what will happen with high probability—the evolution of components towards commodity. Scenarios cover the rest: regulatory ruptures, geopolitical shifts, demand discontinuities that follow no pattern. In combination, a future map is drawn for each scenario, and today's moves—sourcing decisions, platform bets, in-house builds—are tested for viability across all of them. This joins the structural precision of mapping with the environmental breadth of scenario work.
How ready is your organization for AI and agents? — Take the AI Readiness Check