Wardley Mapping and Strategic Situational Awareness
1. Overview
A. Definition
Wardley Mapping is a visual strategy technique proposed by Simon Wardley. It arranges the value an organization delivers as a value chain anchored by user needs on the vertical axis, and places each component's evolution stage—moving through Genesis → Custom-Built → Product/Rental → Commodity/Utility—on the horizontal axis, rendering the entire business landscape as a single map. The essence of a map is that it expresses both position and movement, which distinguishes it from a mere diagram and makes it a true "map."
Wardley Mapping matters because it targets a fundamental limitation shared by most strategy tools: they operate without situational awareness. Tools such as SWOT, the BSC, and the Business Model Canvas merely list or classify elements; they cannot show spatially "where we are now and what is moving where." It is like a general commanding a battle with only a troop-deployment table and no terrain map. By possessing a map's three essentials—anchor (users), position (place in the value chain), and movement (evolution)—Wardley Mapping drags strategy out of the realm of "intuition and rhetoric" and into the realm of "observation and reasoning."
B. Background and Necessity
Wardley Mapping arose around 2005 from Simon Wardley's experience as the CEO of a photo-sharing company, when he kept asking himself whether his company's strategy was actually sound. He noticed that the then-popular strategy frameworks all skipped straight to action (what to do) without asking about the current position. It was like advising someone to "play aggressively" in chess without ever looking at where the pieces stood. Combining Sun Tzu's line that "he who knows the terrain and the weather makes victory complete" with the observation that each element in a value chain commoditizes over time, he devised a map that captures position and movement together.
Three forces make this technique more urgent today. First, rapid commoditization driven by cloud, open source, and generative AI. The "custom-built → product → utility" shift that once took years is now compressed into months, so yesterday's differentiating capability routinely becomes today's commodity part. Second, the intensification of platform and ecosystem competition. Because we must handle composite systems in which components sit at mixed evolution stages rather than a single product, deciding what to build in-house versus delegate to an external utility requires terrain awareness first. Third, the need for strategic communication. When executives, developers, and procurement teams speak about strategy in different languages, a single map offers common ground for discussion. In this sense Wardley Mapping is required not as a mere analytical tool but as a common language for decision-making and organizational alignment in an age of commoditization.
C. Key Characteristics
The first characteristic of Wardley Mapping is that the horizontal axis is evolution, not time or maturity. Evolution is not chronological progress but the degree to which something diffuses and standardizes through supply-and-demand competition, so the same technology may sit at different positions depending on context. Second, a map is context-specific. The same "electricity" may be a utility for a data-center operator yet still at the custom/product stage for a renewable-energy R&D firm, so you cannot simply copy another company's map.
Third, Wardley Mapping aims to be an imperfect but useful tool. A map is not a perfect prediction but a discussion board for drawing out better questions and hypotheses—a falsifiable document that you revise once it is shown to be wrong. Fourth, maps are drawn iteratively and collaboratively. They are not artifacts completed alone; the value lies in the very process of stakeholders gathering to argue over where components sit.
Fifth, Wardley Mapping makes the flow of capital visible. Here "capital" means not only money but the organization's entire pool of resources—people, time, and attention. By seeing which components investment is piled onto, you can check at a glance whether you are "wasting resources expensively self-producing something already commoditized" or "neglecting the Genesis area, the source of differentiation, for lack of investment."
Because of these five characteristics, Wardley Mapping works not as a "template that gives answers" but as a training tool that exercises an organization's strategic-thinking muscle. In particular, by providing a common visual language to organizations that previously exchanged strategy only in words, it simultaneously raises the quality and the speed of discussion.
2. Overall Structure — The Map's Two Axes and Components
A Wardley map is a picture that places components as points on a two-dimensional plane—with visibility (the value chain: top = visible to the user, bottom = invisible underlying components) on the vertical axis and evolution stage (left = Genesis, right = Commodity) on the horizontal axis—and connects dependencies with lines. The overall structure is as follows.
flowchart TB
U["User"] --> A["Anchor: user needs"]
A --> VC["Value chain (vertical): need to visible service to invisible components"]
VC --> C1["Place components by evolution stage (horizontal)"]
C1 --> G["I. Genesis"]
C1 --> CB["II. Custom-Built"]
C1 --> P["III. Product/Rental"]
C1 --> CM["IV. Commodity/Utility"]
G --> M["Movement: left to right commoditization"]
CB --> M
P --> M
CM --> M
M --> S["Derive strategy via climatic patterns, doctrine, gameplay"]
In this structure, the anchor is the map's reference point: the user and their needs. Since every component ultimately exists to satisfy user needs, the map must start from "whose needs, and which ones." If the anchor wavers, the whole map loses direction. Starting from the need "a cup of tea," for example, "cup → hot water → kettle → electricity" hangs off it in a chain, and each element's evolution position differs.
The vertical axis (value chain) represents the degree of visibility to the user. At the top are services the user directly experiences; at the bottom are the infrastructure and parts that support them but remain unseen. The dependency lines connecting them reveal "what stands on what," letting you trace how changes in lower components propagate upward.
The horizontal axis (evolution) divides each component's maturity and diffusion into four stages. The leftmost Genesis is newly emerged, uncertain, and scarce; Custom-Built is where usefulness is confirmed and things are made individually; Product/Rental is where it has become a repeatedly purchasable commodity good; and the rightmost Commodity/Utility is the standardized state consumed as a matter of course, like electricity or water. The key point is that almost every component feels a gravity pulling it from left to right, and strategy is the act of reading that movement and riding it, accelerating it, or delaying it.
3. Core Components and Evolution Stages
A. User Needs and the Anchor
A map starts not from an abstract "market" but from concrete users and their needs. If the need is mis-set, the entire value chain hangs in the wrong direction, so at this stage you persistently ask "what problem do we really solve?" For a power company, for instance, the user need may be not "electricity supply" but "lighting, heating/cooling, and device use without inconvenience," and redefining the need this way changes the components that hang below and their priorities. Needs may be several rather than one, and each need branches into its own value chain.
In practice, if you cannot nail the anchor, the map may look plausible yet help no actual decision, because a vague user need destabilizes the criteria for judging horizontal-axis evolution as well.
The importance of setting the anchor becomes clear in that the same business yields an entirely different map depending on whom you take as the reference user. For an online education platform, anchoring on the "learner" puts content, learning experience, and recommendations at the top, whereas anchoring on the "instructor" puts authoring tools, revenue settlement, and student management at the top. The two maps are complementary, and they surface the organization's implicit assumptions about which need investment should concentrate on. Choosing the anchor is therefore itself a strategic decision.
B. The Value Chain and Dependencies
The value chain is a structure that stacks components vertically by depth of dependency, with the user need at the apex and the components needed to satisfy it below. Upper elements depend on lower ones, and change propagates along these lines. In practice you judge visibility by asking "would the user feel inconvenience if this element disappeared?" and find lower dependencies by asking "what does this not work without?" and descending accordingly. Simply surfacing hidden critical dependencies or duplicated investment in the drawing process is itself a major gain.
When arranging the value chain vertically, note that visibility (vertical axis) and evolution (horizontal axis) are two independent axes. A top service that is highly visible to the user may be evolutionarily a commodity (e.g., the search box a user uses daily is visible, yet the search infrastructure is heavily commoditized), while an invisible lower component may still be at Genesis. If you confuse the two axes and place something "to the right (or left) because it is important," the map becomes distorted. You must keep the vertical axis—user visibility—and the horizontal axis—degree of maturity and diffusion—separated to the end, as answers to different questions.
C. The Four Evolution Stages and Their Traits
Evolution is the process by which a component spreads and standardizes ever more through repeated competition of supply and demand. Each stage demands a different management style and financial profile. The table below compares the core differences across the four stages, while the "why" is narrated in the paragraphs that follow.
| Stage | Traits | Uncertainty | Suitable methods | Example |
|---|---|---|---|---|
| I. Genesis | Novel, scarce, high failure rate | Very high | Exploration, experiment (agile) | Early quantum computing |
| II. Custom-Built | Usefulness confirmed, built individually | High | Iterative development | Bespoke in-house systems |
| III. Product/Rental | Repeatedly purchasable commodity good | Medium | Lean, incremental improvement | Commercial packaged SW |
| IV. Commodity/Utility | Standardized, mass-consumed | Low | Six Sigma, operational efficiency | Cloud computing, electricity |
The most important insight in this table is that the suitable methodology is the opposite at each stage. The left-hand Genesis stage is the source of differentiation but close to gambling. Since you cannot know what will succeed, many attempts fail, so rapid learning and experimentation take priority over cost control; applying efficiency and standardization methods here tramples the sprout of innovation. Conversely, the right-hand commodity stage has almost no room for differentiation, where stability and unit cost are everything, so efficiency-oriented management such as Six Sigma and operational automation fits. Building anew each time here while urging "let's be creative" produces enormous waste. The middle custom-built and product stages are a span where you gradually raise efficiency between these two extremes.
The representative case showing the strategic implication of this evolution axis is cloud computing. Until the mid-2000s, a "server" was at the product stage, something a company specified and bought and ran itself; but when Amazon pushed this into a pay-as-you-go utility with EC2, the capabilities of countless firms running their own servers were reduced overnight to the inefficiency of "expensively self-producing a commodity part." A Wardley map helps you read in advance "is what is now at the product stage about to cross into a utility?" and pre-emptively decide to adopt an external utility instead of building it yourself. The typical procedure for drawing a map is as follows.
flowchart TD
S1["1. Define users and needs (set the anchor)"] --> S2["2. Build the value chain: need to components, vertically"]
S2 --> S3["3. Assess each component's evolution stage (left-right placement)"]
S3 --> S4["4. Connect dependency lines, complete the map"]
S4 --> S5["5. Apply climatic patterns: where is it moving?"]
S5 --> S6["6. Check doctrine: are universal principles observed?"]
S6 --> S7["7. Choose gameplay: how will we intervene?"]
S7 --> S8{"Test hypotheses, execute"}
S8 -->|"Mismatch with observation"| S3
S8 -->|"Sound"| S9["Execute strategy, re-map periodically"]
D. Climatic Patterns, Doctrine, and Gameplay
A completed map is not a conclusion in itself but a starting point for reasoning about strategy. After drawing the map, you derive strategy at three levels. Climatic patterns are environmental rules a player cannot change, such as "everything evolves" and "past success breeds future inertia." Just as you cannot change the weather but can forecast it, climatic patterns let you predict where components on the map will flow. Doctrine consists of universal principles to be observed almost always regardless of context, such as "focus on user needs," "use a common language," and "use appropriate methods (differently per stage)." Gameplay is the active move chosen in a specific context—tactics such as accelerating commoditization to neutralize a competitor's differentiation (opening up), seizing a standard first, or cultivating an ecosystem. The reason for distinguishing these three levels is to concentrate capability on moves that fit the situation (gameplay) without wasting force resisting the unchangeable (climate) and without skipping what must always be observed (doctrine).
A concrete example of gameplay is the open approach tactic. When a competitor monopolizes and monetizes some component, releasing it as open source or an open standard causes that component to slide rapidly toward a utility and collapses the competitor's revenue base. Google's opening of Android—pulling the value of the mobile OS down to a commodity and shifting the competitive arena to higher-level services—is the archetype. Such moves are hard to choose without a map: only when the map first points out "which component at the product stage is giving the competitor bargaining power" can you design the aggressive move of deliberately commoditizing it.
4. Comparison with Other Strategy Tools
The character of Wardley Mapping becomes clear when contrasted with existing strategy tools. The core difference lies in "does it list and classify elements, or does it show position and movement?"
| Tool | Core output | Position/movement | Limitation |
|---|---|---|---|
| SWOT | List of strengths/weaknesses/opportunities/threats | None | Static listing, lacks context and connections |
| BSC | Four-perspective KPI system | None | Measurement-centric, weak terrain awareness |
| BM Canvas | Nine-block business model | None (static) | Does not reflect evolution or competitive dynamics |
| Porter's 5 Forces | Industry structural pressures | Partial | Hard to grasp temporal movement |
| Wardley Mapping | Value-chain × evolution map | Yes (central) | Requires drawing skill, some subjectivity |
As this comparison shows, the common weakness of traditional tools is that they do not ask "what is moving where now." This does not mean SWOT or the Business Model Canvas is useless. It is only that these merely write snapshots of the current state into different boxes and cannot express the dynamic chain such as "if component A crosses into a utility, how does business B shake?" Precisely because Wardley Mapping takes that movement and propagation as its axes, it complements rather than replaces other tools. In practice, many practitioners grasp the terrain with a Wardley map, then carry detailed business design on into the Canvas and performance management into the BSC.
To put the implication in numbers, suppose a financial firm maintained its fraud-detection engine entirely by in-house development (custom-built, 5 billion KRW invested per year), then confirmed from the map that the function had already moved to the product/API stage of many vendors, and—keeping only the core rule engine in-house while converting the rest to a utility—cut operating costs substantially. What matters is not the savings themselves but the point that had the map not first shown "what has already been commoditized," the very decision would have been delayed.
Another contrasting case is how the map's time axis is read. If Porter's 5 Forces answers the static question "who holds power in the current industry structure," Wardley Mapping adds to it the dynamic question "in which direction is the component that is the source of that power now moving." For instance, even if a supplier holds bargaining power through a monopolistic product, if that product is sliding toward a commodity via open source and standardization, the bargaining power will soon vanish. Using the two tools together, you read "the current structure" and "the structure's movement" simultaneously and can separate short-term negotiation from medium-to-long-term investment judgment.
5. Advanced — Organizational Structure, Practical Application, and Recent Trends
The most practical extension of Wardley Mapping is the Pioneer–Settler–Town Planner (PST) model, which matches organizational structure to evolution stages. The Genesis area is handled by Pioneers good at fast experimentation, the custom-to-product transition span by Settlers who refine ideas into products, and the commodity/operation span by Town Planners strong at scale and efficiency—so that different cultures, talents, and methods are placed per stage within one organization. This structurally prevents the common failure of "trying to handle all components with one way (e.g., enterprise-wide agile or enterprise-wide Six Sigma) and losing both innovation and efficiency."
The PST model is persuasive for a further reason: the nature of failure differs at each evolution stage. At the Genesis stage, "not trying" is the greatest failure, so a Pioneer culture that encourages fast discarding and retrying fits; at the operation stage, "exceptions and variability" are the greatest failure, so a Town Planner culture valuing standards, automation, and repeatability fits. The Settler, in between, stabilizes the unstable prototype the Pioneer created into a repeatable product and bridges it into a form the operations team can take over. Forcing these three groups under one evaluation metric (e.g., a company-wide common KPI) cows the Pioneer under short-term performance pressure and forces needless experiments on the Town Planner, so both lose their roles. Organizational application of Wardley Mapping must therefore go as far as designing evaluation, reward, and hiring systems separately per stage.
A recent trend is the growing application of Wardley Mapping to the ultra-fast commoditization of the generative-AI and cloud-native space. As LLM fine-tuning, embeddings, and vector search—custom-built only a year or two ago—move rapidly to managed APIs (product/utility), firms face having to judge by map "how far to keep their own models in-house and from where to depend on external APIs." Wardley Mapping is also used as a common framework in discussions of cloud migration, platform engineering, and supply-chain sovereignty (digital sovereignty) to explain "which capabilities to internalize (build in-house) and which to leave as a common utility." At the community level, open-source tools and online editors for drawing maps have spread, shifting what once relied on paper and whiteboards into collaborative digital artifacts. That said, judging horizontal-axis position still involves subjectivity and interpretation, so recent discussion recommends also using an evolution-trait checklist that places components semi-quantitatively by stage traits (ubiquity, certainty).
6. Considerations and Implications
Wardley Mapping is an attractive tool but not a panacea; on adoption you must consider the following pitfalls and premises together. From a professional engineer's perspective, its adoption and use must weigh the following comprehensively.
First, the goal must be situational-awareness capability, not the tool itself. The value of Wardley Mapping lies not in a pretty map artifact but in the organization internalizing the thinking habit of "asking first about the current position and direction of movement." Drawing a map once and hanging it on the wall is useless; it must be run as a living document re-drawn periodically whenever the strategic environment changes.
Second, you must manage the subjectivity of evolution-position judgment. Horizontal-axis placement depends on the author's interpretation, so a map drawn alone easily harbors bias. It is advisable to always go through a collaborative process in which stakeholders gather to argue over and exchange grounds for each component's position, and to share evolution-trait criteria such as ubiquity and certainty to correct the judgment.
Third, you must design linkage with other strategy and management systems. Wardley Mapping only shows the terrain; it provides no detailed execution plan, financial model, or performance metrics. You must therefore also equip the connective links that make the strategic direction derived from the map concrete through follow-on tools such as the Business Model Canvas, roadmaps, the BSC, and EA (enterprise architecture) for it to lead to execution.
Fourth, you must strategically weigh the speed of commoditization and the trade-offs. "Differentiate by building in-house, or adopt a utility to gain efficiency?" has a different answer at each stage. Hastily outsourcing/commoditizing a core capability still at Genesis/custom stages loses differentiation, while stubbornly keeping an already-commoditized element in-house loses both cost and opportunity. Commoditization also brings new risks such as supplier lock-in, security, and sovereignty, so decide not by efficiency alone but with risk and governance perspectives in parallel.
Fifth, alignment of organizational capability and culture must be a premise. As the PST model implies, if you cannot place different talents, methods, and evaluation systems per stage, the map remains a mere picture. Escaping the practice of forcing a single development methodology across the company, organizational design and change management that permit per-stage heterogeneity must proceed together for strategic situational awareness to convert into real performance.
References
- Simon Wardley, "Wardley Maps" (online book/Medium series): https://medium.com/wardleymaps
- Wardley Maps official community wiki: https://learnwardleymapping.com/
- Learn Wardley Mapping (introductory guide): https://learnwardleymapping.com/book/
In one line: Wardley Mapping is a strategy tool that renders the position and movement of a business landscape on a single page by combining the value chain (vertical axis) and evolution stage (horizontal axis) anchored on user needs, helping the strategic choice between building in-house and adopting commodities on a basis of situational awareness.