A general who can't see the battlefield is just guessing with confidence. So is a leadership team that sets strategy from a list of priorities and a SWOT grid, both useful, neither a map. Wardley mapping fixes a specific, common blindness: it shows you where each piece of your business sits and which way it's drifting, so the move you pick is a response to the landscape rather than a hope laid over it.

The quick version

  • What it is. A map with two axes: a value chain (user needs at the top, the things that support them below) plotted against how evolved each component is, left to right.
  • What it's for. Situational awareness, a shared picture of the terrain, before anyone debates strategy. It shows position and where each piece is heading, which a static list never does.
  • The core insight. Everything evolves left-to-right, from novel to commodity. You differentiate on the new bits and ruthlessly standardise the old ones.
  • The honest limit. A map is a model, not the truth. It can launder opinion into fact if no one's allowed to challenge it. Its value is the argument, not the artefact.

The idea in depth

Wardley mapping is named after Simon Wardley, who developed the technique at the software company Fotango around 2005 after working out the underlying evolutionary framing the year before (Wikipedia: Wardley map). The method is set out across a series of nineteen essays, published free as the book Wardley Maps on Medium under a Creative Commons licence, and it starts from a complaint Wardley makes about most corporate strategy: it skips the step a soldier would never skip. As he puts it, "strategy without an understanding of the context (i.e. without situational awareness) is pretty much worthless" (Wardley, "An Introduction to Wardley 'Value Chain' Mapping," 2015).

Two axes: needs down, evolution across

A Wardley map is built from two simple movements. First you anchor on a user need at the top, then chain downward through everything required to meet it, the visible product, the platforms beneath it, the raw infrastructure beneath those. That vertical axis is the value chain, ordered by visibility to the user. Second, and this is the part other tools miss, you slide each component along a horizontal evolution axis with four stages: genesis (brand new, uncertain, one-of-a-kind), custom-built (understood enough to build deliberately), product (off-the-shelf, many vendors), and commodity (a utility you barely think about, like electricity from a socket).

The point of the second axis is that components don't sit still. Under the pressure of supply and demand, they march rightward, from rare and wonderful to ubiquitous and boring. Wardley's evolution axis runs "from 'genesis' through 'custom build' and 'product' to 'commodity'," and crucially it's measured by certainty, not time: a thing is more evolved when it's well-understood and standard, not merely when it's old.

So the move is: before your next planning session, draw the chain for one product on a whiteboard and place every box on the genesis-to-commodity line. The disagreements that surface, "wait, you think our billing is custom-built and I think it's a commodity?", are the entire payoff. You've just found where two leaders were quietly planning against different worlds.

quadrantChart
    title A Wardley map, in miniature
    x-axis "Genesis" --> "Commodity"
    y-axis "Invisible" --> "Visible to user"
    quadrant-1 "Stable & seen"
    quadrant-2 "Emerging & seen"
    quadrant-3 "Emerging & hidden"
    quadrant-4 "Stable & hidden"
    "Customer-facing app": [0.42, 0.92]
    "Recommendation model": [0.2, 0.66]
    "Payments": [0.82, 0.55]
    "Compute / hosting": [0.9, 0.2]
Higher = closer to the user; further right = more of a commodity. The map's job is to show position and drift. Leaders Loop

Why "situational awareness" is the real product

Wardley borrows the phrase deliberately from military thinking. He cites John Boyd's OODA loop, Observe, Orient, Decide, Act, as "probably the only truly universal" strategy technique he's found useful, and a map is mostly a tool for the first two steps: it forces you to observe the landscape and orient against it before you let anyone leap to decide (Wardley, 2015). The deeper title he uses for his keynote on the subject, "Crossing the River by Feeling the Stones", after Deng Xiaoping, captures the stance: you can't plan a route across terrain you can't see, so first make the terrain visible, then feel for the next stone.

This is also where Wardley mapping earns its place next to the rest of the strategy canon rather than replacing it. A SWOT or a Five Forces analysis tells you about a position at a moment; a Wardley map adds the one thing they leave out, direction of travel. Position without movement is a photograph of a race.

"Strategy without an understanding of the context, without situational awareness, is pretty much worthless.", Simon Wardley

From map to move: doctrine and gameplay

A map is the start, not the answer. In Wardley Maps, the picture feeds a wider strategy cycle: once you can see the landscape, you apply doctrine (universal good practices that apply almost everywhere, for instance, use appropriate methods for each stage of evolution) and then gameplay (context-specific moves you choose because of what this map shows). The most repeated piece of doctrine is the simplest: build the novel, genesis-stage work in-house where differentiation lives; rent the product-stage pieces; and buy the commodity-stage pieces as a utility. Trying to lovingly hand-craft your own electricity is a way to lose.

So the move is: for every component you mapped, ask one question, "is this where we should be spending our cleverness?" Cleverness spent on the right-hand, commodity side of the map is cleverness wasted. The map turns a vague "we should focus" into a list of specific things to stop custom-building.

The honest limitation. A Wardley map looks authoritative, and that's its risk. Critics note that the process can let a confident team "launder assumptions into facts" and "delegitimise challenge" while feeling rigorous (Wikipedia: Wardley map). Where a component sits on the evolution axis is a judgement, not a measurement, and two reasonable people will place the same box differently. The defence is the same as the purpose: a map is only useful if it's drawn to be argued with, in pencil, by people allowed to move the boxes. Treat it as settled truth and you've built a prettier version of the problem it was meant to solve.

A worked example

Take a mid-sized online grocer, call it FreshRun. All figures below are illustrative, used to show the method, not real company data. The leadership team is split: half want to build a bespoke AI delivery-routing engine in-house; half want to ship faster and worry it's a distraction. Instead of arguing from conviction, they map it.

The user need at the top is "get my shopping, on time, today." Chaining down: the storefront app (a product, plenty of capable platforms), the routing optimisation (arguably custom-built shading toward genesis if they use a novel AI approach), the warehouse management system (a mature product), and the compute it all runs on (a pure commodity, nobody's building their own data centre). Drawn out, the argument resolves itself: the storefront and warehouse software are commoditising, so hand-crafting either burns cleverness on the wrong side of the map. The routing engine, by contrast, is the one component sitting far enough left to be a genuine differentiator if customer density makes it worth it.

flowchart TD
    A(["User need: groceries, on time, today"]) --> B(["Storefront app, product"])
    A --> C(["Delivery routing, custom / genesis"])
    B --> D(["Warehouse system, product"])
    C --> D
    D --> E(["Compute & hosting, commodity"])
FreshRun's chain. The single box far enough left to matter is the routing engine; everything below it is something to buy, not build. Leaders Loop

The map didn't make the decision, the team did. But it turned "build vs. buy, everywhere" into one sharp question: is delivery routing far enough toward genesis, and valuable enough, to justify being the one thing we build ourselves? That's a question you can actually answer with data, and it's invisible on a priorities list.

Frequently asked questions

Is Wardley mapping just a fancy value chain or capability map?

No, and the difference is the whole point. A value chain or capability map shows you what you have and how it connects. A Wardley map adds the evolution axis, which shows you which way each piece is moving and therefore how you should treat it. Position plus movement is a different tool from position alone.

Do I need software to draw one?

Not to start. A whiteboard, sticky notes and an hour beat a polished diagram every time, because the value is in the disagreement, not the artefact. Free tools like Online Wardley Maps exist once you want to share and version them, but the first map should be cheap, fast and wrong-in-useful-ways.

How is this different from SWOT, PESTLE or Five Forces?

Those frameworks describe a position at a moment, strengths, external forces, industry structure. Wardley mapping is complementary: it adds direction of travel and a view of the whole value chain at once. Use the diagnostic frameworks to assess where you stand, and a Wardley map to see where the ground is shifting under you.

What's the most common mistake?

Treating the map as an answer instead of an argument. The second-most common is placing components by gut and never re-checking, especially calling something "custom" because your team built it, when the market now sells it as a commodity. If your map can't be challenged, it isn't doing its job.

Where does it fit in a real planning cycle?

Early. Map the landscape first to build shared situational awareness, then move into doctrine ("are we using the right method for each stage?") and gameplay (the specific bets). It sits upstream of goal-setting, which is why it pairs naturally with work on strategic intent.

Related in the Toolkit

Where to go next