Wardley Mapping

You can't make good strategic bets on a landscape you can't see. A Wardley Map makes the terrain visible: what your users need, what components serve those needs, and which ones you're over-investing in because you haven't noticed they became commodities.

Overview

Wardley Mapping is a technique for visualizing your strategic landscape. You start with a user need at the top, map the chain of components required to serve that need, and then plot each component along an evolution axis from genesis (novel, uncertain) through custom-built, product, and finally commodity (well-understood, standardized). The result is a map that reveals where you’re over-investing in commodity components, where you have genuine differentiation, and where the landscape is about to shift underneath you. A platform team building its own logging pipeline when mature SaaS options exist is a classic case of misreading component evolution.

We reach for Wardley maps when teams are making strategic bets without a shared picture of the terrain. It pairs naturally with Iterative Strategy Development because the map gives you a snapshot of the current landscape and the evolutionary dynamics tell you where to place your next hypothesis. It also sharpens conversations about value streams; instead of treating every component equally, the map forces you to ask which parts of the chain deserve investment and which should be outsourced or standardized. The core insight is that different evolutionary stages demand different management approaches, and most strategic confusion comes from applying the wrong approach to the wrong stage.

Watch it build

The map on this page steps through three authored maps one slide at a time, narrating the strategic reasoning behind each placement and each move. Start here before you draw your own.

• Tea Shop — the canonical intro. Wardley’s own example: a cup of tea decomposed into shop, cup, kettle, and power, ending in a choice between franchising for scale or sourcing artisan pottery to differentiate. Watch how one map supports two strategies that cancel each other out.
• Platform Team Evolution — misreading evolution. A platform team builds logging, alerting, and authentication in-house, then the market turns each into a commodity (Datadog, PagerDuty, Auth0) while the team keeps paying to maintain its custom versions. This is the logging-pipeline case from the Overview above, made playable — the same trap, one click away.
• UX Practice Maturation — capability building. A solo designer producing ad-hoc mockups grows into a product-trio member backed by a design system. Watch a role climb in visibility and shift right in evolution as the practice matures.

Your first map

Stepping through a finished map won’t teach you to draw one, and drawing is where the learning is. Start a map in the builder, or grab a whiteboard:

1. Pick one user need. The user’s need, not your team’s. “A customer can check out and pay,” not “we run a payments service.” Put it at the top.
2. List the value chain beneath it. What does that need depend on? Checkout depends on a payment gateway, which depends on fraud scoring, which depends on compute. Keep asking “and what does that need?” until you bottom out at raw utilities.
3. Place each component on the evolution axis. Left to right: genesis (novel, you’re inventing it) → custom-built (you wrote it) → product (you buy or rent it) → commodity (it’s a utility, like power from the wall). When a placement is contested, hover a stage name on the map’s evolution axis for that stage’s tells: ubiquity, certainty, how the market treats it.
4. Argue about the placements. This is the value. When two people disagree over whether authentication is “product” or “commodity,” you’re having the exact strategic conversation the map exists to force. The map is a prop for the argument, not an artifact to file.

Now do it for real: sketch your own team’s top three components — the three you sink the most engineering effort into — on the evolution axis. If any of them are sitting in commodity territory, you’ve just found where you’re paying custom-build prices to feel special.

Resources

• Simon Wardley, Wardley Maps (CC BY-SA 4.0, Leading Edge Forum) — the definitive guide to the technique
• Learn Wardley Mapping — community resource with tutorials and examples
• Visual is Valuable — the principle behind why mapping works
• Iterative Strategy Development — maps inform strategy; iterative cycles refine the map
• Value Stream — the chain of activities that Wardley maps visualize