A good enough map

A good enough map

I'm often asked about whether we can add a new axis onto a map, to be blunt I prefer not to.

When you map, you start by identifying users and their needs. For example, a Tea Shop has users like the business that wants to sell cups of tea to consumers who will hopefully drink it.

Article content
Users and their need for a cup of tea

You then expand this cup of tea through the capability to make a cup of tea and components required to meet this need. This is a graph, a chain of what is needed.

Article content
A chain of the cup of tea

We then ask "how evolved" each component is. This creates the map.

Article content
The map of a cup of tea

Formally, we tidy this up by adding a line of evolution at the bottom and an indicator for the value chain. NB. There can be many value chains on a single map; there is, in practice, no y-axis because that is contained within the chains themselves; it's more of a directional indicator, i.e. the further you go down the chain then, the less visible the components become to things higher up the chain.

Article content
The Map

Onto this map we can :-

  • Challenge what we are doing - "Why are we custom building kettles?"
  • Add missing components - "Have we thought about staff to make the tea?"
  • Add missing users - "What about regulators?" or "What about staff, don't they have needs?"
  • Add missing needs - "What about a nice place to sit?" or "wifi?" or "a payment method?" or "How about some biscuits!"

We can use the map to discuss how to manage the system, measure it, how and where the landscape is changing, where we should focus to improve operations, and where we should differentiate. There is an awful lot to be discussed with this simple but imperfect map.

However, that discussion does require thought, communication and challenge. The map, as simple as it is, provides a massive compression of information compared to text. To compensate, it also provides a constraining framework (a strong opinion in both the view of value chains and evolution), which enables discussion despite the huge amount of information. Even with this, I have found in research meetings that two hours per day is the maximum time people can work on maps without becoming mentally exhausted. Mapping may be simple, but it is also mentally hard.

Adding another axis will just increase the effort required and up the potential for confusion. That alone would make them less useful. So, yes, you could add more axes or more colours or more symbols or more of everything. But that doesn't mean the maps become more useful. Stripping away more might be the better path.

For me, the maps are good enough until something better and simpler comes along. Less is often more.

Just because it's simple should never imply it was easy. Yet that effort is also often where value accrues. It's not just the final map (vital as it is) but the lessons learned across the dialogues. I'm getting better at explaining maps, and mapping. Now if only I were getting better at drawing them.

Not only ‘good enough’, which suggests we could and should do better, but we’ll judged A useful framework of this sort stimulates and supports human inquiry The urge to elaborate usually seems to me to be driven by a desire to reduce the need for thought - to turn the framework into an algorithm for analysing a system This is the path to complacent passive observation To keep the inquiry alive, frameworks must be handled sensitively and held at bay

I have been following Wardley Mapping for four years. This is the first time I understand it. Past: It is cool! ... But I just don't understand it. Present: I get it!... I can make it! This post is powerful!

All models are wrong, but some are useful.

Maps: Models, Architectures, Perspectives - Models: Symbolic representation - Architecture: User purposes - Perspective: scope https://caminao.blog/enterprise-architecture-fundamentals-the-book/book-nuggets-maps-territories/

  • No alternative text description for this image
Like
Reply

To view or add a comment, sign in

More articles by Simon Wardley

  • A moment of reflection.

    In 2023, I wrote a short series of posts about the AI / vibe coding space. These were subjects that I have covered in…

  • Map evolution not maturity

    Many people inquire if the evolution axis of a Wardley Map can be substituted with maturity. Although possible, I…

    10 Comments
  • Simple suggestions for technology investment.

    TL;DR Be clear on your purpose. Understand the landscape.

    19 Comments
  • AI and the New Theocracies

    Like most people, I use and depend upon multiple AI systems daily. I find them convenient and delightful.

    39 Comments
  • A quick and easy guide to measurement.

    I'm frequently asked, "What are Wardley Maps good for"? Well, they are ideally suited for asking and exploring…

    33 Comments
  • Simple tips for managing any project.

    If you're coming here for the latest and greatest in project management techniques, then I'll stop you there. In this…

    41 Comments
  • Wardley Maps and Cynefin

    I am occasionally asked how to combine Wardley Maps with Cynefin. They are complementary tools, not a replacement for…

    38 Comments
  • Google Next Trip report

    Been a bit quiet of late in terms of writing but then there has been a lot of travel and oodles of events. The most…

    1 Comment
  • Why the fuss about serverless?

    To explain this, I’m going to have to recap on some old work with a particular focus on co-evolution. Co-evolution Let…

    6 Comments
  • On being lost and the imposter CEO

    The first five chapters of my book, covering the beginning of my journey through strategy & mapping is now up as a…

    26 Comments

Others also viewed

Explore content categories