Wardley Mapping

Overview

Wardley Mapping was developed by Simon Wardley while he was CEO of Fotango, a Canon subsidiary, in the early 2000s. Wardley found himself unable to communicate clearly about strategy without understanding the competitive landscape his organization operated in — and unable to find any tool that combined business model, competitive position, and the evolutionary dynamics of markets in a single view. He developed the mapping method out of necessity and documented it extensively in blog posts and in Wardley Maps (2020, self-published under Creative Commons).

The core insight: components evolve. Everything in a value chain — technology, practices, data, knowledge — moves over time through predictable stages from novel to commodity. Most strategy frameworks treat components as static; Wardley Maps treat them as dynamic, which has profound implications for where and how to compete.

The Two Axes

• Y-axis (Value Chain): vertical position represents visibility to the user. Components at the top are directly visible and valuable to the customer; components at the bottom are infrastructure the customer doesn't see but the top depends on.
• X-axis (Evolution): horizontal position represents evolutionary stage, left to right:
  • Genesis — novel, uncertain, rare; no one has figured this out yet
  • Custom-built — bespoke, specific to a few organizations; expertise-intensive
  • Product — increasingly standardized, sold off-the-shelf by multiple vendors
  • Commodity/Utility — standardized, widely available, often consumed as a service (compute, electricity, logistics)

The strategic implications of position on the evolution axis:

• Genesis components are sources of genuine competitive differentiation — and are expensive and uncertain to manage
• Custom-built components offer competitive advantage but require internal expertise and are transitioning toward product
• Product components should typically be bought, not built — building what can be purchased cheaply is waste
• Commodity/Utility components should be outsourced or consumed as services — spending engineering effort to build what Amazon Web Services commoditizes is strategic malpractice

When to Use It

When the client's question involves technology strategy, build vs. buy vs. partner decisions, competitive positioning in dynamic markets, or organizational design in technology-intensive industries. Particularly powerful for technology companies, digital transformations, and any strategy conversation where the pace of change in underlying components is material to competitive position.

How It Works

1. Identify user needs — start with what the customer or user actually needs; these anchor the top of the map.
2. Map the value chain — identify the components required to meet those needs and the dependencies between them. Build downward from user needs to underlying enablers.
3. Assess evolutionary stage — for each component, estimate where it sits on the evolution axis. Is this available as a commodity service? As a standard product? Or does it require custom development? Is it genuinely novel?
4. Identify strategic patterns — where are there opportunities to commoditize (use what others have built at low cost)? Where does the map show components that are valuable and still at Genesis or early Custom-built — these are your actual differentiators?
5. Define strategic moves — which components should you invest in? Which should you stop building and start buying? Where is the organization investing in components that competitors can replicate cheaply?
6. Check for inertia — where is the organization investing in components that are already Products or Commodities? This is where strategic waste is hiding — and often where incumbents are most vulnerable to disruption.

Common Pitfalls

• Mapping for completeness rather than insight — Wardley Maps can become exhaustively detailed; the value is in what the map reveals about strategic choices, not in the inventory itself
• Ignoring evolution dynamics — the static picture is less valuable than asking "how fast is this component moving right, and what does that imply for our investment timeline?"
• Treating all Genesis components as strategic — being early on the evolution curve is valuable only when the component connects to user needs high on the value chain; low-value Genesis work is still low-value
• Applying it to slow-moving industries without adaptation — Wardley Mapping is most powerful in dynamic, technology-intensive markets; in slower industries the evolution axis compresses and matters less

Recommended Books

• Wardley Maps — Simon Wardley
• Crossing the Chasm — Geoffrey Moore
• The Innovator's Dilemma — Clayton Christensen