Intro to Wardley Mapping

A hard truth of decision-making is that complete information will never be available. We use tools, techniques, shorthands, and experience-laden aphorisms to fill in the gaps, but they remain inadequate.

Our individual coping mechanisms are bespoke, weird, and inconsistent. We struggle with self-contradiction over time. Decisions made tomorrow will unfold differently than those made today, even with no new information.

These individual problems compound in organizations, where most of us do our work. Thanks to markets that assume strategic incompetence, we can mostly get by if we at least do the wrong things together. But that requires cooperation, which demands shared understanding.

Shared understandings only come about when we can communicate. And we are very, very bad at communicating (as evidenced by most group problem-solving conversations).

We are missing placeholders for our past understandings, so they can reach into our present decisions. We are also missing a way to share with others. Wardley Mapping can help with both.

Wardley Mapping is all about building a shareable visualization of context and intention. It affords the articulation of a detailed strategy while remaining intuitive and compact. A Wardley Map placeholds a point-in-time understanding, making consideration and discussion possible.

Every organization operates within a landscape that represents the context for its decisions. To build a Wardley Map, we express that landscape as a value chain — a series of interdependent activities required to meet user needs. We also categorize the elements of the value chain according to their stage of evolution under supply and demand competition. The result is a single, dense graphic describing our assumptions that anyone can learn to read.

Use mapping to quickly and proactively analyze solution sets. You’ll avoid costly mistakes and minimize the chance of missing something important. Every step of the mapping process reveals new insights that enable better decisions. Basic use helps with knowing what to build, buy, and outsource. Deeper exploration increases the probability of stumbling upon something novel.

In general, I view it as a standard practice to diminish risk.

How to map

Mapping is a continual process, with an infinite level of potential iteration and detail. Don’t stress about getting your first map perfect, because you can always make improvements as you discover new information.

Step 1: What is your purpose?

As a product manager, analyst, executive or anyone else responsible for outcomes, the first thing to do is articulate your purpose. What is that core principle that prompts you to do this work? What do you hope to achieve, and why?

Helpful questions:

  • What is your purpose?
  • Why do others follow you?
  • What is the higher reason for doing this work?

Step 2: What is the scope?

Next, describe the scope of the map. A reasonable scope can be an individual problem, a product, a business, or an entire industry. Articulating the scope helps you stay focused as you build the map.

Helpful questions:

  • What critical work are you doing right now?
  • What elements of your work have a lot of moving parts?
  • What are the individual problems that need to be solved?

Step 3: Who are your users?

Any purposefully created thing has “users.” Whoever finds your product valuable is a user in this context. A work of art has an audience, a ridesharing service has drivers and passengers. Remembering whom your work serves is important. It can be all too easy to forget critical users when deciding on strategy!

Helpful questions:

  • Who are your users?
  • Who is expecting something from you?
  • Who is asking for help?
  • Who is missing from the picture?

Step 4: What are their needs?

One of the fundamental principles of Wardley Mapping is a focus on user needs. Once you know who your users are, becoming familiar with their needs can guide you toward doing the right work, intuitively. All you need is one guiding question: Is this work aligned with our users’ needs?


Helpful questions:

  • What are your users’ needs, and why do they have those needs?
  • What’s their first interaction with you? Why did they come to you?
  • What happens next?
  • What happens last?
  • Are there any unmet needs not listed?

Step 5: What is the value chain?

Understanding user needs is only part of the picture. The constant pressure to responsibly allocate resources (time, effort, funding) means you must prioritize the right work. The Value Chain can help you make those determinations.

To create a value chain, examine your users’ needs and then list all the activities that need to happen in order for their needs to be met. These will be your “first order” activities. Now list any other activities that need to happen in order for your first order activities to be fulfilled, underneath. This will result in a layer of “second order” activities. Continue this process until all activities are identified.


In order to keep track of which activities are subordinate and how they relate to each other, draw lines connecting the subordinate activities to their superior activities. In other words, identify the dependencies.


Note that when any of these dependencies break down, the effect cascades up the chain and can prevent the fulfillment of user needs. Identifying these dependencies means that they can be monitored and managed. At the same time, any work that doesn’t fit into a value chain is at risk for being waste. Observing dependencies and avoiding wasted effort are effective ways to diminish risk.

Helpful questions:

  • What are all the activities that need to happen in order to meet user needs?
  • What are the dependencies? Which activities depend on which other activities?
  • Is a dependency missing or unmanaged?

Step 6: How evolved is each component in the value chain?

Each dependency in your value chain has evolved through the forces of supply and demand competition. During this evolution, its characteristics have changed as well. In fact, each dependency exists on a spectrum that spans from the new, uncertain and failure-prone to the old, boring and reliable.

A component’s placement on the spectrum of component evolution indicates the most economical way to approach it: Outsource, buy, or build? The fact of the matter is that most organizations will approach each component in a way that matches their own internal bias. In other words, if you like building things, you’ll probably attempt to build it. If you like buying, you’ll probably attempt to buy. And if you like outsourcing, you’ll definitely attempt to outsource. This is expensive and wasteful, when components can instead be treated in an individually appropriate way.

A more evolved component can be outsourced and treated like a building block, while a less evolved component usually needs to be built from scratch or given other investment (money, time and energy). The real danger is in mistreating a more evolved component by building it from scratch. To illustrate the point, consider Thomas Thwaites’s toaster.

Outsourcing highly evolved components is a critical aspect of building cost-effective solutions. Since you have limited resources, it makes sense to save them for the components that actually need special treatment. Don’t reinvent someone else’s wheel!

For each dependency in the value chain, use the evolutionary characteristics cheat sheet to determine where the component belongs: Genesis, Custom, Product, or Commodity. For example, you might ask what the market is like for a component. If the market is undefined, then the component is probably in Genesis. A growing market, however, might suggest it’s in Product (+rental). Place each component along the horizontal axis (Evolution) according to your determination.

Don’t worry too much about placing users and needs. If it helps to do it, by all means do so, but there’s no hard rule.


Helpful questions:

  • How evolved is each component?
  • How does the market view or treat it?

Step 7: Now what?

By orienting around your users’ needs and the dependencies involved in fulfilling them, and how to treat those individual dependencies, you can now perform a quick gap analysis:

  • Are there any components labeled as “Commodity” that you haven’t outsourced?
  • Are there any components labeled as “ Product” for which you haven’t purchased an off-the-shelf product?
  • Are you doing this the hard way, e.g. building when you can buy? And if so, why?
  • On which components have you decided to focus your energy and invest heavily? Are you actually focused, or just spread out?

If this article helped you or if you have questions, I would love to hear from you! You can also hire me for one-on-one mapping work and group workshops for your company. Just drop me a line below!

Lastly, I’m building a fast-paced and pragmatic online course to teach Wardley Mapping to busy people. If you would like to be kept up-to-date about news and announcements, sign up here!


Contact me below!

One thought on “Intro to Wardley Mapping

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s