Wardley Mapping

Status: Documented, not shipped · Evidence: C · Family: Strategy and opportunity · Verdict: reject (2026-06-03)

Wardley Mapping (licensed CC BY-SA 4.0 by Simon Wardley). Simon Wardley (Wardley Mapping).

What it is

A Wardley map is a strategy diagram with two axes that mean different things. The vertical axis is a value chain: start from a user need at the top and chain downward through the components that fulfil it, each component depending on the ones below it, so the picture is a dependency stack anchored to a need rather than a free-floating box-and-arrow. The horizontal axis is evolution: each component is placed along a left-to-right scale of how mature-and-commoditised it is - Genesis (novel, just invented), Custom-Built (bespoke, hand-made), Product (off-the-shelf, including rental), and Commodity / Utility (standardised, metered, taken for granted). The deliverable is a single map on which every component sits at a height (how close to the user need) and a horizontal position (how evolved), with dependency lines between them.

The durable cognitive move underneath the diagram is worth separating from the branded packaging, because they are not the same thing. The move is: decompose what you provide into a need-anchored dependency chain, then locate each piece on a maturity-to-commodity gradient, and reason about strategy from where things sit and which way they are drifting. The strategic payoff the method claims is twofold. First, situational awareness - you can see the whole landscape on one page and notice, for example, that you are hand-building (Custom) something the rest of the market now buys as a commodity. Second, anticipation - because components tend to drift rightward over time (genesis becomes custom becomes product becomes commodity), the map invites you to play moves against that drift: industrialise what is commoditising, defend or invest where genesis is creating new value, and avoid being the firm still custom-building what everyone else rents.

So the honest description holds two layers apart. The underlying operations - decompose by dependency, and sort items by maturity-and-commoditisation - are general and recombinable. The packaging - the specific two-axis canvas, the four named evolution stages, the accompanying catalogue of “doctrine” (universal good practices) and “gameplay” (context-specific plays) and “climatic patterns” (predictable market movements) - is the branded Wardley Mapping system, released by its author under an open licence. The grade and the verdict below turn on that distinction: the operations are familiar, and the branded packaging carries a confident, evolution-flavoured precision that the evidence does not back.

When it helps / when it misleads

As a stance, the map helps when a team is making a build-versus-buy-versus-rent call across a stack of capabilities and keeps treating every component the same way. Sorting components by how commoditised they are is a genuinely useful corrective: it surfaces the embarrassing case (you are custom-building a thing the market sells as a utility) and the opportunity case (an emerging component you could own before it commoditises). It is sharpest in technology-platform and digital-sourcing decisions - which is exactly the domain it was invented for - and it pairs naturally with a heavier downstream method (a scenario set for the futures, an options comparison for the decision).

It misleads or wastes effort when:

• The map’s confidence outruns its inputs. The horizontal placement of a component is a judgement call, and the method offers no measurement to settle it - reasonable people place the same component in different stages, and the four crisp stage boundaries imply a precision the underlying judgement does not have. The most pointed published criticism, recorded on the method’s own encyclopedia entry, is that the process can let people “launder assumptions into facts, delegitimise challenge, and still create consensus” - a polished one-page map can make a contestable guess look settled. That false-precision risk is the central reason this entry is gated.
• The picture is mistaken for the analysis. A map locates and describes; it does not decide. It has no mechanism to weight components, price a bet, or value a market. A beautiful map of a tiny or shrinking opportunity is still a poor decision, and the diagram will not tell you so.
• It is run as a ritual without the situational judgement it presumes. Drawing the canvas, naming four stages, and reciting “doctrine” is the cargo-cult failure: the form is reproduced without the strategic reading that gives it value. The method’s own author warns repeatedly against copying practice without understanding context, and a map produced as a checklist is precisely that.
• It is pointed at a problem that already has a sharper tool. If the job is to hold several uncertain external futures in parallel, the disciplined method is scenario-planning. If it is to trace what one change sets off, that is the futures-wheel. If it is simply to decompose a question into a dependency or category tree, that is an issue-tree. The map’s evolution axis is its one genuinely distinctive element; everything else it does is a flatter version of a tool the catalog already has.

What the evidence says

The honest grade for the move - “map components on a need-anchored value chain against an evolution-to-commodity axis” - is C (conceptual), and the grading has to be careful, because Wardley Mapping is widely adopted and has an articulate body of writing behind it, but that is not the same as tested.

What the record supports. The method is real, named, openly documented, and genuinely used. It originates in a concrete commercial setting (below), it has a substantial free book and an active practitioner community, and it influenced at least one named policy document, the UK government “Better for Less” paper (Maxwell et al., 2010), which fed into early UK Government Digital Service thinking. As a structured way to picture a sourcing landscape and prompt a build-buy-rent conversation, it is a coherent and plausibly useful practitioner technique.

What the record does NOT support, and the laundering trap. There is no controlled or comparative study I can locate that tests the method itself - “do teams that draw a Wardley map make better strategic decisions than teams that do not?” - against any alternative. The literature is of two kinds, and neither grades the move upward: (1) the method’s own corpus - Wardley’s blog series, the Creative-Commons book, and community guides - which is explanation and advocacy by the author and adopters, not independent evaluation; and (2) descriptive applications (a map of this industry, that platform) which demonstrate use, not effect. The most-cited empirical-sounding claim inside the corpus is Wardley’s own report that between roughly 2006 and 2007 he plotted more than 6,000 activities on a certainty-versus-ubiquity space and extrapolated the evolution curve from that data. That is a self-reported, un-peer-reviewed exercise by the method’s author, never independently replicated or published as a study; it is the empirical backstop for the evolution axis, and it cannot carry the axis above a conceptual grade on its own. The conservative governing grade is therefore C: a coherent, documented conceptual framework, no controlled evidence for its own move, with the author’s data exercise noted but not counted as independent validation.

Transfer caveat (required). All of the adjacent material is from human strategists and organisations in technology, sourcing, and government-IT settings; none of it studies a Wardley map produced by or with an AI agent. The evidence is transferred from human contexts and is not validated for AI-augmented use.

Excluded figures (required). No traceable, author-and-year effect size for the method’s decision impact exists; any “Wardley Mapping improves strategic outcomes by N%” framing has no primary source and is excluded as fact. The “6,000+ data points” figure is recorded above only as the author’s own self-report of how the evolution axis was derived, explicitly not as an independent measure of the method’s effectiveness, and it does not move the grade.

Why it is / is not a skill here

Verdict: Reject; status flag (documented with attribution and licence caveat, not shipped). This overturns the placeholder P-tier framing some unexamined strategy candidates carried; on research the move neither clears the evidence bar nor adds a distinct general operation, and what is genuinely distinctive about it is the very thing that makes it risky to ship.

Two gates close in sequence.

Evidence and false-precision gate. A skill in this library has to clear an evidence-and-honesty bar. Wardley Mapping is graded C - coherent and adopted, but with no controlled test of its move and only the author’s self-reported data exercise behind its signature axis. On top of the thin evidence sits a specific honesty hazard the registry names directly: cargo-cult risk and false precision. The four crisp evolution stages and the polished one-page canvas invite exactly the failure its own encyclopedia entry records - “launder assumptions into facts, delegitimise challenge, and still create consensus.” Shipping a think- skill that renders contestable judgement calls as a confident, stage-labelled map would manufacture precision the evidence does not support, which is the opposite of what this library is for. That alone gates it to documentation rather than a product.

Distinctness gate. Even setting evidence aside, the map decomposes into operations the catalog already ships plus a domain remainder:

• The dependency-chain decomposition is issue-tree. Anchoring to a user need and chaining downward through the components that fulfil it is a need-rooted dependency tree - the choose-your-axis decomposition issue-tree already owns. The need-anchoring is a preset root, not a new mechanism.
• The evolution-to-commodity sort is the one distinctive element, and it is a maturity-rating heuristic, not a separable cognitive move. Placing each component on a Genesis-to-Commodity scale is rating items against a fixed four-stage taxonomy - structurally the same pattern the catalog declined in cognitive-bias-checklist and in the moat lens’s barrier menu: a taxonomy is a prompt, not a move. It is the content (the specific evolution stages) that is unique to Wardley, not the cognitive operation (sort against a named scale).
• The strategic-reading remainder is competitive-and-platform-strategy domain content, which the library routes to pm-skills. The candidate sits in the strategy-and-opportunity family, whose registry header reads “weakest cross-domain fit; many defer to pm-skills.” Every in-family competitive frame is already routed away - porters-five-forces, blue-ocean-tools, and jobs-to-be-done are flag / reject; swot is excluded; moat-defensibility-lens is reject-to-pm. The map’s “doctrine and gameplay” layer is the same kind of object: business-and-platform strategy whose value is the domain knowledge, which is pm-skills’ charter, not a general thinking move.

Why flag rather than fold, build, or a clean reject. A fold into issue-tree would over-claim, because issue-tree carries the dependency decomposition but not the evolution axis, and the axis is the branded, under-tested, cargo-cult-prone element - folding it in would import precisely the hazard the first gate excludes. A build would ship a C-grade, false-precision-prone, domain-heavy method into a library that has deliberately rejected every sibling of that kind. A bare reject would under-serve the reader, because the method is famous, openly licensed, and genuinely instructive about how a thinking tool can mislead. So the honest service is to document it fully and with attribution: point the dependency decomposition to issue-tree, the futures reasoning to scenario-planning, and the competitive-strategy content to pm-skills, while flagging the licence and the false-precision caveat. The learning value of the NO: a celebrated, openly-shared, articulate strategy method can still be documented-not-shipped when its evidence is conceptual and its most distinctive feature is the very thing - confident stage labels on a contestable map - that a precision-honest library refuses to manufacture.

Lineage and who to read

Wardley Mapping was created by Simon Wardley in 2005, while he was CEO of Fotango, a Canon-owned software company in the UK; he had developed the evolutionary framing the year before. The company was profitable but Wardley felt he lacked any real situational awareness of where it was heading, and - asking why military commanders use maps but business strategists rarely do - he built a value-chain-plus-evolution map as the answer. He refined the work at Canonical (UK) between 2008 and 2010, and its concepts appear in the “Better for Less” paper (Liam Maxwell with Jerry Fishenden, Mark Thompson, Simon Wardley and others, September 2010), a critique of UK government IT spending that fed early UK Government Digital Service thinking.

Wardley has released the method openly: the canonical text is his blog-series-turned-book, commonly cited as Simon Wardley, Wardley Maps (the “Bits or Pieces?” series, 2015 onward; collected as a Creative-Commons book), provided free in print, PDF, and ebook and licensed Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0). Wardley frames the work as “a community, it is not some money making machine for myself - it’s a gift,” and CC BY-SA is its governing licence: derivative work must attribute Simon Wardley and share alike. “Wardley Mapping” and “Wardley map” are named after their author and used here descriptively, with attribution; this entry is flagged as branded for that reason.

Named sources

• Simon Wardley, Wardley Maps (the “Bits or Pieces?” / blog.gardeviance.org series, 2015 onward; collected as a free Creative-Commons book), licensed CC BY-SA 4.0. The canonical and most complete account of the method, its two axes, the four evolution stages, and the doctrine / gameplay / climatic-patterns catalogue. Author’s own corpus - explanation and advocacy, not independent evaluation. (C)
• Simon Wardley, “On Diffusion and Evolution” and “On mapping and the evolution axis” (blog.gardeviance.org, 2014-2015). Where Wardley reports plotting more than 6,000 activities on a certainty-versus-ubiquity space (circa 2006-2007) and extrapolating the evolution curve. The empirical backstop for the evolution axis; self-reported, un-peer-reviewed, never independently replicated. Cited to locate the axis’s basis and its limits. (C)
• Liam Maxwell, Jerry Fishenden, William Heath, Jonathan Sowler, Peter Rowlins, Mark Thompson and Simon Wardley, Better for Less: How to make Government IT deliver savings (September 2010). A policy paper applying mapping-style evolution thinking to UK government IT; evidence of real-world adoption and influence, not an effectiveness study. (Practitioner / applied)
• “Wardley map,” Wikipedia. Records the origin (Fotango, 2005), the open Creative-Commons status, and the principal published criticism: that the process can let people “launder assumptions into facts, delegitimise challenge, and still create consensus.” Cited for the false-precision caveat that gates this entry. (Reference / critical)

Excluded under the evidence rule: there is no traceable author-and-year effect size for the method’s decision impact, so any “Wardley Mapping improves outcomes by N%” framing is excluded as fact. The “6,000+ data points” figure is the author’s own self-report of how the evolution axis was derived, recorded as lineage and explicitly not counted as independent validation of the method’s effectiveness.