What a Wardley Map Actually Is
A Wardley Map is a 2D diagram that plots the components of a system (or business) based on two properties: how visible they are to the user, and how mature the technology is. Think of it like a topographic map for your technology stack — instead of elevation and coordinates, you're plotting visibility and evolution.
Y-Axis: Value Chain (Visibility to the User)
The vertical axis represents how directly a component serves the end user. Components at the top are things the user sees and interacts with. Components at the bottom are invisible infrastructure that supports everything above.
- Top of the map: The mobile app, the checkout page, the search bar — things users touch directly.
- Middle of the map: APIs, business logic, internal services — things that enable the user-facing components.
- Bottom of the map: Compute, networking, power, storage — foundational infrastructure the user never thinks about.
Components are connected by dependency lines flowing downward. The mobile app depends on the API, which depends on the database, which depends on compute. This creates a chain of value from the user down to the infrastructure.
X-Axis: Evolution (Technology Maturity)
The horizontal axis represents how mature or evolved a technology is. Every technology follows a predictable lifecycle from left to right:
| Stage | Characteristics | Example |
|---|---|---|
| I. Genesis | Brand new, experimental, high uncertainty, high failure rate. Nobody knows if it will work. | Quantum error correction, neuromorphic computing |
| II. Custom Built | The concept is proven but no standard product exists. Organizations build bespoke solutions. | Early internal CI/CD tools (circa 2005), custom container orchestrators (circa 2013) |
| III. Product (+Rental) | Competing products exist. You can buy or rent a solution. Features differentiate vendors. | Jira, Datadog, GitHub Actions, managed Kubernetes |
| IV. Commodity (+Utility) | Standardized, interchangeable, cheap, boring. Differentiation is on price and reliability. | Electricity, cloud compute (EC2), object storage (S3), DNS |
The Critical Insight: Inertia and Movement
Everything moves from left to right over time. What was Genesis yesterday becomes Custom Built today and Commodity tomorrow. Container orchestration was Genesis around 2013 (Google's internal Borg), Custom Built by 2015 (early Kubernetes adopters writing their own configs), Product by 2018 (managed Kubernetes offerings), and is approaching Commodity today (one-click clusters on every cloud provider).
The strategic power of this axis is identifying where things are versus where you're treating them. If you're custom-building something that the market has already commoditized, you're wasting resources. If you're outsourcing something that's still in Genesis and represents your core innovation, you're giving away your advantage.
When asked "How do you decide whether to build or buy?", don't just list pros and cons. Describe the Wardley Map mental model: "I plot the component on an evolution axis. If it's a commodity — like auth, logging, or compute — I buy. If it's in Genesis and represents our core differentiator, I build. The expensive mistake is custom-building commodities or outsourcing your innovation." This shows structured strategic thinking, which is exactly what senior/staff-level interviews assess.
Key Point: The most common strategic error Wardley Maps reveal is building commodities. Organizations routinely spend millions maintaining custom-built systems (monitoring, deployment, identity) that the market now offers as mature products or utilities. The map makes this waste visually obvious — you see a component sitting in the Custom Built column while the market has moved it to Product or Commodity.