Wardley Mapping keeps coming up more and more often in conversations about strategy, but it's surrounded by a certain haze: many have heard of it, few have seen it applied, and almost nobody can clearly explain what it's good for in day-to-day work. Is it a serious strategy tool or just another fad in visual management? In this article we try to answer honestly: what it is, what problem it solves, how organizations that adopt it actually use it, where it fits in an agile context, and what it has to do with the rise of artificial intelligence.
The problem Wardley Mapping tries to solve
Most of the strategy tools we use —SWOT analysis, business model canvases, OKRs— share a limitation: they don't show the landscape we compete on or how that landscape changes. They are lists or tables, not maps. And a list doesn't tell you where you stand relative to your rivals or where the pieces are moving.
Simon Wardley, who developed the method while running a technology company in the mid-2000s, started from a concrete discomfort: he was making strategic decisions without really understanding the terrain. His critique, which he documents in his work Wardley Maps —published openly as a series of essays and freely available— is that in war and in chess nobody would make decisions without a map, yet in business we do it constantly, replacing the map with opinions, anecdotes and management fads.
For Wardley, a map must meet two conditions that common tools don't: be visual and be anchored to something (in geography, north; in his method, the customer), so that the relative positions of elements carry meaning and movement can be anticipated.
How a Wardley Map is built (in essence)
Without pretending to be a complete tutorial, it's worth understanding the logic in order to judge its usefulness. A Wardley Map is built in three steps.
First, you identify the user and their need. The whole map hangs from there; it is the anchor, equivalent to geographic north.
Second, you lay out the value chain: the components needed to satisfy that need, linked according to who depends on whom. This is represented on the vertical axis, from most visible to the user (top) to most invisible and infrastructural (bottom).
Third —and this is what sets it apart— each component is placed on the horizontal axis according to its stage of evolution: genesis (something new, uncertain, experimental), custom-built, product or rental, and finally commodity or utility (something standardized, ubiquitous, consumed without thinking, like the electricity from a power socket).
What's valuable is that this position is not static: everything tends to evolve to the right, from novel to commoditized, driven by competition and supply. A map is not a snapshot; it is the basis for anticipating movement.
Why the evolution axis changes decisions
Wardley's most practical contribution is that how you should manage something depends on what evolutionary stage it is in. What is in genesis is not managed the same way as what is a commodity.
What is in genesis requires experimentation, tolerance for failure, exploratory teams; trying to plan it with precision is absurd because the uncertainty is irreducible. What is a commodity requires efficiency, standardization, cost optimization; treating it as an exploratory adventure is waste. Wardley calls these profiles "pioneers, settlers and town planners", drawing on an idea also developed by Robert X. Cringely: organizations that need three different types of teams for three different phases of evolution.
Here Wardley Mapping connects with a critique very present in the agile community: applying the same method to everything. A map helps you see which parts of the product call for exploratory agility while others call for industrialized execution, and that forcing a single model onto the whole landscape is a strategic mistake, not just an operational one.
Who actually uses it, and how?
Here we need to be honest, because the question in the title is legitimate: does anyone really use it?
Adoption of Wardley Mapping is real but uneven, and concentrated in certain profiles. British public administrations were pioneers: the UK's Government Digital Service incorporated it to decide what to build in-house and what to consume as a commoditized service, a decision with enormous public cost implications. In the technology world, it is frequently used in architecture and build-vs-buy decisions: the map makes it evident that building in-house something that is already a commodity (such as, for years, server infrastructure) wastes resources instead of taking advantage of what the market already offers in standardized form.
In practice, organizations that adopt it tend to use it in three situations:
The first is investment and architecture decisions: where to put your own effort and where to rely on providers. The map turns a debate of opinions into a conversation about the evolution of components.
The second is strategic communication across areas: a map is a shared artifact that business and technology people can look at together, something scarce in organizations with silos. Here its value is almost conversational: the map doesn't decide, but it orders the debate.
The third is anticipating movements in the environment: since components evolve to the right in a predictable way, the map lets you ask what will be a commodity in a few years and position yourself accordingly.
It's also worth being frank about its adoption limits. Wardley Mapping has a real learning curve, depends heavily on the judgment of whoever draws it, and there is no dominant standard tool or certification that institutionalizes it. This explains why, despite its value, it remains more known than practiced. It is a thinking tool, not a process that can be imposed top-down.
Wardley Mapping and artificial intelligence: a textbook case
Few times has a tool found such a timely moment. The rise of generative AI is, in Wardley's terms, a component in full evolution, and understanding which stage each piece is in is exactly what the method helps clarify.
A few years ago, building AI capabilities was in the genesis or custom-built stage: it required specialized teams, in-house infrastructure, costly experimentation. Today, a large part of those capabilities have been commoditized at an astonishing speed: access to powerful language models is consumed as a utility, through an API, just as we consume electricity. What was an exploratory competitive advantage has become infrastructure available to everyone.
A Wardley Map helps you ask a crucial strategic question in this context: which part of our AI-based offering is truly differentiating (genesis, where it's worth investing) and which part is already a commodity (where building it in-house is waste)? Many organizations are investing enormous resources in building custom AI components that the market already offers in standardized form, while neglecting the layer where they could truly differentiate: their domain knowledge, their data, their understanding of the user.
The map doesn't give the answer, but it formulates the right question. And in strategy, formulating the right question is almost everything. For agile teams exploring how to integrate AI into their work —the territory of ScrumIA— this distinction between what is differentiating and what is commoditized keeps effort from being spent where it brings no advantage.
Is it for your organization?
Not every organization needs Wardley Mapping, and it's worth saying so. If your context is stable, your value chain is simple and your strategic decisions are few and clear, the method may be more sophistication than necessary.
It is especially useful when several conditions come together: there are significant investment or architecture decisions on the table; there are silos between business and technology that make strategic conversation difficult; the environment evolves fast and it's worth anticipating movements; and there is someone with the curiosity and rigor to invest in learning to use it well. AI, given its speed of evolution, has meant that more organizations meet these conditions than did a few years ago.
Like any tool, its value depends less on the tool itself than on the quality of thinking of whoever uses it. A poor strategist with a map is still a poor strategist; but a good strategist without a map is making decisions blindly about terrain they could see.
Wardley Mapping is neither magic nor a fad. It is a serious attempt to bring into management something we take for granted in any expedition: a map of the terrain before deciding the route. Its greatest virtue is not the drawing technique, but the discipline of thought it imposes: anchoring on the user, seeing the full value chain, and recognizing that each component is managed differently depending on how evolved it is.
Its adoption remains a minority, and that is information in itself: it requires judgment, patience and a culture willing to make its strategic assumptions explicit. But at a time when AI is reordering at full speed what is differentiating and what is commodity, the ability to map that movement may be more valuable than ever.
Do you use it in your organization? And if you tried it and dropped it, what held you back: the learning curve, the lack of strategic culture, or that it simply didn't solve a problem you had?
Comments (0)
Log in to your Scrum Manager area to comment