Wardley mapping, created by Simon Wardley, gives strategists a shared visual language for two questions that rarely get answered together: what does our value chain actually depend on, and how mature is each of those dependencies?
Most strategy conversations happen at the wrong altitude. Leaders debate which technologies to invest in without a clear picture of where those technologies sit in their lifecycle — or how that position will change. Wardley maps make both dimensions explicit, on a single canvas.
The two axes
A Wardley map has two axes. The vertical axis is the value chain: user-visible needs sit at the top, and the underlying components that enable them descend toward the bottom. This axis answers the question of visibility — what the user cares about versus what is hidden infrastructure.
The horizontal axis is evolution. Wardley identified four stages a component moves through over time: genesis, custom-built, product, and commodity. A component in genesis is novel and poorly understood — activity around it is experimental, costly, and uncertain. As it matures into custom-built, practitioners develop repeatable approaches but each implementation is still bespoke. The product stage brings standardized offerings and competition on features. Commodity is the final stage: the component is ubiquitous, interchangeable, and competes almost entirely on price and reliability.
The direction of travel on the horizontal axis is one-way. Technology components move from left to right as understanding accumulates, supply chains mature, and competitive pressure commoditizes what was once rare. The rate of movement varies, but the direction does not reverse.
How to read a map
Place every component your value chain depends on as a node, then draw lines between them to show dependency. A node toward the top and left of the map represents something that is visible to users and still in early stages — a high-stakes, high-uncertainty dependency. A node toward the bottom and right is mature, largely invisible infrastructure that should cost little to source and should not be the site of strategic differentiation.
The map immediately surfaces mismatches. If a component that users do not directly experience is still being built custom when a commodity version exists, the organization is spending engineering effort on undifferentiated work. Conversely, if a component close to the user need is already a commodity in the broader market, treating it as a proprietary asset is likely a strategic trap — competitors can source the same capability at low cost.
Reading a map is also about reading movement. Wardley maps are not static snapshots; they are meant to be annotated with anticipated shifts. Marking where a node is expected to move over the next few years makes the strategic choices explicit: invest before the commodity transition, harvest margin while it is still possible, or prepare for disruption from below.
Applying it to technology bets
The practical value of Wardley mapping in technology strategy is that it forces precision about timing. A technology bet is not simply a judgment that a capability will matter — it is a judgment about where that capability currently sits on the evolution axis, how fast it is moving, and what the implications are for your position when it arrives at commodity.
For components in genesis or early custom-built stages, the strategic logic is to explore: build narrow prototypes, monitor the field for signals of acceleration, and avoid over-committing capital before the dominant design emerges. For components approaching the product-to-commodity transition, the logic shifts to exploit: extract value from current differentiation, begin sourcing commodity alternatives, and reallocate the engineering effort that will be freed up.
Wardley maps also illuminate second-order effects. When a component commoditizes, it typically enables a new layer of innovation to emerge above it — new genesis-stage capabilities that were not economically viable before the underlying layer became cheap and reliable. Spotting that pattern early, before the enabling commodity transition is complete, is one of the more powerful uses of the framework.
This is where the map connects directly to technology intelligence. Signals in patents, research publications, investment flows, and regulatory activity can indicate which components are approaching an evolution stage transition. The map provides the structural context; the signals provide the timing evidence.
Limits of the method
Wardley mapping is a sense-making tool, not a prediction engine. Several limitations are worth holding alongside its strengths.
First, placing components on the evolution axis requires judgment. There is no objective measure of how far along a technology is. Practitioners in the same organization will disagree, and that disagreement is often productive — but it means maps should be treated as working hypotheses rather than established facts.
Second, the framework assumes a broadly competitive market where commoditization pressures operate. In heavily regulated sectors, or where monopoly dynamics apply, the evolution curve can stall or be distorted. The map needs to account for those structural forces explicitly.
Third, building an accurate map requires genuine knowledge of your value chain's dependencies — not just the obvious layers, but the ones that sit three or four levels below the user-visible surface. That depth of knowledge is often missing, and a map built on incomplete inputs can produce false confidence.
Finally, a map reflects the world as it is understood at the time of drawing. Technology evolution can be punctuated by events — a breakthrough publication, a regulatory change, a large-scale adoption decision — that shift a component's position faster than anticipated. Maps need to be revisited regularly, not filed as finished deliverables.
Used with those caveats, Wardley mapping is one of the more rigorous tools available for structured thinking about technology positioning. It does not replace the need for continuous intelligence — it gives that intelligence a place to land.
Keep exploring: return to the Frameworks pillar for more analytical tools, read how the technology adoption lifecycle complements the evolution axis, or see how CanaryIQ supports corporate strategy teams putting these frameworks into practice.