A while ago I wrote an article for Flowtopia called From Value Streams to User Needs: Making Flow Visible Where It Starts.
The central argument was that Value Stream Mapping and User Needs Mapping are complementary. Value Stream Mapping helps us understand how work flows through an organisation, while User Needs Mapping helps connect that back to the people we serve, the needs they are trying to meet, and the capabilities required to support them.
I still think that is a useful way of looking at the relationship between the two.
Recently I have been thinking about the language we use to describe that relationship, particularly the familiar phrase “flow of value.”
It is a phrase many of us use routinely. A colleague and I debated what we actually meant by it for a long time, and eventually arrived at this as a useful shorthand:
The continuous movement of value-creation efforts through the network of people, teams, systems and processes that work together to meet user needs.
What actually moves through that network is work, information, requests, materials and decisions. But focusing only on their movement risks missing the more important question: is that work contributing to something truly valuable?
To understand the flow of value, we therefore need to understand both how work moves through the system and what value means to the people the system serves and to the organisation providing it.
That distinction also helps explain why I find User Needs Mapping and Value Stream Mapping useful together.
Two Views of the System
Value Stream Mapping gives us an operational view. We can follow work through a system and see where activities take place, where something waits, where information passes between people or systems, where handoffs happen, and where rework or other forms of friction appear.
It helps us ask questions such as:
How long does a request take to fulfil? Where does time accumulate? Where are the queues and handoffs? Are we optimising one part of the system at the expense of the whole?
User Needs Mapping starts somewhere different.
We begin outside the organisation.
Who are we serving? What are they trying to achieve? What do they need from us in order to make progress?
We then work inwards, identifying the capabilities that contribute to meeting those needs and the capabilities they, in turn, depend on. Teams and technical systems can then be overlaid to show how responsibility is currently distributed and where dependencies, unclear stewardship or cognitive load may be making delivery harder.
A simplified User Needs Map might therefore connect:
user → need → capability → supporting capabilities → teams and systems
This is less a process sequence than a chain of contribution. It shows how different parts of the sociotechnical system contribute towards a user's ability to achieve something they value.
The distinction matters because improving the flow of work does not necessarily mean we have increased value.
If we reduce the time required to make a product change from twenty days to five, we have improved something important about our system of work. But that alone does not tell us whether the resulting change helps anyone make progress towards an outcome they care about.
Equally, we might understand an important user need extremely well while discovering that changing the capability required to meet it involves six teams, several approval processes and weeks of waiting.
Understanding value does not automatically give us good flow. Improving flow does not automatically create value. We need to remain attentive to both.
What do we Mean by Value?
This brings us to another useful perspective: Value Exchanges.
My first real introduction to this concept came through Stephen Fishman and Matt McLarty's book Unbundling the Enterprise.
The book explores digital business models, APIs, and optionality, but one idea that particularly caught my attention was its use of Value Dynamics: viewing a business as a network of participants exchanging different forms of value.
Their Facebook example makes this particularly tangible.
A Facebook user does not simply pay Facebook money for a service. Users provide things such as personal information, activity and content. In return, Facebook provides access to its service and reach: the ability to connect and interact with other people.
Facebook then participates in other exchanges. Businesses pay for advertising and receive reach, targeting and access to attention in return. Developers participate in other exchanges involving applications, users and access.
The model describes several different value currencies, including data, content, reach, services and money.
This is useful because it challenges the assumption that value is synonymous with revenue, or that value travels through one linear path.mDifferent participants value different things, and one exchange may only become economically meaningful because of other exchanges elsewhere in the network.
That gives us a more precise question to ask alongside “how does the work flow?”:
What is being exchanged here, and what makes that exchange worthwhile for each participant?
Value Network thinking has a longer history than Unbundling the Enterprise, with important foundational work by Verna Allee. Krishna Kumar has also been exploring these ideas in the context of value streams and flow; I have included links to his work at the end for anyone who wants to go deeper.
For User Needs Mapping, however, the important idea is fairly simple; we should not assume value merely because work is moving.
Value Exchanges and User Needs Mapping
UNM deliberately begins with the user and asks what progress they are trying to make.
That remains our anchor.
Starting with user needs protects us from simply mapping what our organisation currently does and assuming they must therefore be valuable.
But the idea of value exchange gives us another useful question:
What does each participant give and receive as part of this relationship?
Sometimes the answer is obvious: a customer receives a useful service and provides payment. Often it is more nuanced. A user might provide information in return for insight. An internal product team may consume a platform capability while providing feedback that helps the platform evolve. A partner might provide market access in return for revenue or access to another capability.
Thinking explicitly about the exchange helps us understand why the relationship matters.
UNM then lets us work inwards:
If this is the user, this is what they need, and this is the exchange we want to sustain, what must we be capable of doing to make that possible?
Which capabilities contribute?
Which capabilities support them?
Which teams currently steward those capabilities?
Where are responsibilities fragmented, or where do dependencies repeatedly cross boundaries?
This gives us a useful bridge from value and need into the sociotechnical system responsible for supporting them.
Where we need to understand the detailed movement of work through that system, Value Stream Mapping and other flow-analysis techniques can then provide another view.
Different Maps for Different Questions
I find it useful to think of these as different lenses rather than stages in a methodology.
A Value Exchange perspective helps us understand who participates, what each party gives and receives, and why the relationship is worthwhile.
A User Needs Mapping perspective helps us understand the progress users are trying to make and the capabilities required to support that progress.
A Value Stream Mapping perspective helps us understand how the work involved moves through the system and where delay, waste or friction occurs.
They overlap, but they make different things visible.
Sometimes a Value Stream Map exposes a recurring delay that leads us to examine the capabilities and team boundaries involved.
Sometimes a User Needs Map reveals a fragmented capability and prompts a closer examination of how work moves through it.
Sometimes thinking explicitly about the value exchange makes us question whether improving the existing flow is actually the most useful thing to do.
The question should determine the map, rather than the other way around.
And Then, Perhaps, Talk About Structure
This is also why I remain cautious about questions such as:
“Should we organise around value streams?”
Perhaps. But identifying a value stream does not, by itself, tell us how to arrange teams.
Before making a structural decision, I would rather understand who is being served, what they need, the exchanges that make the relationship valuable, the capabilities involved, and where work is encountering friction. That gives us evidence to decide whether team boundaries, stewardship or interactions actually need to change.
A value stream is not an instruction to redraw the org chart. It is another way of making part of the system visible enough to have a better conversation about what, if anything, should change.
Mapping What Matters
No single map gives us the whole system. A Value Stream Map makes one set of relationships visible. A User Needs Map makes another. A Value Network gives us another perspective.
That is not a limitation of mapping. It is why maps are useful. They deliberately make some things prominent so that we can reason about a particular problem.
For me, the enduring value of User Needs Mapping is that it keeps bringing that reasoning back to a simple starting point:
Who are we serving, and what are they trying to achieve?
From there, we can explore the capabilities that make that progress possible, the work required to provide and change those capabilities, and the exchanges that help us understand whether those efforts are creating something people value.
The goal is not to find one map that contains all of those things. It is to choose the view that helps us make a better decision.
And then map what matters.
Further Reading
Krishna Kumar's Value Networks and Value Streams provides a more in depth exploration of value exchanges, value networks and what we mean when we talk about the “flow of value”. His wider writing in The Polaris Flow Dispatch develops these ideas further.
Unbundling the Enterprise by Stephen Fishman and Matt McLarty is also well worth exploring, particularly its treatment of Value Dynamics and Value Exchanges in digital business models.