A Wardley Map plots your value chain — the user's need at the top, everything it quietly depends on beneath — against evolution: how commoditised each piece is, from genesis on the left to utility on the right. Position is the strategy. Build and differentiate on the left where things are novel; buy and outsource on the right where they're commodity. And because every component drifts rightward over time, the map shows not just where you are but where you're heading — including the classic, expensive error of custom-building something the rest of the world now buys off the shelf.
Here's the value chain for an online shop: the customer at the top, and beneath them the things they depend on — the storefront, your recommendation engine, the platform, compute, and power. Position each component along the evolution axis and the map tells you what to build and what to buy — and flags anything that's in the wrong place.
Drag any node left or right to set how commoditised it is. On a keyboard, use the ◀ / ▶ buttons on each component below the map. One component starts deliberately miscast — see if the map catches it.
Most "strategy" artefacts are static. A SWOT is four boxes of adjectives; a 2×2 sorts things but says nothing about where they sit in a value chain or which way they're going. A Wardley Map adds the two things that actually drive a build-vs-buy call: where a component sits on the chain, and how far it has evolved.
| Lens | What it shows | What it misses | Reach for it when |
|---|---|---|---|
| SWOT / a 2×2 matrix | A snapshot: strengths, weaknesses, sorted quadrants. Good for framing a first conversation. | No value chain, no dependencies, no sense of time. Nothing tells you what's about to change. | You need a quick shared vocabulary — not a decision you'll bet the roadmap on. |
| A plain value-chain diagram | What depends on what — the anchor need and the components beneath it. | Evolution. It treats a genesis component and a commodity the same, so it can't tell you build vs buy. | You only need the dependency structure, and the maturity of each part is obvious. |
| A Wardley Map | Position and evolution: where each piece sits on the chain, how commoditised it is, and which way it's drifting. | Precise timing and numbers — it's a strategic sketch, not a forecast. | You must decide what to build vs buy, and spot what's about to commoditise before a rival does. |
The evolution axis is the part that's genuinely new — and it's not a mood, it's four stages. Each one comes with a different right posture. Get the stage right and the build-vs-buy decision makes itself.
Novel, uncertain, rare. Nobody has done it; you're not even sure it works yet.
Understood but still bespoke and rough. Every team builds its own, its own way.
Good-enough products and services exist; vendors compete on features.
Standardised, metered, boring, everywhere. Indistinguishable between suppliers.
Each card is a real component a team has to decide on. Read where it sits on the evolution axis, then choose: build it in-house, or buy it off the shelf? Two are traps — something that sounds generic but is actually close to your core, and something teams love to build that they really shouldn't.
Once you can see the map, you start noticing it everywhere — in the roadmaps that quietly waste a quarter, and the ones that put effort exactly where advantage lives. Four you'll recognise.
It's 2025 and a team spends two quarters on login, sessions, SSO and password resets — then ships three security bugs. Authentication commoditised a decade ago; the map would have shown it parked hard on the right.
The one component sitting in genesis on your map is the thing customers can't get anywhere else. Handing it to an agency or a generic vendor to "save time" quietly gives your moat away — you've outsourced the only part that was yours.
Ten years ago you sized a server and rented it by the month; today compute is a per-second, serverless utility. The component never moved on the value chain — it slid right on evolution. Contracts, team skills and architectures that assumed "product" are now overpriced.
A team pours its best engineers into a bespoke queue, a hand-rolled deploy pipeline and a custom storage layer — all commodities — and calls it strategy. It feels like engineering excellence. On the map it's effort spent far right, where no customer can tell you apart.
The hard part isn't plotting the dots — it's the honesty to admit your "special" component is a commodity, and the nerve to keep building the novel core while a rival ships faster on bought parts. That's the work we do with the leaders and teams we coach: turning a picture on a screen into a build-vs-buy call the whole team can stand behind.
Talk to us about strategy coachingEffort spent on the right-hand side is invisible to customers; effort on the left is where advantage lives. Position on the map decides build vs buy — not taste or habit.
No component sits still. Today's genesis is tomorrow's product and next decade's utility. Strategy is partly knowing what's about to commoditise — and not being the last team to custom-build it.
Bullet points and OKRs don't show position or movement. A map lets a whole team point at the same picture and argue about where things are — and where they're heading.