Wardley Mapping

Table of Contents

  1. Definition
  2. How It Relates to Marketing
  3. How to Build a Wardley Map
    1. The Four Stages of Evolution
    2. Key Strategic Elements
  4. How to Utilize Wardley Mapping
  5. Comparison to Similar Frameworks
  6. Best Practices
  7. Future Trends
  8. FAQs
  9. Related Terms
  10. Sources

Definition

Wardley Mapping is a strategic planning framework that visualizes the components of a value chain against their stage of evolution to create situational awareness — a shared, defensible picture of the competitive landscape on which strategic decisions can be made. Unlike most strategy frameworks, which produce text-based outputs (such as SWOT statements or generic strategy choices), a Wardley Map is an actual map: components are placed in two dimensions, dependencies are drawn explicitly, and movement of components over time is anticipated.

The framework was developed by Simon Wardley, then CEO of the UK-based software-as-a-service company Fotango, who created the technique in 2005 after building an evolutionary framework the previous year. Wardley further developed the methodology while at Canonical UK between 2008 and 2010. The framework draws explicitly on Sun Tzu’s The Art of War — particularly the five factors of Purpose, Landscape, Climate, Doctrine, and Leadership — and on John Boyd’s OODA loop. Wardley Mapping is licensed under Creative Commons Attribution-ShareAlike 4.0 and is freely available, including through Wardley’s open-source book Wardley Maps: Topographical Intelligence in Business.

A Wardley Map plots components along two axes:

  • Vertical axis (Visibility / Value Chain): how visible a component is to the end user — anchored by the user need at the top and descending through the underlying capabilities and dependencies required to meet that need.
  • Horizontal axis (Evolution): how mature a component is, moving left to right through four stages — Genesis, Custom-Built, Product (and Rental), and Commodity (and Utility). This axis is measured by certainty rather than time, reflecting how well understood and standardized a component has become through supply-and-demand competition.

The map’s purpose is not to dictate strategy but to support better strategic conversations. Wardley Maps will not tell you what to do; they improve a leadership team’s ability to communicate, anticipate change, and act with shared understanding.

Back to Top

How It Relates to Marketing

Wardley Mapping is directly relevant to marketing strategy because marketing decisions are typically made about specific components of a value chain — and those components evolve, change in cost, and create or destroy customer value over time. Common marketing applications include:

  • Category positioning — distinguishing components in the Genesis or Custom stage (where novelty and innovation messaging is appropriate) from those approaching Commodity (where convenience, price, and ubiquity messaging is appropriate).
  • Value proposition design — anchoring the value proposition in genuine user needs at the top of the map rather than in features the team finds interesting.
  • Competitive intelligence — mapping competitors’ value chains and identifying where their components are at different stages of evolution.
  • Brand and product portfolio strategy — managing brands and products whose underlying components are evolving at different speeds.
  • Martech investment decisions — using maps to evaluate which marketing technology components are commodity (rent or buy) versus differentiating (build or carefully customize).
  • Channel and ecosystem strategy — visualizing partner and channel relationships as part of the broader value chain.
  • Go-to-market planning — identifying which gameplay patterns (e.g., open-sourcing a component to accelerate commoditization) will most help the company’s position.
Back to Top

How to Build a Wardley Map

Wardley Mapping is a qualitative framework. A typical mapping process follows these steps:

  1. Identify the user. Define explicitly who the user is — customer, consumer, business buyer, regulator, or other stakeholder.
  2. Identify the user’s needs. State the specific needs the user is trying to meet. These anchor the top of the map.
  3. Build the value chain. List the activities and components required to meet those needs. Connect each component to the ones it depends on. The visibility axis reflects how visible each component is to the user.
  4. Place components on the evolution axis. For each component, judge its evolution stage based on the four stages.
  5. Identify movement and inertia. Indicate which components are likely to evolve (moving right) and where organizational, competitive, or technical inertia may slow that evolution.
  6. Identify climatic patterns. Apply Wardley’s catalog of climatic patterns — external forces such as “everything evolves,” “no choice over evolution,” and “competitive pressures” — to anticipate change.
  7. Apply doctrine. Test the organization against Wardley’s universal principles (a catalog of about 40 principles such as “know your users,” “focus on user needs,” “challenge assumptions,” and “use appropriate methods”).
  8. Identify strategic plays (gameplay). Select from a catalog of repeatable competitive plays such as open-sourcing, building ecosystems, accelerating evolution, or creating fear/uncertainty/doubt (FUD).
  9. Iterate using the Strategy Cycle. Combine the map with the broader strategy cycle (Purpose → Landscape → Climate → Doctrine → Leadership), continually updating as the environment changes.
Back to Top

The Four Stages of Evolution

StageDescriptionCommon CharacteristicsAppropriate Approach
GenesisFirst-of-its-kind, novel, uncertain, high R&DExperimental, custom, expensive, no formal marketExplore; expect failure; protect intellectual capital
Custom-BuiltBespoke, hand-crafted solutions; differentiation through expertiseConsultants and specialists, limited standardization, high costBuild for specific contexts; capture learning
Product (incl. rental)Productized, packaged, sold to manyDefined features, competitive vendors, predictable pricingBuy or partner; optimize for fit
Commodity / UtilityWidely available, standardized, low cost, often pay-per-useUtility pricing, near-zero differentiation, ubiquitous availabilityRent or consume; do not build internally
Back to Top

Key Strategic Elements

ElementPurpose
AnchorA reference (user, business, or other entity) that bounds the map
PositionWhere each component sits in the value chain and on the evolution axis
MovementDirection and speed of components’ evolution over time
Climatic PatternsExternal forces predictably acting on the landscape
DoctrineUniversal principles applicable to any organization
GameplayRepeatable competitive plays available to influence the landscape
Back to Top

How to Utilize Wardley Mapping

Common use cases include:

  • Build-vs.-buy-vs.-rent decisions — Wardley argues that the appropriate approach is determined by evolution stage: build at Genesis, contract custom in Custom-Built, buy products in Product, and rent or consume utilities in Commodity.
  • Technology and platform strategy — used extensively by software, cloud, and platform organizations to inform infrastructure and architectural decisions.
  • Outsourcing and partnering decisions — identifying which components are at a stage where outsourcing makes economic sense.
  • Identifying inertia — surfacing where the organization is clinging to outdated approaches that no longer fit the evolution stage of a component.
  • Anticipating competitive moves — predicting how competitors and the broader ecosystem are likely to evolve.
  • Product strategy — finding white space, weak components, or opportunities to commoditize parts of a competitor’s value chain.
  • Public-sector strategy — Wardley Maps have been adopted by the UK Government Digital Service (GDS) for strategic planning and digital service modernization, and have been used in initiatives including High Speed 2 (HS2) infrastructure planning.
  • Organizational design — informing how to structure teams around components at different stages (e.g., pioneer-settler-town planner team archetypes Wardley proposes for Genesis, Custom-Built/Product, and Commodity stages respectively).
Back to Top

Comparison to Similar Frameworks

FrameworkFocusOutputPrimary Use
Wardley MappingValue chain + evolution; situational awarenessVisual mapStrategy through anticipation of change
SWOT AnalysisInternal strengths/weaknesses + external opportunities/threatsText matrixSituational diagnosis
Porter’s Five ForcesIndustry competitive structureText rating per forceIndustry attractiveness
Business Model CanvasBuilding blocks of a business modelSingle-page canvasBusiness model design and articulation
Value Chain Analysis (Porter)Internal activities and their value contributionActivity-by-activity analysisCost and differentiation analysis
Cynefin FrameworkSense-making in different decision contextsFive domainsChoosing appropriate decision approaches
Three Horizons ModelTime horizons for innovationThree-horizon portfolioInnovation portfolio balance
BCG MatrixMarket growth × Relative market share2×2 portfolio gridPortfolio resource allocation

Wardley advocates do not treat the framework as a replacement for other tools. Many practitioners use Wardley Maps to establish situational awareness first, then apply tools such as SWOT, Five Forces, or Business Model Canvas to specific components.

Back to Top

Best Practices

  • Start with the user, not the technology. Maps that begin with technology components rather than user needs typically produce inward-looking analysis.
  • Treat maps as conversations, not artifacts. Maps are most valuable as the basis for shared discussion among a leadership team. Their accuracy is less important than the shared understanding they produce.
  • Iterate. First maps are typically wrong in important ways. Iteration with diverse stakeholders improves both accuracy and adoption.
  • Match approach to evolution stage. A common failure mode is applying product-stage approaches (e.g., agile sprints) to Genesis-stage work, or applying Genesis-stage exploration to commodity work. Methods must match stage.
  • Identify inertia explicitly. Where components resist their natural evolution (because of contracts, organizational culture, legacy systems, or installed base), mark this on the map; inertia is where strategic risk concentrates.
  • Use doctrine as a checklist. The 40-odd doctrine principles serve as a structured organizational maturity check.
  • Don’t combine Wardley Maps with Cynefin into a single view. Simon Wardley has explicitly cautioned against merging the two — they provide complementary but distinct perspectives, and their value lies in the tension between them.
  • Recognize that maps are models, not truths. As one practitioner summarized, Wardley Maps will not tell you what to do; they will only improve your leadership team’s ability to communicate and achieve shared understanding through a clearer visualization of the business context.
Back to Top
  • AI as the dominant evolutionary force. Generative AI and adjacent technologies are accelerating the evolution of many components from Custom-Built or Product toward Commodity. Wardley Mapping is widely used to evaluate which marketing, software, and content components are likely to commoditize next.
  • Application to public-sector and infrastructure strategy. Wardley Maps continue to expand in use within UK government and have spread to other public-sector contexts and large infrastructure programs.
  • Mapping ecosystems and platforms. As more value is created in multi-party platforms, Wardley Mapping is increasingly applied at the ecosystem level rather than the single-organization level.
  • Tooling and collaborative mapping. Online mapping tools (Miro, OnlineWardleyMaps, MapKeep, and others) have lowered the barrier to collaborative map creation and are bringing the framework to broader audiences.
  • Integration with OKRs and operating cadences. Some organizations use Wardley Maps as the strategic foundation that informs OKRs and operating reviews, providing situational context for goal-setting.
  • Continuous mapping practice. Mature adopters increasingly treat mapping as a routine practice rather than an annual offsite, refreshing maps continuously as components evolve.
Back to Top

FAQs

1. Who created Wardley Mapping? Simon Wardley created the technique in 2005 while CEO of the UK-based SaaS company Fotango, building on an evolutionary framework he developed the previous year. The methodology was further developed at Canonical UK between 2008 and 2010.

2. What are the two axes of a Wardley Map? The vertical axis represents visibility within the value chain (anchored by the user need at the top). The horizontal axis represents evolution through four stages — Genesis, Custom-Built, Product (and Rental), and Commodity (and Utility).

3. What are the four stages of evolution? Genesis (novel, uncertain, R&D-stage), Custom-Built (bespoke, expert-driven), Product (productized, sold to many), and Commodity / Utility (standardized, widely available, often pay-per-use). The appropriate methodology, sourcing decision, and team type differ at each stage.

4. What is “situational awareness” in Wardley Mapping? Situational awareness is a shared, defensible understanding of the competitive landscape — who the users are, what they need, what components deliver those needs, and how those components are evolving. It is the foremost goal of mapping.

5. What is “doctrine” in Wardley Mapping? Doctrine refers to roughly 40 universal principles for strategic success — including “know your users,” “focus on user needs,” “challenge assumptions,” and “use appropriate methods.” Doctrine is treated as broadly applicable regardless of context and provides a checklist for assessing organizational maturity.

6. What is “gameplay” in Wardley Mapping? Gameplay refers to a catalog of repeatable competitive plays — actions such as accelerating a component’s evolution, open-sourcing, building an ecosystem, exploiting constraints, or applying fear/uncertainty/doubt — that organizations can deploy once situational awareness has been established.

7. How is Wardley Mapping different from SWOT or Porter’s Five Forces? SWOT and Porter’s Five Forces produce text-based assessments. Wardley Maps produce a visual model of components, dependencies, and evolution. Wardley Mapping is generally used earlier — to build situational awareness — with other frameworks applied to specific components once the landscape is mapped.

8. Is Wardley Mapping free to use? Yes. The framework is published under a Creative Commons Attribution-ShareAlike 4.0 license. Simon Wardley’s book Wardley Maps: Topographical Intelligence in Business is freely available online.

9. What are common criticisms of Wardley Mapping? Common observations include that the framework has a learning curve, that evolution-stage judgments are subjective, that maps are most useful for broad strategy rather than fine-grained decisions, and that the framework’s terminology can feel inaccessible to leaders accustomed to traditional strategy tools. Practitioners typically address these by combining mapping with other frameworks.

10. Who uses Wardley Maps? Adopters include technology companies, the UK Government Digital Service, large infrastructure programs such as HS2, security organizations evaluating build-versus-outsource decisions, venture capital firms, and an active practitioner community organized through the Map Camp conference, the Wardley Maps Discourse, and related communities.

Back to Top
  1. Situational Awareness
  2. Value Chain Analysis
  3. Strategy Cycle
  4. Cynefin Framework
  5. OODA Loop
  6. Doctrine (Wardley)
  7. Climatic Patterns (Wardley)
  8. Pioneer-Settler-Town Planner Model
  9. Build-Measure-Learn
  10. Three Horizons Model
  11. Porter’s Five Forces
  12. SWOT Analysis
  13. Porter’s Generic Strategies
  14. PESTLE Analysis
  15. BCG Matrix (Growth-Share Matrix)
Back to Top

Sources

Back to Top

Was this helpful?

Previous

VRIO Framework