How to map a value stream

Mapping a value stream isn't just drawing a diagram: it's getting teams to walk together along the path value takes to the customer. Along that journey, handoffs, bottlenecks, and, above all, a shared understanding emerge.

better

Org Strategy

Footprints simulating the steps of a value stream


In the previous article, we explained what a value stream is and why, for us, it is the heart of the operating model. Here, we share how we work on it with the organizations we guide.

A value stream is the sequence of activities that an organization carries out to respond to a customer request: the steps taken, one after the other, to deliver value. Unlike an organizational chart, which is read from top to bottom, a value stream runs across the organization from side to side, spanning multiple departments. Mapping it is the way to see the system that produces results, and the foundation for deciding how to organize afterwards.

When starting out, we almost always encounter the same thing: each department knows well what it does, but knows little about what the others do. And what they think they know is often outdated or out of context: processes that have been modified over months or years, agreements that lost their context, steps that no one remembers why they exist.

Karen Martin and Mike Osterling describe it like this: in most organizations, no single person can describe the complete series of steps required to transform a customer request.

That is why a value stream is not mapped from a desk. It is mapped with the people who make value happen.

Who needs to be in the room

A value stream is divided into stages: the key moments of the customer journey—for example, discovering the organization, purchasing, using the product or service, and receiving post-sale support. Each stage has its processes, its owners, and its handoffs to the next.

Team leaders and department heads participate. More specifically, the people who have ownership of the main tasks in the flow.

Usually, they coincide with the heads of the departments, but it should not be taken for granted: in a value stream, the owner of a stage does not have to be the owner of the department. A stage can span multiple departments, and a department can participate in multiple stages.

How we work

We do it in three stages:

  • Workshops with all departments for the overall mapping: the stages of the value stream, from end to end.

  • One-on-one sessions with directors to map the processes of each stage in greater detail.

  • Validation sessions with executive leadership and heads of cross-functional areas.

The order matters. First, you look at the big picture and then at the detail, so that each process is understood within the complete journey and not as an isolated piece. And validation includes cross-functional areas, such as technology, data, or legal, because they serve all stages simultaneously.

After each phase, we review the outcome with the team. Not to consider it final, but to question it and dig deeper: is there true alignment, or does it only seem that way?

Our role is, above all, to facilitate. We provide ideas or solutions to the extent that the group needs them, but the goal is for the team to take ownership of the solutions, work collaboratively, and align throughout the process. Martin and Osterling sum it up in one phrase: value stream mapping is a team sport.

Starting with the customer

We start with the customer because they are the ultimate recipient of value. Focusing on them also helps maintain a user-centric approach: thinking not so much about how we do things, but about how the customer needs them.

The questions are open-ended, designed to spark conversation rather than fill out a template. The first is usually very simple: “If I were a customer, how would I discover you?”. And from there: “And then what?”. “And after that?”.

This repeated sequence outlines the stages of the value stream from the perspective of the one receiving the value, rather than from the structure producing it.

Within each stage, the questions dive into the details:

  • What value does the customer receive?

  • Who serves them and through which channels?

  • Who is responsible for each step of the process?

  • What documents and information are required?

  • What must be handed off to the next area?

  • What tools are needed?

Even so, in each stage it is also worth asking what value is generated for the business, or at what point it is produced. This is the value balance we discussed in the previous article: starting with the customer does not mean forgetting the organization.

What travels and who owns it

There is a part of the mapping dedicated to defining what travels through the value stream—that is, what the organization offers and delivers to the customer. Usually, these are products or services, and each case changes how you look at the map.

If they are products, it is the product that moves through the chain: it is designed, offered, purchased, and operated. Alongside the flow that operates it and delivers it to the customer, someone needs to identify market opportunities, design the products, measure their performance, and improve them. That is why a question arises that many organizations have not explicitly asked themselves: which department or level of the organization should own the products, and what shape should it take?

If it is a service, what moves are people: the customers themselves. The map then looks more like a service blueprint, showing what the customer experiences at every moment and what the organization does, both frontstage and backstage, to make it happen.

In a recent project, that conversation helped define a department that did not exist: one that could take ownership of the products and market opportunities. The map not only showed how the organization worked: it also revealed what it was missing.

What is delivered and who is accountable

Between each stage of the value stream, there is a handoff: each department receives something from the previous one and delivers something to the next. An incomplete file, data in the wrong format, or an approval without context may formally meet the delivery requirement, but they force the next stage to come to a halt. A large part of an organization's friction lies in these handoffs.

With the stages clear, we guide the leaders to review and agree upon what each area must deliver to the next. And, above all, to redefine accountability.

Here lies the paradigm shift: each stage is responsible for delivering to the next in a way that allows it to consume the deliverable properly. It is not just about producing something or completing a task, but about enabling the next stage to carry out theirs.

— It is not just about completing a task, but about enabling the next stage to do theirs. —

What to measure at each stage

Each stage needs its own performance metrics. They usually combine several perspectives: incoming volume (the number of leads or requests), how much of that volume moves forward (conversion), how long it takes (cycle time for each stage), and how much it costs (operational cost).

Measuring by stage allows you to see where time and costs accumulate, rather than relying on an overall figure that does not tell you where to act.

Where it gets stuck

With the map and metrics on the table, we conduct an evaluation with everyone and ask them to point out where the flow gets stuck. Throughout the process, we also question levels of cooperation and identify which tools, processes, or areas are generating friction or issues.

A bottleneck is the point where the flow narrows: work piles up, waits, or has to be redone, and everything downstream moves at the pace of that point. That is why improving other stages accomplishes little as long as the bottleneck remains.

Those bottlenecks almost always exist. They are the starting point for organizational transformation initiatives: each quarter or half-year, planning should include initiatives that address these bottlenecks to make the organization more efficient.

Each stage poses its own challenges and forces the team to think of ways to solve them. Here, something important emerges: many organizations look alike, but each one needs to devise solutions and structures for itself.

— Organizations may look alike, but each one needs to devise solutions and structures for itself. —

Does this work at a larger scale?

We also question scalability. We run theoretical exercises: if the flow of this value stream doubles or triples in the future, will this stage still work? What will get clogged? What will it need to support that capacity?

These questions allow us to look ahead and envision growth scenarios, ensuring that the solutions designed today are scalable and sound.

Fighting over words

There is a type of friction that, surprisingly enough, tends to be the greatest in the process: word choice. Each department wants things to be called what they are used to calling them, and debates flare up around a single term.

A common example: for one department, a “customer” is someone who has already signed a contract; for another, anyone who asked for information. Both use the same word, but mean different things, and their numbers no longer add up.

In reality, it is about aligning on what a word means. It does not matter what something is called, as long as everyone shares the same meaning.

— It matters what something is called, as long as the group shares the same meaning. —

What remains

The artifacts are created and shared in collaborative tools like Miro or FigJam, and made available to the entire organization in PDF format as well. In addition, they must be documented by the departments that own the processes, ensuring that the map does not remain a mere project deliverable and is updated whenever processes change.

Yet the most valuable thing is not always the map. As work progresses, the group usually achieves strong alignment because they ultimately build, or negotiate, a shared understanding of how the organization works. Martin and Osterling describe value stream maps as effective tools for leadership alignment, and that is what we see in practice.

After the map

With the value stream mapped, bottlenecks identified, and responsibilities agreed upon, another phase begins: adoption—getting the organization to operate according to what has been drawn. We will discuss that in another article.

When was the last time the departments in your organization sat down together to define how value reaches your customers?

Shall we talk? Write to us at hello@bettter.co

Important note: Our writings are the result of our experience and working philosophy, as well as the learning experiences gained throughout our lives and with our clients. They are personal accounts, ideas, and provocations. If you find them useful, feel free to make them your own.

Sources

  • Karen Martin and Mike Osterling, Value Stream Mapping (McGraw-Hill, 2013). Chapter 1. Our translation.

We share everything we know and experience through our blog. Leave us your email and receive our reports, news, and case studies in your inbox.

We share everything we know and experience through our blog. Leave us your email and receive our reports, news, and case studies in your inbox.