Developed by Simon Wardley at Fotango in 2005 and later published openly in his book Wardley Maps.
Plots the components behind a user need by visibility and by how far each has evolved toward commodity, showing what to build, buy, or outsource.
Eight components behind a small-business loan decided online, placed by visibility and evolution
The user need is a small-business owner getting a loan decision the same day. Each component sits across by how far it has evolved, from novel to commodity, and up by whether the owner sees it. The first is placed as an example; place the rest, and the column says whether to build, buy, or rent it. Illustrative.
- Not placedPlacedBuildBuyRent as a utility
- Not placedPlacedBuildBuyRent as a utility
- Not placedPlacedBuildBuyRent as a utility
- Not placedPlacedBuildBuyRent as a utility
- Not placedPlacedBuildBuyRent as a utility
- Not placedPlacedBuildBuyRent as a utility
- Not placedPlacedBuildBuyRent as a utility
- Not placedPlacedBuildBuyRent as a utility
Seen by the user
How far it has evolved
Your sort matched 0 of 8.Your sort matched 1 of 8.Your sort matched 2 of 8.Your sort matched 3 of 8.Your sort matched 4 of 8.Your sort matched 5 of 8.Your sort matched 6 of 8.Your sort matched 7 of 8.Your sort matched 8 of 8.
- Build
- Genesis and custom-built: new, still being worked out, and often where the edge is. Build it in house, with a team free to experiment.
- Buy
- Product: several vendors sell it and compete on features. Buy and configure it; building it again adds cost and no edge.
- Rent as a utility
- Commodity: standard, cheap, and expected. Rent it by use and spend nothing on making it special.
The sort
- Credit decision model: Build. Hidden from the owner, but it is what makes a same-day yes possible. Custom-built and the bank's edge: build and keep it.
- Live cash-flow scoring: Build. Genesis: new and uncertain. Build it with a small team and expect to throw versions away.
- Banker's advice call: Build. Visible and specific to this bank: its people are the difference the owner feels. Keep it in house.
- Online application form: Buy. Visible, but a product: buy one and configure it. Its quality matters; its code does not.
- E-signature: Buy. A mature product the owner sees. Buy it.
- Identity checks: Buy. Hidden and sold by several vendors. Buy it.
- Payments out: Rent as a utility. A standard service every bank uses. Rent it.
- Cloud hosting: Rent as a utility. A commodity bought by the hour. Rent it, and spend the savings on the model.
An example
A regional bank wanted to offer small-business loans with a decision the same day, and the technology team's plan was to build the whole service in house: application, identity checks, payments, and hosting. The estimate was eighteen months.
The head of strategy mapped it instead. At the top, the user: a business owner who needs a yes or no today. Under it, every component the need depends on, each placed by whether the owner sees it and by how far it has evolved, from new to commodity. Most of the plan sat on the right. Identity checks and e-signature were products several vendors sold; payments and hosting were commodities rented by use. Only three components sat on the left: the call a local banker made to every applicant, the bank's credit model for local firms, refined over years of its own loan book, and an untested idea for scoring a firm from its live bank feed. The revised plan bought or rented five components, built the two new ones, kept the banker's call, and shipped in five months.
Why it works
Teams decide what to build by habit: whatever the engineers like building, or whatever was built last time. A map replaces habit with two questions about each component. Its visibility says what the user actually experiences. How far it has evolved says how it should be sourced: new things have to be built and experimented with, mature products are bought, and commodities are rented as utilities.
The map also shows where the edge is. A company that builds commodities spends its best people on work any vendor does as well, and starves the few novel components that make it different. Because components keep evolving toward commodity, the map also shows what will change: today's custom-built differentiator is tomorrow's product, and the plan should expect it.
The thinking behind it
Simon Wardley Simon Wardley, a British business strategist and former chief executive, created the method at Fotango in 2005. His map places the components needed to meet a user's need by how visible they are to the user and by how far each has evolved from novel to commodity, with lines for the dependencies between them. He later published the method openly in his book Wardley Maps, on Medium under a Creative Commons license.
How to run it
- Name the user and the need. One user and one need at the top of the page: a business owner wanting a loan decision today.
- List the components the need depends on. Work down from the need, drawing a line from each component to the ones it relies on.
- Place each by visibility. What the user touches at the top, what sits behind it lower down.
- Place each by evolution. Genesis, custom-built, product, or commodity, judged by the market, not by how the company does it today.
- Mark the components that are moving. An arrow toward commodity where vendors are arriving or prices are falling.
- Read off build, buy, or rent. Build the left, buy the middle, rent the right, and check the plan against it.
- Argue over the map with others. Where people disagree on a placement, the disagreement is the uncertainty to resolve.
Where it goes wrong
Components get placed by how the company does them today. The bank runs its own data center, so hosting gets marked custom-built. Place each by the state of the market; the gap between the two is a finding.
The map has no user. It starts from the systems the company owns and shows the architecture, not the need. Start every map from one user and one need, and leave off anything the need does not depend on.
The map is drawn once. Components evolve, and a map from last year marks as custom what is now a product. Redraw it when the plan is reviewed and mark what moved.
When to use something else
- Value Stream Mapping. When the question is where time and waste sit in a process, not how to source its parts.
- Technology S-Curve. When the question is how far one technology has left to improve before a successor overtakes it.
- Porter's Five Forces. When the question is how attractive a whole industry is, not how to build one service in it.
Where it sits in SOLVE eX
Go to the source
- Wardley Maps, book published openly on Medium; the practice began at Fotango in 2005