What It Does
Wardley Mapping is a strategic planning technique created by Simon Wardley that visualizes the components of a business or technology landscape on two axes: the value chain (vertical, from user need to underlying components) and evolution (horizontal, from genesis through custom-built to product to commodity). By mapping components along these axes, decision-makers can identify strategic moves, predict market evolution, and make informed build-vs-buy decisions.
Unlike traditional strategy tools (SWOT, Porter’s Five Forces), Wardley Maps explicitly model the movement of components along the evolution axis, making it possible to anticipate when custom solutions will become commoditized and when new capabilities will emerge.
Key Features
- Value chain visualization: Maps dependencies from user needs through all underlying components
- Evolution axis: Classifies components as genesis, custom-built, product, or commodity
- Movement patterns: Identifies components that are evolving and in which direction
- Doctrine principles: Set of universally applicable strategic principles (e.g., use appropriate methods, manage inertia)
- Gameplay patterns: Strategic plays informed by component position (e.g., commoditize a competitor’s differentiator)
- Open framework: Free to use, Creative Commons licensed, with active community
Use Cases
- Technology leaders deciding build vs. buy for infrastructure components
- CTOs mapping their technology landscape to identify strategic investments
- Product managers understanding where their product sits in the broader value chain
- Teams evaluating when to adopt emerging technologies vs. waiting for commoditization
Adoption Level Analysis
Small teams (<20 engineers): Useful for founders and tech leads making foundational technology choices. Low overhead — a whiteboard or online tool suffices. The challenge is having enough context to map accurately.
Medium orgs (20–200 engineers): Strong fit. Wardley Maps help align engineering, product, and leadership on technology strategy. Maps can inform roadmap prioritization and team structure decisions.
Enterprise (200+ engineers): Excellent fit for strategic planning. Multiple maps can represent different business units or capability areas. Risk: maps can become complex and require dedicated facilitation to maintain.
Alternatives
| Alternative | Key Difference | Prefer when… |
|---|---|---|
| Tech Radar | Categorizes tools by adoption readiness | You want to track individual technology choices rather than map strategic landscapes |
| SWOT Analysis | Strengths/weaknesses/opportunities/threats | You need a quick strategic snapshot without component-level detail |
| Architecture Decision Records | Individual decision documentation | You need to record specific decisions rather than map the overall landscape |
Evidence & Sources
Notes & Caveats
- Wardley Maps require significant domain expertise to create accurately; garbage in, garbage out
- The evolution axis is subjective; reasonable people can disagree on where a component sits
- Maps are a snapshot in time and need regular updates as the landscape evolves
- No standardized tooling; maps are drawn in various tools from whiteboards to specialized apps
- The technique has a steep learning curve; the book is 19 chapters and community practice helps significantly