Wardley Mapping
Also known as: Wardley Maps, Value Chain Mapping, Situational Awareness Mapping
A strategic mapping technique that visualizes the components needed to serve a user need, arranged by their position in the value chain (visibility) and their stage of evolution (genesis to commodity), revealing strategic options and moves.
Quick Reference
Memory Aid
Map user needs → components → evolution stage. Build what's novel, buy what's commodity.
TL;DR
Map all components needed to serve a user need, arranged by visibility (top to bottom) and evolution (genesis to commodity). Identify strategic moves: build novel components, outsource commodities, anticipate evolution-driven disruption.
What Is Wardley Mapping?
A Wardley Map is like a geographical map for your business. It shows all the components needed to serve your users, arranged from visible (user-facing) at the top to invisible (infrastructure) at the bottom, and from new/uncertain (left) to mature/commodity (right). This reveals where to invest, what to outsource, and where disruption will come from.
All models are wrong, but some are useful. Wardley Maps are useful because they provide situational awareness — the ability to see the landscape before making strategic decisions.
— Simon Wardley
Wardley Maps use two axes: the vertical axis represents the value chain (user needs at top, underlying components below), and the horizontal axis represents evolution (Genesis → Custom → Product → Commodity). Every component moves from left to right over time — today's innovation becomes tomorrow's commodity. By mapping components and their evolutionary stage, leaders can anticipate market movements, identify strategic plays (e.g., commoditize a competitor's value proposition), and make build-vs-buy decisions based on evolutionary position.
Wardley Map Structure
A map with user needs at the top (visibility), components arranged by value chain (vertical) and evolution stage (horizontal: Genesis → Custom → Product → Commodity).
A map with user needs at the top (visibility), components arranged by value chain (vertical) and evolution stage (horizontal: Genesis → Custom → Product → Commodity).
Origin & Context
Developed by Simon Wardley while he was CEO of Fotango (a Canon subsidiary). Frustrated by the lack of situational awareness in business strategy, he created Wardley Maps inspired by military mapping and Sun Tzu's principles.
Core Components
User Needs
The anchor point at the top of the map — what the user actually needs.
Example
For an e-commerce business: 'Buy products conveniently and receive them quickly.'
Components
Everything needed to fulfill the user need — activities, practices, data, and knowledge.
Example
Website, payment processing, inventory management, logistics, customer support.
Evolution Axis
The stage of maturity for each component: Genesis (novel), Custom (bespoke), Product (standardized), Commodity (utility).
Example
Cloud computing has evolved from Custom (2000s) to Product (AWS 2006) to Commodity (2020s).
Movement
All components evolve from left (genesis) to right (commodity) over time due to supply and demand competition.
Example
Computing: mainframe (genesis) → client-server (custom) → cloud (product) → serverless (commodity).
Did You Know?
Simon Wardley developed Wardley Mapping while CEO of a cloud computing company in 2005, frustrated that existing strategy tools like SWOT and Porter's Five Forces didn't show how things change over time. He open-sourced the entire methodology, refusing to patent or commercialize it — leading to its grassroots adoption across government and enterprise.
When to Use Wardley Mapping
Technology strategy and build-vs-buy decisions
Problem it solves: Reveals which components to build (novel/differentiated) and which to buy/use commodity (mature).
Real-World Application
Mapping an application architecture reveals that the team is building a custom authentication system (evolved to commodity). Switching to Auth0 frees engineering to focus on genesis-stage components that differentiate.
Anticipating market disruption
Problem it solves: Shows where component evolution will create disruption opportunities.
Real-World Application
Mapping the automotive industry in 2015 would show 'powertrain' evolving from combustion (product) toward electric (product/commodity), signaling the disruption Tesla was driving.
The most powerful strategic move on a Wardley Map is 'industrialization' — taking a component that competitors treat as custom and turning it into a commodity, which shifts the competitive landscape in your favor. AWS did this with cloud infrastructure.
How to Apply Wardley Mapping: Step by Step
Before You Start
- →Understanding of your users and their needs
- →Knowledge of your value chain components
- →Awareness of component evolution stages
Identify User Needs
Start with the user and their needs — anchor the top of the map.
Tips
- ✓Be specific about the user and the need
Common Mistakes
- ✗Starting with technology instead of user needs
Map the Value Chain
List all components needed to serve the user need and arrange by visibility.
Tips
- ✓Include activities, data, knowledge, and practices — not just technology
Common Mistakes
- ✗Only mapping technical components
Assess Evolution
Place each component along the evolution axis based on its maturity.
Tips
- ✓Use characteristics (ubiquity, certainty, publication of best practices) to assess stage
Common Mistakes
- ✗Confusing age with evolution — old components can still be custom
Identify Strategic Moves
Look for opportunities: components to industrialize, areas to invest, threats from evolution.
Tips
- ✓Ask: 'What happens when this component evolves to the next stage?'
Common Mistakes
- ✗Creating the map but not using it for strategic decisions
Value & Outcomes
Primary Benefit
Provides situational awareness for strategic decisions by visualizing the landscape of components and their evolution.
Additional Benefits
- ✓Reveals build-vs-buy decisions based on component maturity
- ✓Anticipates market disruption by tracking evolution
What You'll Learn
- →How to map and visualize your strategic landscape
- →How component evolution drives market dynamics
Typical Outcomes
Best Practices
📋 Preparation
- •Start with user needs, not technology
- •Gather input from across the organization
🚀 Execution
- •Map the current state honestly
- •Don't over-engineer the first map — it's a tool for thinking
🔄 Follow-Up
- •Update maps as components evolve
- •Use maps in strategic planning conversations
💎 Pro Tips
- •The map is a conversation tool, not a finished diagram. Its value is in the strategic thinking it provokes.
UK Government Digital Service
The UK Government Digital Service (GDS) used Wardley Mapping to transform how the government delivers digital services. By mapping the technology landscape, they identified that many agencies were building custom solutions for commodity problems (like identity verification and payments). This led to the creation of shared platforms like GOV.UK Pay and GOV.UK Verify, saving hundreds of millions of pounds.
Limitations & Pitfalls
Subjective — evolution positioning requires judgment
Mitigation: Use team consensus and evolution characteristics to guide placement
Steep learning curve for first-time mappers
Mitigation: Start with simple maps and iterate as understanding grows
Apply Wardley Mapping with Stratrix
Turn this framework into a professional strategy deck in under a minute. Stratrix applies Wardley Mapping automatically to your business context.
Try Stratrix Free