> ## Documentation Index
> Fetch the complete documentation index at: https://meta.niceshare.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Wardley Mapping

> Wardley Mapping visualizes user needs, value chains, and evolution stages to guide strategy. Learn how to decide where to build, buy, or differentiate.

<Info>
  **Category**: Models<br />
  **Type**: Strategy and Situational Awareness Model<br />
  **Origin**: Simon Wardley, mid-2000s<br />
  **Also known as**: Wardley Map, Value Chain Evolution Map
</Info>

<Note>
  **Quick Answer** — Wardley Mapping is a strategic method that maps user needs, supporting value-chain components, and each component's evolution stage from genesis to commodity. Developed by Simon Wardley, it helps teams decide what to build, what to buy, and where to differentiate. Its key insight is that strategy improves when context becomes visible and assumptions become explicit.
</Note>

## What is Wardley Mapping?

Wardley Mapping is a visual strategy model for making context-aware decisions in uncertain and competitive environments.

> "The map is not the territory, but without a map you are likely to get lost." — Simon Wardley (strategy practice principle)

A Wardley map has two axes: value chain visibility (from user need to underlying components) and evolution (from novel/genesis to product and then commodity/utility). By locating components on this landscape, teams can see where custom building creates advantage and where adopting utilities is faster and cheaper. The model is often used with `/models/map-is-not-territory`, `/models/cynefin-framework`, and `/models/ooda-loop`.

### Wardley Mapping in 3 Depths

* **Beginner**: Draw the user need at the top, then list what must exist beneath it to deliver value.
* **Practitioner**: Place each component on an evolution stage and identify which ones should be industrialized versus differentiated.
* **Advanced**: Use gameplay patterns, inertia analysis, and doctrine to forecast competitive moves and redesign organizational structure.

## Origin

Wardley Mapping was created by Simon Wardley during his work on cloud strategy in the mid-2000s, then shared publicly through talks, open writing, and community practice. The method emerged from a simple operational problem: teams made major strategic bets without shared situational awareness.

Wardley combined value-chain thinking, evolutionary economics, and practical doctrine into one visual language. Over time, the method was adopted in technology strategy, public-sector transformation, and platform planning. Its influence grew further as cloud infrastructure moved from a novelty to utility, reinforcing the core build-versus-buy logic.

## Key Points

Wardley Mapping works when teams use it continuously, not as a one-off diagram.

<Steps>
  <Step title="Start from user need, not internal structure">
    Mapping begins with what users need to accomplish. This prevents teams from optimizing internal org charts instead of customer outcomes.
  </Step>

  <Step title="Visibility before optimization">
    Many strategic errors come from hidden dependencies. A map exposes upstream and downstream links so trade-offs become explicit.
  </Step>

  <Step title="Evolution stage changes your decision type">
    Components in genesis or custom stages may justify experimentation and unique bets. Commodity-stage components usually favor standardization and external services.
  </Step>

  <Step title="Doctrine and gameplay guide execution">
    Mapping is not only analysis. Doctrine principles and gameplay moves translate the map into concrete sequencing, investment, and competitive actions.
  </Step>
</Steps>

## Applications

Use Wardley Mapping to align architecture, product strategy, and organizational focus.

<CardGroup cols={2}>
  <Card title="Build vs Buy Decisions">
    Map each component before budgeting. If infrastructure is already utility-grade, buying may free resources for differentiation layers.
  </Card>

  <Card title="Cloud and Platform Strategy">
    Identify where commoditization reduces cost and where custom capability still creates moat. This clarifies migration timing and platform boundaries.
  </Card>

  <Card title="Portfolio Prioritization">
    Use map position to rank initiatives: stabilize utilities, modernize product-stage capabilities, and selectively fund experimental components.
  </Card>

  <Card title="Executive Communication">
    A shared map improves cross-functional dialogue by replacing abstract strategy debates with visible assumptions and dependencies.
  </Card>
</CardGroup>

## Case Study

A commonly cited Wardley analysis of Netflix's transition from DVD rental to streaming highlights how component evolution shaped strategic timing. The case describes Netflix reducing store-related cost structure by shifting from physical channels toward digital delivery, while investing early in custom streaming capabilities and recommendation systems.

Two measurable indicators capture the strategic outcome: first, reported cost-structure reductions of roughly 60-70% associated with eliminating physical-store dependencies in early phases; second, scale expansion to 260.8 million paid subscribers by the end of 2023. While many factors drove Netflix's performance, the map-based view explains why sequencing around component evolution mattered.

## Boundaries and Failure Modes

Wardley maps can create false confidence when teams treat placement as objective truth rather than informed judgment. Another risk is skipping user-need clarity and mapping internal systems in isolation. A frequent misuse is producing beautiful maps without doctrine-driven action plans, leaving decisions unchanged despite better visuals.

## Common Misconceptions

Wardley Mapping is often misunderstood as a drawing exercise rather than a decision method.

<AccordionGroup>
  <Accordion title="It is only for large enterprises">
    Small teams benefit equally because mapping clarifies where to avoid custom complexity early.
  </Accordion>

  <Accordion title="A map gives exact predictions">
    Maps improve situational awareness; they do not eliminate uncertainty. Strategy still requires iterative learning.
  </Accordion>

  <Accordion title="Once mapped, strategy is done">
    Environment and competitors move. Maps must be revised as components evolve and user needs shift.
  </Accordion>
</AccordionGroup>

## Related Concepts

Wardley Mapping becomes more actionable when paired with complementary decision and systems models.

<CardGroup cols={3}>
  <Card title="Cynefin Framework" href="/models/cynefin-framework">
    Match action style to complexity level in each map area.
  </Card>

  <Card title="OODA Loop" href="/models/ooda-loop">
    Convert map insights into rapid observe-orient-decide-act cycles.
  </Card>

  <Card title="Map Is Not Territory" href="/models/map-is-not-territory">
    Maintain epistemic humility while using abstract representations.
  </Card>

  <Card title="SWOT Analysis" href="/models/swot-analysis">
    Connect map positioning with competitive strengths and threats.
  </Card>
</CardGroup>

## One-Line Takeaway

<Tip>
  Strategy improves when you can see user needs, dependencies, and evolution on one map before committing resources.
</Tip>