Wardley Mapping: How to Map Your Strategy

Wardley mapping is a visual strategy method that plots every component of your value chain against an evolution axis, from brand-new and unpredictable to fully commoditized and invisible. Unlike a slide deck full of bullet points, a Wardley map forces you to see your business as a set of moving pieces, each drifting toward commodity over time, and each carrying a different risk profile depending on where it sits.

Simon Wardley developed the approach around 2005 while running Fotango, a cloud precursor inside Canon. He was trying to answer a question most executives still struggle with: "Where should we actually focus?" His answer was situational awareness, borrowed from military strategy, applied to technology and business landscapes.

What is Wardley mapping?

A Wardley map is a value chain plotted on a two-dimensional canvas. The Y axis shows visibility to the end user: components at the top are things the user directly experiences, while components further down are the infrastructure or capabilities that make the top-layer work. The X axis shows evolutionary stage: how mature, standardized, and widely available each component is.

You draw lines between components to show dependencies. Then you look at what each component's evolution stage implies about how you should treat it. A component in the early "genesis" phase needs exploration and experimentation. One in "commodity" is best bought off the shelf. The map makes those distinctions visible at a glance.

Key terms:

• Value chain: the ordered set of components needed to deliver a user need
• Evolution axis: the X axis running from genesis through custom-built, product, and commodity
• Doctrine: universal good practice (e.g., "be transparent", "use appropriate methods") that applies regardless of context
• Climatic patterns: market forces that act on every map the same way (e.g., "everything evolves toward commodity")
• Situational awareness: knowing where you and your competitors actually stand before deciding what to do

Key Facts

• Only 37% of senior leaders say their organizations can execute on strategic priorities effectively, according to Gartner (2023).
• McKinsey research found that 70% of strategy execution failures trace back to poor organizational alignment, not bad strategy itself (McKinsey Quarterly, 2021).
• Companies that practice systematic situational awareness in technology strategy are 2.5x more likely to outperform peers in digital transformation maturity (Deloitte Digital Transformation Survey, 2023).

The two axes: value chain and evolution

The Y axis is about user visibility. Place what the user directly sees and uses near the top. Backend systems, supplier relationships, and technical infrastructure sit lower. This ordering matters because the user doesn't care how the plumbing works. But you, as a strategist, need to know which invisible component could knock the whole value chain offline.

The X axis tracks evolutionary maturity across four stages:

The insight Wardley keeps repeating: components don't stay put. Everything moves left to right over time. Compute power was a custom engineering challenge in the 1990s. By 2010 it was a product (licensed servers). By 2020 it was commodity cloud. A strategy that treats commodity components as custom-built wastes resources. A strategy that treats emerging components as if they were commodity misses the opportunity to build a defensible position.

Wardley mapping vs other strategy tools

Most strategy tools analyze a snapshot. Wardley maps show movement.

The practical difference: SWOT tells you that "technology infrastructure" is a strength or a weakness. A Wardley map tells you exactly which infrastructure components are heading toward commodity (and should be outsourced) and which are still in genesis (and might become a competitive moat if you invest now). That specificity is what makes it useful for decisions, not just diagnosis.

If you use value chain analysis today, you can layer Wardley mapping on top of it. Your value chain activities become the Y axis. The evolution stages give each activity a time dimension the original Porter framework never provided.

Similarly, scenario planning pairs naturally with Wardley maps. Scenarios describe possible futures. Wardley maps let you test which components in your current value chain are vulnerable in each scenario.

How to create a Wardley map

Step 1: Identify the user and the need

Start with the person who consumes what you produce. Not a segment, not a persona: a specific user with a specific need. Write it at the top of your canvas. Everything else on the map exists to serve that need. If you skip this step, the map becomes a technology diagram with no strategic anchor.

Step 2: Map the value chain

Work backwards from the user need. What does the user interact with? What does that component depend on? Keep asking "what does this need to work?" until you reach infrastructure. Each component gets a node. Draw dependency lines between them. At this stage, don't worry about where components sit on the X axis. Just get the chain visible.

Step 3: Place components on the evolution axis

Now assign each component a position along genesis, custom-built, product, or commodity. Use these signals to guide placement. Is the component well-understood and widely available? Commodity or product. Is it something only a few organizations have figured out? Custom-built. Is it brand-new and actively being invented? Genesis.

This step is the hardest. Teams often argue about placements, which is a feature, not a bug. The disagreement surfaces hidden assumptions.

Step 4: Analyze movement and inertia

Expect every component to move right over time. Ask: what's moving fastest? What's being blocked from moving by internal inertia (legacy systems, skill gaps, contracts)? Inertia is a major source of strategic risk. It's also where incumbents lose to new entrants who are unencumbered by legacy.

If a competitor is treating a product-stage component as commodity and you're still building it yourself, you're wasting resources. Conversely, if a component is still in genesis and you're treating it like a commodity by outsourcing to a single vendor, you're building dependency at the worst possible time.

Step 5: Apply doctrine and climatic patterns

Doctrine is context-free best practice. Things like "use the most appropriate method for each component stage," "build small, autonomous teams around user needs," and "never mistake a map for reality." Doctrine applies regardless of what your map looks like.

Climatic patterns are predictable forces that act on every industry: everything commoditizes, ecosystems evolve faster when supply-side shifts occur, higher-order systems emerge from commodity components. Recognizing these patterns helps you anticipate movement rather than just react to it.

Step 6: Decide strategic plays

Now you can make concrete decisions. Should you build or buy a capability? Build, borrow, or buy frameworks work much better when you know a component's evolution stage. You don't buy a genesis capability (no product exists yet). You don't build a commodity one (waste of time and money).

Other plays include: accelerating commoditization of a competitor's advantage (open-sourcing something they rely on), investing in genesis components that will become your future moat, or divesting custom-built components that are commoditizing and no longer defensible.

Wardley mapping examples

Theory makes more sense when you see it in context. Here are three scenarios where teams apply Wardley maps to real decisions:

These examples share a pattern: the map makes visible what was previously invisible, what should be bought vs. built, and where unique investment creates lasting advantage.

This connects directly to competitive advantage: your defensible position lives in the components that are still in custom-built or genesis stages. Once they become commodity, competitors can replicate them. Disruptive innovation often works exactly this way, using newly commoditized components to undercut incumbents who are still over-investing in them.

Benefits and limitations

Benefits:

• Forces you to be specific. You can't hand-wave your way through a Wardley map. Every component needs a position, and that position implies a decision.
• Exposes inertia. Teams often discover they're spending most of their engineering budget on commodity components because legacy systems make it feel necessary.
• Aligns teams. A shared map replaces 20 slide decks of competing priorities with a single view everyone can argue against or build on.
• Works at multiple scales. You can map a single product, a business unit, or a whole company.
• Pairs well with other tools. Use it with jobs-to-be-done for user need validation, scenario planning for future-state modeling, or blue ocean strategy for identifying uncontested spaces.

Limitations:

• Steep initial learning curve. The mapping syntax is not intuitive, and most teams need a few sessions before the maps start producing insights rather than confusion.
• Requires honest placement. If your team is politically invested in a project, they'll place it in a more flattering evolution stage than it deserves.
• Maps go stale. Technology and market conditions shift. A Wardley map from 18 months ago may be actively misleading if you haven't updated it.
• Hard to scale to very large organizations. You can map a product or a business unit. Mapping an entire enterprise of 50,000 people produces a picture too complex to act on without segmenting it first.

The strategy map and the balanced scorecard are better fits when you need to communicate strategy to the whole organization. Wardley maps shine most in technology and product strategy, where component-level visibility drives the most important investment decisions.

Frequently asked questions

Is Wardley mapping free?

Yes. Simon Wardley published the method under a Creative Commons license. The book is free online at wardleymaps.com. No software license or certification is required to start.

What software do teams use to create Wardley maps?

The most popular tools are OnlineWardleyMaps (free, open-source, built specifically for this method), Miro and Mural (general whiteboarding tools with community templates), and plain drawing tools like Excalidraw or Google Slides for quick sessions. Some teams use dedicated tools like MapScript or Wardley Maps AI for automated placement suggestions.

How does a Wardley map differ from a value chain analysis?

A traditional value chain analysis shows where in your operations value is added, but treats the chain as static. A Wardley map adds the evolution axis, which turns a snapshot into a strategic trajectory. You can see which parts of your chain are commoditizing and adjust your investment accordingly. They answer different questions: value chain analysis asks "where do we create value now?" while Wardley mapping asks "where will value come from, and what should we do before competitors figure it out?"

Can non-technical teams use Wardley mapping?

Yes, though most examples come from technology and operations contexts. Business units have used Wardley maps for supply chain strategy, organizational design, and even regulatory response. The method works wherever you have a user need, a set of interdependent capabilities, and a question about what to invest in.

How does Wardley mapping fit with OKRs?

They work well together. Wardley maps tell you where to focus. OKRs give you a mechanism to commit to that focus and measure progress. A common pattern: run a mapping session at the start of a planning cycle to identify the highest-leverage evolution plays, then write OKRs around those insights rather than defaulting to last year's priorities.

---

Strategy tools are most useful when they force you to be specific about things you'd prefer to leave vague. Wardley mapping does exactly that. It asks you to name every component your business depends on, decide where each one sits on an evolution curve, and then explain your investment decisions in light of that map. That discipline, applied regularly, is what separates organizations that spot the next shift before it happens from those that react to it after competitors already have.

For further reading on the tools that work alongside a Wardley map, see value-chain analysis, scenario planning, build, borrow, or buy, and how the flywheel effect compounds the advantages a map helps you spot.