Featured Product
This Week in Quality Digest Live
Lean Features
Chuck Werner
Manufacturers must be data driven and have a continuous improvement mindset amid disruptions in the supply chain
Gleb Tsipursky
Remodeling the work setup will help teams shift successfully across post-pandemic workplaces
William A. Levinson
‘Utility divided by cost’ encompasses literally everything we need to know
Jim Benson
‘The time to relax is when you don’t have time for it.’
Bruce Hamilton
How a TPS teacher sees a shipping department

More Features

Lean News
Partnership embeds quality assurance at every stage of the product life cycle, enables agile product introduction
First trial module of learning tool focuses on ISO 9001 and is available now
Offset-aware programming of spindle transfers and bar pulls helps manufacturers drive multichannel CNC machinery
Freedom platform connects to any industrial asset to provide automated intelligence related to asset availability, utilization, and continuous improvement
Galileo’s Telescope describes how to measure success at the top of the organization, translate down to every level of supervision
Too often process enhancements occur in silos where there is little positive impact on the big picture
This book is a tool for improvement and benchmarking
Real-time data collection and custom solutions for any size shop, machine type, or brand
Collect measurements, visual defect information, simple Go/No-Go situations from any online device

More News

Jim Benson


The Exercise Every Team Needs

Value stream mapping for knowledge work, where lean and agile collide

Published: Tuesday, August 10, 2021 - 12:02

Value stream mapping is a team exercise, it’s collaborative, enlightening, and the foundation for professionalism.

I’m pretty well-known for saying that teams are unique and that there is no one process that satisfies every team’s needs. There is, however, one activity that I’ve seen every team we’ve worked with, in countless fields—from construction to software engineering to banking, even with groups of patent lawyers at the United States Patent and Trademark Office—and that is a value stream mapping (VSM) exercise.

More than anything else, and perhaps surprisingly, this exercise builds culture and gives teams the means to actually take control of their work. From what I’ve seen, you can’t be a self-organizing team without first seeing and understanding the work you actually do... in all its raw, painful reality.

If you can’t describe what you are doing as a process, you don’t know what you are doing.
~ W. Edwards Deming

What is value stream mapping?

The VSM exercise has a long, technical, and perhaps even off-putting name. It was originally conceived of to see the steps in any process, and identify places for improvement. A laudable goal, a worthy goal, even, and I probably lost about 25 percent of the readers by stating it.

But I promise, it has evolved to much more than that. More relevant, more powerful, more inspiring.

The VSM exercise is a launchpad for many types of conversations. They are moments of actionable vulnerability that as change agents give us an opportunity to get people to accept levels of operational transformation that would normally scare them.

Why do we need value stream mapping?

Why do we need value stream mapping?

A VSM exercise lets us see everything about our work, not just so we can improve a few things, but so we can actually know what our culture is, what it produces, and how to maintain it. The culture creates the product. The culture makes sure we go home every day feeling satisfied. The culture on-boards people humanely, fairly promotes, lets us learn.

Every team needs a VSM exercise because almost every team we’ve ever worked with makes assumptions about the way they work, and how they are (of course!) aligned. Simply put, that means almost every team on Earth really doesn’t know what they are doing.

Why is this surprising?

Our goal with VSM for knowledge work is to:
• Co-create a shared understanding of common workflows
• Co-create a shared understanding of how things deviate from those common workflows
• Co-create a list of things that don’t always go as planned
• Co-create a set of circumstances where we will talk to/collaborate with people external to our team
• Co-create a set of solutions for anything that might require fixing

Or to be more concise: The goal with VSM is to co-create a shared understanding of who the team is, what they do regularly, and how inhumane their current systems are.

It’s not hyperbole when we say every single team we’ve done VSM with has benefited from the experience. We will likewise add, this is regardless of their initial hostility toward the exercise. Some teams or team members will always try to opt-out of the process. That’s normal, it’s healthy, and if it doesn’t happen at least a little, you know that you have a bunch of people who will say “yes” no matter what you ask them to do. (In other words, they aren’t really participating, they are placating.)

What tends to happen is this: Enthusiastic people start building a value stream map based on their enthusiastic rose-colored “everything is groovy” mindset.

The people who are opting out can only take that for so long. When their frustration reaches a critical point, the opt-out people will jump up to “correct” the enthusiastic people. They get ready for a fight, but instead find collaboration. They get ready for defense, but instead are immediately disarmed by informed conversation.

It is truly beautiful.

if you can’t describe what you are doing as a process

How is a value stream mapping exercise done?

We generally do VSM exercises over the course of two days to a week. Spreading out the activity with an evening break in between gives people a chance to sleep on what can be some very emotional conversations, realizations, and decisions.

When we do them remotely, we will never do more than a 4-hour session on a given day and often try for under three. We find that online workshops are 100-percent more draining on individuals than in-person sessions. They are still useful and necessary; they just take more cognitive energy.

The Modus Way of Mapping Value Streams

The steps sound simple but are incredibly deep:

1. Gather team with gear. Whether virtually or in person, you’ll need people. These are the people who actually do the work. Not just managers or people who think they know what the work is. People who really do the work must do the VSM exercise. Since no one knows how work is truly done, we need to include people with the most intimate knowledge. These people will also be wrong, each in different ways. One perspective never provides an accurate VSM.

They will need super sticky Post-it notes (many colors) and Sharpie markers. There are virtual alternatives if you are using an online tool like Miro or Mural.

2. Start with the end in mind. Starting with the last step (say, delivery to client or shipping or happy customer), the team then works their way backwards through the delivery of the product or service. If you go forward, your VSM exercise will be short and disappointing. Going backwards forces people to really think about the sequence, composition, and emotions behind the way work gets done.

3. Watch the conversations, frustrations, and deviations. You will find that work is rarely done one way, but in several acceptable and unacceptable ways. There are deviations. There will be points where people are surprised by the impacts of their actions. There will be points where people realize they are personally causing problems for others. There will be points where people may become angry, frustrated that they have “told you this a million times.” But now... now they are seeing the system. And that visibility to the causes and consequences of how you work is probably the most valuable deliverable for the individual professionals, the team, the company, and your customers.

When issues arise, have people mark them with a red Post-it and a description. These aren’t just improvement opportunities like “get another printer,” they are usually problems with a high emotional value to the professionals on your team. Fix those and you’ve fixed more than just the problem.

4. Add improvements, collaborative opportunities, and notes. This is where we start to deviate from a “traditional” VSM. In knowledge work (described more below), collaboration, immediate improvements, and additional understanding are a major part of the value of the exercise. No team works in isolation, the more isolated your team is, the less it is a team and the more it is a silo.

We want to capture, directly, where in the value stream a team would benefit from more appropriate communications and relationships with “other teams.” We find that many internal frustrations are blamed on other teams, when in reality the work the team had wasn’t just theirs... but no one told the other team.

5. Make it daily. Build your Personal Kanban using the value stream map, track work through the flow you have agreed on, and use the value stream map itself to track the improvements you have made. Let people on your team see the improvements they have made and still wish to make every day. Lastly, make sure you review the improvements, celebrate them, and create an expectation for all that a professional team is always making itself better.

How is VSM different for knowledge work?

value stream mapping in knowledge work

Lean coaches have been doing VSM for years. Agile teams rarely do them but are starting to. We have done VSM in dozens of verticals now. They range from real estate, drug treatment, software development, banking, construction, architecture, hydro-engineering, research, international governance, bioresearch, manufacturing, even rocket assembly, and more.

We’ve found some significant differences in doing these with knowledge workers that cannot be understated.

Collaboration is flow

We are predisposed to accept work for ourselves as individuals and assign work to other individuals. The fact is people so rarely work alone as to make it a near impossibility. We always work in teams and for customers. When we inhibit collaboration, we inhibit flow, communication, relationships, respect, and learning. When we inhibit collaboration, we inhibit quality and professionalism.

Variation is a sword

In knowledge work we want to reduce or exploit known variation but not make it go away. In manufacturing, where we are more interested in commodification, we want it to go away. This distinction is important because it radically changes our relationship with variation.

In the short form, in our work, variation is the range of ways we can work at any specific time. That variation is a function of complexity and the level to which we understand our work. The lower the understanding, the lower the variation (variation itself is a very long blog post). In knowledge work, we are often making money or achieving professional satisfaction by discovering things, solving problems, or making something better for the customer.

When we feel that we can just produce the same thing over and over again, that is called “commodification.” Knowledge work that has been commodified ceases to grow and is simply foisted on the customer.

Variation that is seen early as an opportunity can come in the form of problems to solve, weird needs of a specific customer, a leapfrogging of our capabilities by the competition, a technological roadblock, or a crazy idea by our team members. Most often, we ignore these or sweep them under the rug until they become an expensive problem... but they were originally an opportunity.

The VSM is the ‘where we see it all’

In lean, we want to go to the gemba, the place where work happens. This is where the evidence is and where things are truly visible. In knowledge work, most of the value creation or processing of raw materials is done in people’s heads. Without really expensive machinery, we aren’t going to see that particular gemba.

For knowledge work, the VSM and any visual controls it creates becomes our gemba, or a proxy-gemba. We see what is happening here. We can fix things here. This is an impactful difference between traditional and knowledge work VSM exercises. We can’t map something out here and then go look at the assembly line. We have to map this and create things that will become as tangible as an assembly line.

Accountability becomes responsibility

As we see the work as a system that all professionals are part of, we see not just what everyone is “supposed to do” (accountability), we see what everyone “can do” (responsibility). We can set up a system where every professional in your organization can truly help the product get created, improved, and released with quality. Not because we’ve told them to, but because they’ve built a system to allow them to.

We love doing value stream mapping

Like I said, we’ve done more than 100 VSM exercises. They are probably the most rewarding work we’ve done.

Work with us. Talk about us doing a VSM exercise with your team(s).

Take the class. Sign up for our VSM for Knowledge Work class, it’s part of our online school at Modus Institute.

Or get really serious. Really take this to the next level with our certification/accreditation in visual management, of which VSM is a foundational element.

First published May 31, 2021, on Modus Institute blog.


About The Author

Jim Benson’s picture

Jim Benson

Jim Benson is the creator and co-author (with Tonianne DeMaria) of the best seller Personal Kanban (Modus Cooperandi Press, 2011) winner of the Shingo Research and Publication Award, 2013. His other books include Why Limit WIP (Modus Cooperandi, 2014), Why Plans Fail (Modus Cooperandi, 2014), and Beyond Agile (Modus Cooperandi Press, 2013). He is a winner of the Shingo Award for Excellence in Lean Thinking, and the Brickell Key Award. Benson and DeMaria teach online at Modus Institute and consult regularly, helping clients in all verticals create working systems. Benson regularly keynotes conferences, focusing on making work rewarding and humane.