# Wardley Mapping

A strategic mapping method that relates user needs, value-chain dependencies, and the evolution of components from novel to commodity.

- Type: method
- Domain: Strategy & discovery
- Level: Advanced
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/wardley-mapping/>)

## What it means

Wardley Mapping, created by Simon Wardley, visualizes a competitive landscape with user need and value-chain visibility on one axis and component evolution—from genesis through custom-built and product to commodity—on the other. Teams use the map to discuss situational awareness and strategic movement rather than produce a conventional process or architecture diagram.

## Why it matters

Product strategy often treats every capability as equally differentiating. A map can reveal where custom work supports genuine advantage, where mature utilities should be standardized or sourced, and how dependencies or market evolution may change strategic options.

## When to use it

Use it for technology-enabled strategy, platform choices, sourcing, capability investment, and evolving markets with meaningful value-chain dependencies. Avoid it when participants lack domain knowledge or when a simpler system map answers the decision.

## How it works

1. Name the users or stakeholders and the needs that anchor the map.
2. Identify the components required to meet those needs and connect their dependencies.
3. Place components vertically by visibility to the user and horizontally by evolutionary stage.
4. Examine inertia, constraints, climatic patterns, and likely movement across the landscape.
5. Generate strategic options for build, buy, standardize, differentiate, or reorganize.
6. Challenge assumptions with evidence and update the map as the landscape evolves.

## A practical example

A travel platform maps personalized itinerary advice near the user while placing identity, payments, hosting, and messaging beneath it. The team stops custom-building messaging infrastructure, invests in its distinctive recommendation capability, and monitors model services that are rapidly commoditizing.

## Where it breaks

Placement relies heavily on judgment, and maps can appear more objective than their evidence warrants. The method has specialized notation and concepts, does not quantify economics, and may encourage deterministic stories about how components evolve.

## Common mistakes

- Drawing a dependency diagram without anchoring it to a user need.
- Placing components by preference rather than evidence about evolution.
- Assuming custom-built components are inherently strategic.
- Treating the map as a static answer instead of a contested model.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/wardley-mapping/#visualization-wardley-mapping>)

## Sources

1. [Wardley Maps — Strategic Mapping for Business Evolution](<https://www.swardleymaps.com/>) — Wardley Maps · Creator-authorized official resource
2. [Introduction to Wardley Mapping](<https://learnwardleymapping.com/introduction/>) — Learn Wardley Mapping · Creator-licensed learning resource

## Related topics

- [Technology Strategy](<https://wiki.soroush.uk/topic/technology-strategy/>)
- [Competitive Advantage](<https://wiki.soroush.uk/topic/competitive-advantage/>)
- [Ecosystem Map](<https://wiki.soroush.uk/topic/ecosystem-map/>)
