Index

Strategic Frameworks

Wardley Mapping

A visual method that maps the components needed to serve a user need along axes of visibility and evolution, from genesis to commodity.

Wardley mapping reveals strategic positioning by plotting value chain components against their evolutionary stage.

Core question

Where does each component sit on the evolution curve, and what moves does that position make possible?

Example

A platform team maps their stack and discovers the auth layer is custom-built but commodity-grade. They replace it with a managed service, freeing engineering to focus on differentiating features higher in the value chain.

How to apply

  1. 1.Identify the user need and list every component required to serve it.
  2. 2.Position each component on the evolution axis: genesis, custom, product, or commodity.
  3. 3.Draw dependency lines to expose hidden coupling and leverage points.
  4. 4.Decide where to build, buy, or partner based on evolutionary position.

Pitfalls

  • ·Treating the map as a static artifact instead of a living conversation tool.
  • ·Mislabeling component maturity due to internal familiarity bias.
  • ·Over-investing in mapping precision when a rough sketch would drive the same decision.

Questions

How is Wardley mapping different from a typical strategy matrix?

Most matrices lack a spatial dimension for evolution. Wardley maps show movement over time, revealing when to shift from build to buy.

Do you need a complete map to get value?

No. Even a rough map of ten key components often surfaces one or two positioning insights that change resource allocation.

Related