What do you do when you’re the Industry Leader – you Improve!

Armstrong World Industries is the global leader in suspended ceilings. That might not seem like much to you, but when you sell over a billion square feet of ceiling tile and the grid to suspend it every year, you’re making a big impact in the construction and housing market.

One of the things that sets Armstrong apart is innovation and forward thinking in all of the things they do. Although other competitors are trying to influence building codes, Armstrong has the strongest presence and is leading the way in making sure office and other spaces are the healthiest, most energy efficient, and quietest they can be.

Paul, the head of codes and standards, was a big fan of my support to other areas of the technology department. We had many conversations on how Lean was helping his colleagues improve their processes and we often wondered how I could support his team’s efforts.

One day, we were talking about codes and standards and how Armstrong’s competitors were making inroads influencing the critical changes for building health and safety. Paul said it seemed Armstrong was losing its leadership position. People were participating on committees and submitting white papers, but weren’t moving the needle in the right direction. He felt we needed a breakthrough to retake our leadership position.

We both realized, almost at the same time, a strategy session could help drive the changes that would maintain our leadership presence. We agreed a Value Stream Mapping (VSM) session was the approach to take.

We plotted and planned. We chartered the event. We invited critical team members, including our internal customers, Sales and Marketing, manufacturing plant representatives, selected engineers and scientists, and members of Paul’s staff.

Our CEO kicked off the event and gave his support to the team. He told us what we were doing would be vital to the successful future for the company. No pressure at all! The team was enthusiastic and energized. But many of them wondered how using Value Stream Mapping would help them create a future that was any different than the path they were on.

There are two critical moments in any VSM event. The first is when you take a Gemba Walk (going to see) through your process. During this walk, the team saw many aspects of the current process that were overly complex and had opportunities for improvement. Many ideas were written down and shared.

The second critical moment happened when the team visibly mapped the current state process on a wall. There were so many steps and delays. There was waste and opportunity beyond anything they had imagined. Now that they could see it, they could do something about it. The ideas flowed even faster. There were so many things within the control of the team, and they prioritized the ideas they thought would make the most difference and could be implemented.

We built plans to attack the most impactful opportunities to drive codes and standards leadership. By the end of the week, we had a roadmap to distance ourselves from our competitors. Everybody won, as the changes would strengthen the health and safety of everyone who inhabits the office, school, and other business spaces. And, because of the alignment of the team and their sponsors, their customers would receive those benefits quickly.

My first VSM for a non-manufacturing process

I applied Lean thinking exclusively to manufacturing processes for many years of my career. I wasn’t able to stretch my thinking beyond what I could see – the production of a physical product and how it impacts the customer, business, and employees. I conducted Value Stream Mapping (VSM – a strategic planning approach based on the view of the customer) sessions for many  manufacturing facilities and we were able to identify countless opportunities to significantly improve safety, productivity, quality, and customer service. I developed a reputation for my ability to engage teams and facilitate complex sessions.

I was approached by Henry, a coworker, to see if I would be willing to use my VSM approach and apply it to his marketing department. This was an intriguing request and a risky one. He had a strong Lean background and the vision to take what he learned beyond the manufacturing arena. I told him that if he was willing to take a chance, then so was I.

I took a session plan for a manufacturing VSM session and started tinkering with it to make it apply to a non-manufacturing process. It didn’t take long to realize the approach didn’t have to change much. The challenge was to help the team visualize their process in a way that would expose the waste, pain, and opportunities for improvement.

During a typical VSM, we take a Gemba walk of the process, to go and see what’s happening and what gets in the way of delivering for the customer. For the marketing department, the process wasn’t something we could easily see. How would I deal with that, I wondered. I talked it through with Henry and we bounced many ideas back and forth.

Then one of us (I’d like to say it was me, but I really don’t remember) suggested we didn’t have to physically see the process in order to visualize it. We had the experts in the room who knew what role they played in the overall process. We could have them talk us through their part, map it on a wall, and then visualize the entire process once all the experts had their say. As long as we started with the customer and worked our way back to the beginning, we could find the waste, pain points, and opportunities.

This was a brilliant revelation. Now the true test was to try it out in a real situation. And that’s what we did. The team engaged and gave their all. We visualized the current state of the marketing process and identified many wastes, pain points, and opportunities to provide an improved customer experience.

My mind opened to the possibilities. I could now apply Lean principles and Kaizen events to any process, not just manufacturing. Through the years, I learned the benefits in non-manufacturing settings can be multiples of manufacturing processes, as most groups haven’t pursued Lean thinking in these settings. There is so much opportunity it’s almost too easy to provide a winning experience for the teams I support.

I now apply VSM visualization to any process teams are trying to improve. It generates many “a-ha” moments and I often get comments like, “I didn’t realize our process was so complex. Now, by seeing it, I know what to do about it.” I recommend using Lean and VSM when you’re improving a process. You’ll be glad you did.

A Random Birthday Message Leads to a Strategic Planning Session

We hear so much about lead generation, Search Engine Optimization, and other marketing methods. I don’t know much about marketing, but I do know strong relationships can lead to business partnerships.

Many years ago, I was Business Team Manager for one of Armstrong World Industries’ flooring business units. I had a co-worker named Jonah, who was the Business Team Manager for another business unit at the same site. He helped me in my early days on the job. He was promoted soon after I got there. Eventually he left the company to go on to bigger and better things.

Many years later, I connected with Jonah on LinkedIn. After that, I would send him birthday greetings and messages related to his career changes that were highlighted on the platform. Recently, I sent him a message that said, “Happy birthday my old friend, I still remember and appreciate all of your help and support during our days together at the Floor Plant.”

To my surprise, he responded, saying, “Thanks Adam, have you ever done capacity analysis?” I had, and when I asked him for more information, it led to a call and eventually a visit to his custom door facility in Florida.

We spent the day together and realized we could accomplish his capacity analysis request and build a strategic plan for business growth using a Value Stream Mapping event.

Two months later, I was facilitating Jonah’s team through their first ever Kaizen event. They were eager to be a part of the change and were engaged throughout the week. It went so well, they were able to achieve all of their objectives and create a vision of the future the rest of the facility and leadership could align around and support.

I understand why others may think they need to use expensive marketing methods to attract clients. I prefer to think strong relationships produce greater dividends, if you truly care about the people you work

Gemba in the Big City

Four years into the Lean Transformation at Armstrong World Industries, we started expanding Lean beyond our manufacturing operations. Forward-thinking leaders came up with an idea to help us better understand the customer experience from the inside. That is, we would conduct a “Customer Experience” Value Stream Mapping event, with the Gemba being the place where the customer interacted with our ceiling products the most – at their job site(s).

We built a team at our biggest plant in the Northeast, consisting of manufacturing, marketing, sales, and engineering. We planned to visit installations, distribution centers, and contractors who carried and installed our products. After laying out the plan on the first day of the event, we split into three travelling teams: Philadelphia, New York City, and Washington DC. I was the facilitator for Team NYC.

We drove up after the first day’s meeting and had a nice dinner. Then, as we planned out our day of visits, I was assigned to a team of three that was going to visit with a distributor and contractor on a job site in the middle of the city.

Our day in the Gemba started at 3 am at the receiving dock for the distributor. This was the assigned time for ceiling tile and grid deliveries. The drive from the manufacturing plant was approximately 3 hours, so they needed to leave around midnight. If they got stuck in traffic, the workers would wait on the dock until the materials arrived. We got there early and the shipment arrived late, so it was a tough start to our morning. We quickly realized this was an opportunity for us to improve the customer experience. Hearing about it didn’t make the same impact as seeing it in person, at 3 am!

After watching the materials being unloaded and stored, we noticed the contractor was ignoring the advice of how high the materials could be stacked. The reason? He didn’t have the floor space to store things two levels high, so he had to store things three levels high. This caused greater damage potential and gave us another critical improvement opportunity we could deal with at the factory.

Once we left the distributor’s site, we drove into the heart of New York City to see an installation in progress. In this case, we saw our product being taken off standard 4-foot by 4-foot pallets and restacked on 2-foot by 4-foot pallets, which was a major loss in productivity. The reason? The contractor elevators in the building were too narrow for the standard pallets to fit. Again, this was another opportunity to improve our customer’s experience.

We found many other things we could help with during our visit to New York City and the other teams found similar improvement opportunities in Philadelphia and Washington DC. When we reconvened at the plant, we prioritized all the ideas and then made plans to address the top issues.

Over the years, the company made many of the improvements to the process we identified as issues during our visits to customer sites. In addition, the manufacturing organization had a clearer understanding of how their customer used their products and were able to convey it in a more compelling way to their employees. Armstrong remains the producer of choice for ceiling solutions, due to their continued focus on improving the customer experience. The lesson here is to go see your customers, in their space, in their time, if you want to truly understand what they value the most. Go to Gemba!

Go to Gemba, Even If You Don’t Want To

In 2019, I was asked to facilitate the annual Value Stream Mapping (strategic planning) event for a leading consumer brands manufacturer at their facility in Central Pennsylvania. I had facilitated their event the prior year and it was our intent to build on the prior results and drive their continuous improvement culture forward during the event.

The culture of the plant was such that I didn’t get direct feedback from the plant manager, but received it indirectly through the technical manager. There was a strong bond between the two of them, and even though the plant manager appreciated the results I was able to generate and my flexibility to work under challenging circumstances, he generally didn’t directly communicate with me. One reason for this may be that I am a story teller and tend to ramble a bit (surprise), and he liked getting directly to the point.

I was asked to facilitate in a way that would increase the engagement of the production and maintenance technicians and also drive the team to Gemba (the place where the work is done). Working with the technical manager, we identified the team members and activities that would accomplish both requests. On the first day of the Value Stream Mapping event, team members at all levels were engaging in the discussion of issues in the factory and were extremely active during the Gemba walk tour of the factory. Every time an issue was brought up, I made sure we were able to see the actual situation, rather than talking about it. The plant manager even made a point of going to Gemba as much as possible. He spoke about it in his opening remarks and reinforced the idea throughout the day.

On the second day of the event, after mapping the total Value Stream, identifying pain points, and brainstorming improvements, the team prioritized the work they thought would drive the performance and safety to better levels in the coming years. The full team was divided into smaller groups to develop solutions to the highest value problems. The plant manager was assigned to a team consisting of two production technicians and one engineer and they were working on an issue that was causing significant problems on the factory floor.

Sitting at a table in the meeting room, they spent a few minutes talking about the problem they were trying to solve and then got some paper and a pair of scissors and started cutting out various shapes and sizes of paper. I kept an eye on what was going on for a while, but then rotated through other groups to make sure everyone was making progress on their assignments. After fifteen minutes, I returned to the plant manager’s team to see what they were up to. I noticed the plant manager and engineer were moving papers around on the table to simulate the layout of the area in the factory they were concerned with. It appeared the two production technicians weren’t involved in the discussion and they looked distracted by their phones and not engaged in what was happening.

I have never been shy and realized I needed to do something. I said, “What are you all working on at the moment?” The plant manager told me, “Adam, we’re trying to understand the current layout so that we can come up with alternatives to improve the situation.” To that I said, “Have you considered going to Gemba to verify your assumptions? How do you know there’s not a post or another obstruction you may not be aware of in the meeting room?” It looked like the plant manager wanted to say something that wouldn’t have been very nice, but instead he appeared to swallow his pride and took his team out to the factory.

A few minutes later, the technical manager came up to me with a wry smile. He told me, “Adam, you sure got the plant manager’s attention. He took me aside and, in his office, told me, “That darn Adam kicked me out of the meeting room and made me go to Gemba!” I said the first thing that came to my mind, “Am I fired?” “No, of course not,” he told me, “I’m glad you did that! He needs to demonstrate the same behavior he was encouraging in the rest of the team.” After a sigh of relief, I said, “He took it well. I could see he was holding his feelings back. But he did the right thing and went to Gemba.” I still wondered what, if anything their team would learn from the experience.

When the team returned, I noticed all four members were extremely engaged and working at the table with newfound energy. Watching from a few feet away, it was apparent that they found something on the factory floor that they had overlooked in the meeting room and it was helping them develop a better solution they all could support. Eventually the plant manager admitted to me he should have known to go to Gemba first before trying to solve the problem in the meeting room. I was glad to hear it and throughout the rest of the event “Go to Gemba” became the rallying cry for all team members.

Best Event Ever

I was the Lean Champion for Armstrong World Industries for six years. My responsibility was to guide the organization to a continuous improvement mindset in all of their activities. I had no direct reports and reported to the Executive Vice President of Global Technology. When we kicked off our Lean transformation, most in the organization felt we were implementing the “flavor of the week” and weren’t ready to commit to changing their habits.

I knew it would be an uphill climb for me, as my job was one of influence. I had to capture the hearts and minds of my coworkers. It would have to happen one person at a time. With approximately 150 members of our team, I knew it would take a while to get to a point where we could see any indication of changing mindset.

As Lean Champion, I had to be a teacher, mentor, sensei, cheerleader, and pain in the ass at different times. Most people would say I was more of a pain in the ass than anything else. It was just me in the beginning, so I needed to get some allies. Luckily, I already had a few managers and coworkers who had seen my earlier Lean efforts with teams prior to our official Lean transformation. They were there with me, fighting alongside of me and lending credibility to my efforts. I also had the support of my manager, who had seen Lean applied in manufacturing and wanted similar or better results. Our group had taken a few hits over the past few years. A factory start-up didn’t go as well as planned and we had slowed our rate of developing new products for the market. There was a compelling case for change.

At the beginning of our Lean transformation, we strategically planned Kaizen events to target areas of the organization that needed the most help or would create high visibility for the results. Our first official Kaizen event was a Value Stream Mapping event, which is the Lean version of a strategic planning session. For many of the participants, this was their first time in a Kaizen event. I always want to generate energy and enthusiasm in the team, and as a facilitator, I had to put myself out there a lot. After my manager kicked off the event with words of encouragement, he handed control over to me. I decided to try something to get a positive reaction. I said, “I want to welcome you all to our very first Value Stream Mapping event in Technology. It’ll be our Best Event Ever!” Most of the room got the irony of the statement and laughed. Some didn’t know what to think and laughed too. I knew I was on to something.

At different times during the Value Stream Mapping event, I brought up the fact that we were doing work to assure this truly would be a great event, perhaps the best ever. People would poke fun at me every time. At the end of the event, during the report out to our sponsor and customers, my manager made a special point to say the event was truly the best event ever. Again, people laughed, but now they had something to use at my expense from then on.

Over the years, “Best Event Ever” was said many times by many people and the organization made many breakthroughs. An 18-month product development cycle was reduced to 10 months. The new product portfolio of $150 million was increased to $380 million. Over 95% of the total organization had participated in at least one Kaizen event and all new employees were onboarded with Lean principles, taught by the Lean Champion. The overall culture of the organization transformed to one with a continuous improvement mindset and the words of their pain in the ass Lean Champion were well ingrained by the time I left for my next adventure.

Understanding is Critical

In February 2020, Process Improvement Partners was asked to facilitate a strategic planning session in Montreal for a global consumer products company. Having facilitated multiple Kaizen events where English is not the primary language, we set about to design an event that would incorporate additional translation time and resource effort for the event. Normally, this type of session takes three days.  Even though we were told that most participants were bi-lingual, we aligned with the sponsor and leader and added four hours to the event plan.

In the weeks leading up to the event, presentation slides were developed and sent to the team leader to be modified to show English and French terms. I knew that the first day of the session would be the most challenging, as most participants had no Kaizen event or Lean experience. With much training, demonstration, and direction, we had to ensure important elements were clearly and correctly understood.

On the first day of the event, every time anyone spoke, there was translation into French or English. Every time someone asked a question in French, it was translated into English. Any English discussion was translated into French. Things were going slower than anticipated. By lunchtime, we were two hours behind. People were getting concerned. I knew we were going to be fine as the week wore on. The first day is more focused on discussion than teamwork and it feels longer and is more challenging to first-timers.

Aligning and Adjusting

At the end of the first day, we were exactly four hours behind. Those four extra hours planned for in the overall event were already used up. Additionally, in a feedback session at the end of the day, most team members said we were translating more than necessary. After most of the team left, we regrouped with the team leader and sponsors to build a plan to get us back on track. On a positive note, all team members were speaking freely and engaging extremely well. This was most critical for the overall success of the event. In preparations for the event, the leader and sponsors weren’t expecting so much engagement. Their initial skepticism led to the translation requirement.

We agreed we would reduce the translation to an “as needed” basis. This meant that we would ask our engaged team members to speak up when they needed translation or further explanation. It was risky, but we would pay attention to the room and draw out requests for translation if we saw engagement declining. We then joined the team at dinner and watched the team strengthen during the evening.

On the morning of Day 2, we explained our new strategy to the team, in English and French, and told them it would be the last translation they received until they requested it. We also agreed not to translate anything into English. When a question was asked in French, it would be answered in French. The facilitators didn’t need to understand the conversation, unless they were asked something they had to specifically answer. The team liked the new approach.

Less Translation, More Engagement

Once we got the hang of the reduced translation and started watching the team for their understanding, progress happened faster and the team seemed more engaged and satisfied. At the end of the second day, the team reflected their appreciation for the change in approach and showed an optimism for the day’s work and the work to come.

The next two days flew by and the team built a strategic plan of which they could be proud. Their plan improved productivity, safety, quality, and customer service. They also learned many new tools and techniques they could use to solve problems in their day to day work. On the final day, ten different presenters told the story of the week and the strategic plan to an audience attending by video conference all over the world. Those in the audience said they could feel the enthusiasm and alignment and were amazed by how professional the presenters were, regardless of their position. They voiced their support to the team and encouraged them to implement their plan. Some even wanted them to implement it sooner than planned.

The week reinforced how critical communication and understanding is for the team to win. Even though we reviewed progress and issues with translation at the end of the first day, we now know we need to do it sooner if we find ourselves in a similar situation in the future. For the team’s part, we can only thank them for hanging in there while we were learning this valuable lesson.

Listen To Your People, People

A Research and Development team wanted to create a three-year strategic plan. Their goal was to reduce the time it takes from a new product idea to launch of the new product.  Many of the team members believed “you can’t schedule invention.” Working with the team leader, the Research and Development Director, we decided to focus on the work leading up to and supporting the invention, even if we couldn’t specify when an invention would occur. We agreed to use Value Stream Mapping as the approach to help the team accomplish their goals.

On the first day of a Value Stream Mapping event, the team learned about Lean tools and techniques, and then quickly went to Gemba (the place where the work is done) to see what was actually happening in their current process, the Current State. Most people who haven’t participated in a Value Stream Mapping event don’t appreciate the time and effort put into understanding the Current State of their process. They want to work on the Future State, thinking they already know the issues, pain, and problems in their current process. But, as Lean practitioners know, there are always breakthroughs and “A-Ha” moments that occur during the Current State review that lead to a much stronger plan for the Future State.

The team wondered how they could walk their Current State, as much of their work was on their computers, at their desks, in labs, and other testing facilities located in the building. Ever the optimist, I encouraged the team to walk the process, regardless of where the work got done to uncover something that would help them on their journey to the Future State.  Although they were skeptical, they agreed to follow my lead. We walked around the offices first.

We saw different people working at their desks and asked them questions about what they were doing. They did their best to explain things, but I noticed most people weren’t taking notes or asking many questions.

Our next stop on our walk was at a large wall containing a wide variety of graphs, charts, and documents. The R&D Director stopped there and told us proudly about how much information he shared with his people and how much they used the information on the wall. The team seemed satisfied with the explanation, but to me, it looked like a bunch of clutter. There were so many charts and graphs, it was unclear what was important, relevant, and critical to the work of the R&D employees.

I walked over to a Scientist who was working at his desk and asked him if he could join us at the board. I asked him what he thought of all of the information that was posted on the wall. He told the group that he didn’t know, he never looked at it. The team, including the R&D Director was shocked. Was this scientist the only one who didn’t use the information or were there others? As it turned out, there were others working in the area who confirmed they didn’t use the information on the board either. I didn’t want to insult our leader, so we continued our walk through the process, taking note of other issues as we saw them. The team started opening up and asking tougher questions as we went further into the process.

After we completed our walk, the team listed all of the steps in the current process and the issues and problems that existed. One of the biggest problems identified was the lack of communication of relevant information to the scientists. It was just as our brave Scientist had said during the Gemba Walk. Now, the team knew what it had to do in the Future State: Provide visible, relevant, and timely information to the scientists in a way that would help them do their work every day. Over the rest of the three days, the team built a path to the Future State that reduced time from new product idea to launch significantly. Much of the effort centered around providing the proper information to the people who needed it. Instead of assuming what was needed, they included the scientists and technicians in the development of the communication of highest value.

Over time, this communication was developed. In addition, the team created feedback loops to verify the communication was helping R&D employees do their work. Ultimately, the time from new product idea to launch was reduced significantly. More importantly, the team realized how important it is to include people in the design of systems that will be used for their benefit. One properly posed question can save months of effort.

Value Stream Mapping: The First Step on Your Continuous Improvement Journey

You can’t reach your destination if you don’t know how to get there. Maps, or in our technology-driven world, GPS systems, are critical resources for guiding you from point A to B. The same is true for your continuous improvement journey. Unlike your GPS, however, you must build your map through learning. The best way to build it is with Value Stream Mapping.

Value Stream Mapping views everything from the eyes of the customer. Anything that the customer would not pay for is considered Non-Value Added and is waste. The key to Value Stream Mapping is to see the waste in the current process and then develop strategies to remove as much waste as possible, delivering maximum value for the customer.

There are the 8 key components of Value Stream Mapping:

Identify the Value Stream to Map
What is the family of products or services that the customer is willing to pay for? Often, companies will pick a product or service that represents a significant portion of their overall demand or represents most of the process steps. It is better to pick a simpler process the first time Value Stream Mapping is attempted, increasing the complexity of processes to map as experience grows.

Build the Team
The members of the team are critical, as they will learn together and become supporters of the work going forward. The team should be diverse, comprised of people in the process, people who manage the process, customers of the process, and suppliers to the process. It can be beneficial to add a few team members who have no relationship with the process, as they provide “outsider” thinking and can challenge the team during the session.

Voice of the Customer
What is most important to the customer, from their point of view? Often, companies will engage Sales and/or Marketing to represent the customer, based on interactions they have had while dealing directly with customers. It is more powerful to invite direct customers to these sessions, but it can also be risky, as they will see some of the waste or inefficiencies in the current process. Most customers appreciate the opportunity to participate in these sessions, and the rewards far outweigh the risks.

Walk the Current State Value Stream
This is typically the most “eye-opening” part of Value Stream Mapping. The team should leave the meeting room and physically walk the process from the last step to the first. If they are mapping a physical product transformation, the team starts at the shipping dock, and then works their way back to the receiving dock. Start with the customer and what they are expecting to be delivered, then work your way back to the beginning of the process. All the while, the team is looking for waste and inefficiencies. They should be taking notes, pictures, and engaging with each other and others working in the process to fully understand what is going on and why things are working or not working as expected. If the process is virtual, the team should be demonstrating the steps of the process as they occur. Do not discuss the process in a meeting room. Go see what’s actually happening. 

Gather data for the Current State Value Stream
How long does each process take? How many resources are needed for each step? How much inventory or waiting occurs at each step? How is information communicated to each step? How long does it take to change from one product or service to the next? How much space is required by each step? There is so much data that can be gathered, that you have to be careful not to do too much and miss the simplest and most impactful opportunities in the Current State.

Map the Current State Value Stream
Once the team returns to the meeting room, they map out all steps and interactions between steps of the process. This is a team activity, so don’t let just one person do all of the work. Each team member can take a pack of sticky notes and write down steps, placing them in order on a wall or something similar. Next, the team should measure the total time it takes for the product or service to get through the Value Stream, measuring the value-added time, non-value-added time, and lead time. Don’t use a computer, this is a visual activity, and most “A-ha” moments occur while placing steps on a wall and seeing how inefficient the current process is. Don’t be surprised if less than 10% of the time is value-added. In many manufacturing plants, that number drops below 1%. One key point is to map the process as it is, not how you want it to be.

Build the Future State Map
The team develops a vision of what they want the process to be in the future, for the benefit of the customer. By seeing the waste and inefficiencies in the Current State Map, the team imagines what the process would look like if they minimized or eliminated non-value-added steps, inefficiencies, defects, safety issues, and other waste in the current process. After the map is created, the team recalculates the value-added time, non-value-added time, and lead time in the future state. It is not unusual to drop the overall lead time to the customer by 50% or more. It’s also not unusual to identify quick, simple activities to accomplish this lead time reduction.

Create a Plan to Achieve the Future State
The team builds a roadmap of activities and strategies to make the changes required to drive to the Future State. These activities are typically low-cost and quick to implement, but some activities require an entirely new way of leading and managing the process. The team develops the action plan, with owners, due dates, and the managing systems to ensure that the work gets done.

A typical Value Stream mapping session takes between 3 and 4 days. When it’s over, everyone knows their new destination and how they intend to get there. Now, leadership has identified what is necessary to take the journey. Just like any journey, you must take the first step. Value Stream mapping is that first step.