Value Stream Mapping: Finding the Hidden Delays

Dr. Linda Nelms

Hello and Welcome. I am Dr. Linda Nelms and in todays Podcast we will be exploring the concept of Value Stream Mapping and how it is used to identify bottlenecks and streamline processes. To begin our discussion I want you to think about why a request that takes maybe twenty minutes of actual work can somehow take three weeks to actually get back to the person that made the request?

Dr. Linda Nelms

It sounds like an exaggeration, right? But in operations management, we see this counterintuitive paradox all the time. In so many business processes, up to ninety percent of the total time an item spends in a system is spent doing absolutely nothing. Just sitting there, waiting in idle handoffs between people or departments, rather than undergoing any active value creation.

Dr. Linda Nelms

I actually remember seeing this firsthand early in my career when I was working in higher education administration. We were looking at grant proposals. A faculty member would submit a proposal, and on paper, it took fourteen business days to clear administrative review. Fourteen days! So we decided to track it down step by step.

Dr. Linda Nelms

It turned out that the proposal sat in an inbox on the first department desk for four days, got looked at for five minutes, moved to a second desk where it sat for six days, got five minutes of review, and then sat on a third desk for four days for a final ten minute check. Total actual processing time? Twenty minutes. Total wait time? Fourteen business days. That is where Value Stream Mapping, or VSM, comes in.

Dr. Linda Nelms

Value Stream Mapping is a lean technique designed to bring that hidden friction right out into the open. It uses standard visual symbols to depict three distinct horizontal layers across a whole process. At the top layer, you have information flow, showing how orders and instructions move. In the middle layer, you have product or service flow, showing the actual work steps. And at the bottom layer, you have the time flow ladder.

Dr. Linda Nelms

That time flow ladder is critical because it explicitly separates cycle time, which is the active value added work time, from lead time, which is the total clock time from initial request to final delivery. When you map those three layers together, you suddenly see where work is actually moving and where it is just gathering dust on a virtual or physical desk.

Dr. Linda Nelms

And when you look at work from the customer perspective, well, the customer only wants to pay for the steps that actually transform the product or service, right? They do not want to pay for fourteen days of desk sitting. So VSM gives us the visual clarity to root out that idle wait time and focus on what truly adds value.

Dr. Linda Nelms

So, how do we actually put this framework into practice? At its heart, Value Stream Mapping follows a four stage lifecycle. Stage one is mapping your current state workflow, capturing exactly how work happens today, bad habits and all. Stage two is analyzing that map to find and eliminate non value adding waste using things like kaizen bursts. So, a Kaizen burst is a quick, focused improvement activity used in Lean operations to identify and eliminate a specific source of waste or inefficiency. On a value stream map, it is often shown with a burst-shaped symbol to highlight an area that needs improvement. The goal of a Kaizen burst is to make small, practical changes that improve the overall process. Stage three is designing an improved future state map that streamlines the flow. And stage four is executing the implementation plan to make that future state a reality.

Dr. Linda Nelms

Now, although VSM started in manufacturing, its impact in knowledge work and software development is massive. Take software continuous delivery pipelines, for instance. A team might find that moving a new software feature from initial idea to production takes six weeks. But when they draw the current state map, they realize the engineers spent only nineteen and a half hours writing and testing code. The rest of those six weeks, over thirty days, was spent waiting for security reviews, handoff approvals, or sitting in rework loops because of unclear requirements.

Dr. Linda Nelms

By using VSM to identify those specific handoff bottlenecks and eliminating redundant feedback steps, teams have managed to drop their deployment cycles from six weeks down to just two days! That is a dramatic transformation in agility and quality.

Dr. Linda Nelms

However there are a few very common mapping traps that you need to avoid when you are doing this. First, do not overcomplicate your map. It is easy to get bogged down trying to record every microscopic detail, but a cluttered map hides the big picture. Focus on the core steps and high level metrics like headcount, batch size, cycle time, and accuracy percentage.

Dr. Linda Nelms

Second, never ignore the information flow layer. Teams often map the physical or digital work steps but completely miss how decisions and instructions get communicated, which is usually where delays start. Third, do not map without an action plan. A current state map is just a diagnostic tool; if you do not pair it with a future state map and concrete implementation steps, nothing changes.

Dr. Linda Nelms

And fourth, do not try to map multiple product families or services on a single diagram. Trying to trace three different processes on one map creates total confusion. Stick to one product or service family per mapping exercise to keep your analysis clear and actionable.

Dr. Linda Nelms

What I love most about Value Stream Mapping is how it transforms organization culture. In traditional environments, process debates often devolve into individual department opinions or turf wars. Sales blames operations, operations blames design, and so on.

Dr. Linda Nelms

But when you put a data driven value stream map on the wall, or on a shared digital canvas, the conversation shifts entirely. The team stops arguing over personal opinions and starts prioritizing based on objective data and the customer perspective. It builds a shared picture of how work actually flows, fostering total quality management, stronger collaboration, and frankly, a much more engaged, fun environment to work in.

Dr. Linda Nelms

Value Stream Mapping is really your master key in operations management for visualizing process flow, distinguishing value added work from idle wait time, and systematically eliminating operational waste. It turns invisible delays into visible, solvable problems.

Dr. Linda Nelms

As you continue your journey into operations management concepts, I encourage you to put your learning into practice. Try drafting a current state map for a process you encounter, whether that is a workflow in your current job or an every day task like cleaning the house. See if you can spot where the lead time diverges from the cycle time.

Dr. Linda Nelms

To summarize our discussion keep in mind that value stream mapping isn’t just about drawing boxes and arrows—it’s about seeing your operation in a new way. Every process has opportunities to improve, and every small change can create meaningful results. So, the next time you notice a delay, a bottleneck, or a step that doesn’t add value, don’t just work around it—map it, question it, and look for a better way. Keep improving, keep learning, and remember: better processes create better outcomes. Also, I encourage you to check out the additional podcasts available in the Course Resources section! You’ll find a variety of concepts, perspectives, and real-world insights designed to deepen your understanding of operations management and spark new ideas. Choose a topic that interests you, press play, and see where your curiosity takes you. Every podcast is an opportunity to learn something new! Thanks for listening, and until next time, keep finding ways to make work flow better!.