Wardley Mapping
Wardley Mapping is a strategy technique invented by Simon Wardley that plots a value chain on two axes: Y-axis is visibility to the user (top = visible/customer-facing, bottom = invisible/infrastructure); X-axis is evolution (left = genesis/novel, right = commodity/utility). Each component of your business is placed on the map, then arrows show how each component is moving rightward over time as it commoditizes. The map exposes where you should build (genesis), where you should productize (custom-built), where you should outsource (product), and where you should consume as a utility (commodity). Most strategy fails because leaders treat a commoditizing component as if it's still genesis — building proprietary email servers in 2024 instead of using SES.
The Trap
The trap is using Wardley Maps as a one-time PowerPoint exercise. The maps are useless if they're not REVISITED — the whole point is tracking how components move along the evolution axis over months and years. The other major trap: confusing the evolution stage of a component. Teams routinely insist their 'AI/ML platform' is genesis (novel, must build) when in fact it's now a commodity utility (use Bedrock, Vertex, OpenAI). Building bespoke infrastructure for commoditizing components is the fastest way to burn engineering capital with no defensible moat.
What to Do
Pick one customer-facing user need (e.g., 'a user logs in and sees their dashboard'). Map the value chain top-to-bottom: User Need → Application → Platform → Infrastructure. For each component, place it on the X-axis (genesis / custom-built / product / commodity). Draw arrows showing where each component will be in 3 years. For every component drifting toward commodity, ask: 'Are we still building this in-house? Why?' Repeat quarterly. The map is a living artifact, not a deck.
Formula
In Practice
Around 2008, Wardley used his maps inside Canonical (Ubuntu) to predict that compute infrastructure was moving from product (servers you buy) to commodity utility (cloud). The map showed virtualization moving rightward fast. Canonical positioned Ubuntu to be the preferred OS for cloud providers — by 2013, Ubuntu was the most-deployed OS on AWS. Companies that didn't see this evolution kept building proprietary OS distributions for on-prem hardware and lost relevance.
Pro Tips
- 01
The hardest skill in Wardley Mapping is honestly placing components on the evolution axis. Engineers will always argue their work is more 'novel' than it actually is, because that justifies their team's existence. A useful test: 'Could we replace this in 6 months with a vendor for under $200K?' If yes, it's a product or commodity.
- 02
Pay attention to 'inertia points' — where customers, regulators, or your own org resists moving a component rightward. Inertia is where competitors will attack. Banks resisted moving core banking to cloud for years; fintechs exploited that inertia.
- 03
Use climatic patterns: 'Everything evolves' (no component stays put), 'Efficiency enables innovation' (commoditizing infrastructure unlocks new genesis activity), 'Past success breeds inertia' (the components that made you successful are the ones you most resist commoditizing).
Myth vs Reality
Myth
“Wardley Maps replace traditional strategy frameworks like SWOT or Porter's.”
Reality
Wardley Maps complement other frameworks — they show movement and dependencies that static frameworks miss. SWOT tells you where you are; Wardley shows where the landscape is moving. Use them together: Wardley to spot the evolution, Porter to assess the resulting industry structure.
Myth
“Wardley Mapping requires a precise, scientific placement of components.”
Reality
Placement is approximate by design. The value comes from the conversation: 'Why did you put authentication at custom-built? I think it's a product now.' Arguing about placement IS the strategy work. A map that everyone agreed on instantly is probably just a diagram, not a strategy artifact.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your team is building a B2B SaaS product. You're debating whether to build your own user authentication system or use Auth0/Cognito. On a Wardley Map, where should you place 'user authentication' for a typical 2024 B2B SaaS company?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Engineering Capacity Spent on Commoditized Infrastructure
Mid-stage startups (Series B-D) outside of pure infrastructure verticalsStrategically Focused
< 10%
Acceptable
10-25%
Wasteful
25-50%
NIH Syndrome
> 50%
Source: Simon Wardley research; State of DevOps Report
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Canonical / Ubuntu
2008-2013
Simon Wardley used his mapping technique inside Canonical to predict that compute infrastructure was moving rightward from 'product' (servers you buy and rack) to 'commodity utility' (AWS-style cloud). The map made it obvious that proprietary enterprise OS distributions were going to lose, and that the winning move was to be the preferred OS on whatever cloud providers won. Canonical aggressively positioned Ubuntu as the cloud-default Linux. By 2013, Ubuntu was the most-deployed OS on AWS, and was the default on early OpenStack deployments. Competitors who kept building for on-prem hardware (Solaris, HP-UX) lost relevance.
Strategic prediction
Compute → utility
Position taken
Default cloud OS
Outcome by 2013
Most-used OS on AWS
Competitor outcome
Solaris/HP-UX irrelevant
Wardley Mapping's value isn't predicting that change happens — everyone knows that. It's predicting WHEN a component crosses from one evolution stage to the next, so you can position before the rest of the market catches up.
Kodak
1999-2012
Kodak invented the first digital camera in 1975. By the late 1990s, the value chain was clearly evolving: photo capture was moving from custom-built film+chemicals → product (digital camera) → commodity (smartphone with always-on camera). Kodak's leadership had the data but had massive organizational inertia: film was still a $7B/year cash cow. Rather than aggressively positioning for the digital commodity wave, they tried to keep the old chain alive. By 2012, they filed for bankruptcy. A Wardley Map drawn in 2002 would have shown imaging-as-utility coming — and Kodak's leadership in fact had internal versions of exactly this analysis. They chose not to act on it.
Year digital camera invented at Kodak
1975
Year film peaked
2000
Year of bankruptcy
2012
Strategic failure
Inertia at the cash cow
Wardley Mapping reveals strategic moves; it doesn't make you act on them. Past success creates inertia. The components that made you rich are the ones you most resist commoditizing — and they're often the exact ones competitors will attack you on.
Hypothetical: Mid-stage HR-tech startup
2022-2024
A 200-person HR-tech company was burning $14M/year on engineering. A Wardley Mapping exercise revealed that 35% of engineering capacity was on components that had become products (auth, file storage, search infra, compliance reporting, video transcoding). Over 12 months, they migrated 4 of those components to vendors (WorkOS, S3, Algolia, Vanta). They redeployed 8 engineers to AI-powered features that competitors didn't have. The next year, ARR growth went from 22% to 41% with the same headcount.
Engineering on commodity components (before)
35%
Engineering on commodity components (after)
10%
Engineers redeployed
8
ARR growth change
22% → 41%
The growth unlock wasn't a new product — it was an honest map of where engineering hours were being spent. Most mid-stage companies have 20-40% of engineering effort on components that should be vendored.
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Wardley Mapping into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Wardley Mapping into a live operating decision.
Use Wardley Mapping as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.