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.