When Someone Knows You Better than you Know Yourself

I met Cody at a conference in December. We got along so well he invited me to visit his new company in Florida. Before the conference was over, he asked for six copies of my book, “The Wheel of Sustainability.” He wanted a copy for every member of his leadership team. Cody told me he was going to require them to read it before my visit. I was happy to share my books, as no one had shown so much interest in them before. I never could have imagined the level of interest and enthusiasm of one person in particular.

In January, I flew to Florida to visit Cody and his team for the day. I was met outside their new corporate building with a bear hug. Cody led me into a conference room and introduced me to his leadership team. I sat down and noticed 4 skeptical looking, “grumpy old men” sitting across the table. Cody sat on my side of the table, and in front of him was my book, with many pages dog-eared.

I introduced myself and shared my interest in the work they were doing in their new company. After a few minutes, one of the men across the table asked me a terse question. I interpreted it to mean, “Who are you and why are you here? We have more important things to do today.” I answered I might be able to help them on their journey as a start-up.

After a few more minutes of shallow questioning, the COO talked about a specific problem they were having. The CIO entered the conversation and after a few minutes, I shared a view of how I might go about solving the problem with a team. Cody then said, “That’s from page 144 of your book, isn’t it Adam?” I was shocked he knew the book well enough to cite the page number. He proceeded to show me it was indeed on page 144. Was this a coincidence?

The conversation started to get more engaging and now it was clear the leadership team was warming up to me and my approach. We started talking about another critical issue they were facing, and I shared my experience in helping other teams in similar circumstances. Cody interjected, “That’s right off page 198, isn’t it Adam?” I said, “I’m not really sure, but I think it’s in my book somewhere.” Cody showed me it was on page 198 and said, “Don’t you know what pages you put your wisdom in?” I replied, “Cody, I was so happy to finish the book I haven’t opened it since. You know my book better than I do!”

Now the room was on my side, we were talking about issues and I was demonstrating ways to help them they could use immediately. After about two hours, the meeting concluded and Cody walked me around the rest of the corporate facility, sharing his vision of what he hoped the company could become. I was inspired.

At dinner, Cody and his team agreed we should figure out a way I could be a part of their start-up journey. I was fortunate enough to be able to assist them for a while and now have the additional opportunity to work with Cody as a partner in my business. It turns out that no matter the circumstances, you should treasure those in your network who are there to support you and understand you better than you might understand yourself.

Five Lessons from My First Five Years in Business

On May 15, 2018, I registered Process Improvement Partners LLC as an official business. Since then, I have had so many adventures, made lots of mistakes, and hopefully learned from many of them!

As the saying goes, hindsight is 20/20. In the spirit of continuous improvement, I have been challenged by a peer to share my top five lessons from my first five years in business (thanks Stephanie!)

ONE: Focus on meaningful relationships, not vanity metrics.

Truly valuing and connecting with the people in your network is way more important than how many followers, views, likes, and comments. Be sure to focus on what really “moves the needle” for you, and this will look different for everyone. Bottomline: you can't fake caring. If you can help even one person, you are doing important work.

TWO: This is a marathon, not a sprint.

It takes time to build up a following that values what you do and how you can help. I used to think the next activity or post would get someone to do business with me. Now, I realize people want to feel comfortable with you and the value you bring. It takes time, but once it happens, meaningful engagements follow.

THREE: Alignment is vital to a great working relationship.

The work I do is narrowly focused and isn't for everybody. I want to and should work with clients that value my approach and are ready for it. I stopped chasing money and started looking for people I can help and want me to help the way I provide value. If you like fast, sustainable results, I'm your guy!

FOUR: Experiment, experiment, and experiment some more.

I have tried writing (a book, no less), podcast interviews, speaking engagements, paid advertising, and many other things. I always learn from those experiences and know there are many more in my future. I am pretty sure that I won't write another book (never say never), but I'm glad I did. If it helps just one person, it was worth it. And I learned I can do it!

FIVE: Pay close attention, or you might miss an important opportunity.

It's easy to gloss over the last "like" on a post and just chalk it up to someone just being kind. But that person might need my help, so reaching out to someone who is engaging with my content is never a bad idea. In fact, one time it led to a meaningful business relationship. I don't follow up on every post engagement, but I definitely should!

I read that most businesses fail in the first five years, and I can believe it. Having your own business is challenging work and it's not for the faint of heart. Luckily, I have an incredible and supportive family and network. I thank you all for giving me the opportunity to serve you and look forward to many more years of doing so.

Never Give Up – How we almost lost 4 team members

In June 2019, Process Improvement Partners was asked to help a leading consumer brands company execute its first Kaizen event in the history of its New Jersey factory. I came to the factory for a site assessment and determined there were many good candidates for their first Kaizen. After further discussions, we identified the first area for Kaizen.

Working with the continuous improvement manager, plant manager, and corporate support, we chartered an event focused on improving the reliability of one of their critical processing areas. We felt it held great opportunity, and positive results in this area would be very visible and help build momentum for the continuous improvement transformation being sought for the plant.

I always ask four key questions when chartering events:

1.       What’s the problem you want to solve?

2.       What are the measurable objectives of the Kaizen?

3.       Who are the team members you believe will be invested in the problem enough to help you solve it?

4.       Who owns the output when the Kaizen is over?

The leadership team thoughtfully answered these four questions and we immediately designed the Kaizen event based on the charter. I advised that as this was their first Kaizen event, most people in the plant wouldn’t have much experience with continuous improvement. Therefore, communication of the event and to the team would be critical. They assured me they would take extra care in communicating to the plant and to the team.

The Kaizen kicked off in mid-July.  I took extra time to train the 13-person team on Lean principles. After training, we took a walk out into the process to see the current situation and identify opportunities to improve conditions in the area Each team member took sticky notes and pens with them and were instructed to write one idea per sticky note for review after our tour.

We spent more than two hours in the process and team members were writing feverishly, as they were seeing things in a new way and uncovering many issues and wastes associated with the process. As a facilitator, I am always pleased to see team members identifying things as waste they had put up with in their normal job. When we came back to the meeting room, all team members except for one had written ideas on their sticky notes. While this isn’t unheard of, it is a signal something is wrong and needs to be dealt with. In total, the team had written more than 130 ideas for review and prioritization. This story isn’t about those ideas, it’s about each of the four team members who had difficulty in their first Kaizen. The names have all been changed for their privacy

The Story of Roy

Roy’s story is the first one because he didn’t write anything down while out in the process. When we came back into the meeting room, the team shared their ideas one at a time and they were posted on a flipchart. Since Roy hadn’t written anything down, I gave him opportunity to write ideas while others were sharing theirs. He still didn’t write anything, so I gave him the opportunity to contribute in a different way. He was asked to post the flip charts of ideas on the wall as they were filled. He seemed content to do this, and he also appeared to be listening to everyone’s ideas.

After all of the ideas were shared, they were prioritized by the team. Everyone got five votes and picked the things they thought would provide the greatest benefit to the people and the process. Roy voted and, in the end, there were three top projects picked. Following the vote, each team member picked the project they personally wanted to work on, and Roy put his name on one of the projects. Following this, the team was broken into sub-teams of 4 or 5 people.  The sub-teams started to work on and conceptualize their solution before the end of the first day. Everything seemed okay with Roy at that point.

On the morning of the second day, Roy wasn’t there when the team reconvened. No one knew where he was. They thought he was in the plant, however. Once the sub-teams got started on their projects, I went to find Roy. It turns out he had gone back to his normal job, thinking it was more important to the plant than the Kaizen event. I spent time explaining how critical his input was to the Kaizen and convinced him to rejoin the team. Once there, he stayed with them for the rest of the week. It turns out that he was in an area that was unfamiliar to him and didn’t realize that his input and perspective were important and valued. At the report out, he was one of the tour guides who proudly showed off the efforts of the team. Other team members remarked they didn’t think Roy would be a presenter, based on the initial issues during the Kaizen week and his quiet nature. Roy shined and everyone was extremely happy for his contributions to the team.

The Story of Hal

Hal is a mechanical supervisor at the New Jersey plant and was picked for the team based on his extensive knowledge, team focus, and ability to get things done in short order. He seemed like a perfect team member for the first Kaizen. On the first day, he had many ideas to share to improve the situation in the process. When the team prioritized their work, however, he seemed unhappy with one of the projects that rose to the top. This project got five out of 13 votes and centered on the air flow in a working space. Although it wasn’t directly associated with the charter objectives, it generated a lot of interest from the production operators who said it impacted their productivity, safety, and the ability to get their work done in an error-free way, which was one of the charter objectives.

At the end of the first day, it became apparent that the production operators couldn’t solve this problem themselves and needed help from Hal, who had the ability to get the air handling system checked out. Hal didn’t agree this was important and worth his time, but was pushed by the team to at least find out if the system could be fixed. At the end of the day, when the team was adjourning, Hal grudgingly got up from the room and said he would have it assessed before the next day. The team thanked him.

On the morning of the second day, the team was asked to reflect individually on their first day of the first Kaizen in the plant’s history. When it was Hal’s turn, he told us he had nothing to say and everything was okay. It was obvious he didn’t really feel that way. When pushed to say more, he put his two thumbs up, but that’s not what a team needed to hear. So, he was pushed a bit more, and the flood gates opened up. He told the team he thought they were working on the wrong thing and that he didn’t sign up for this event, he was “volun-told” to attend. He thought the team should be working on things they could control and not finger pointing at mechanical issues. After he said his piece, the team thanked him for speaking up and helping them refocus on the things that they could improve during the week.

As the week wore on, Hal was visibly happier and more engaged and by the end of the week, he was extremely proud of all the work the team was able to accomplish. He even mentioned he was happy he had decided to speak up at the beginning of day 2 to get everyone back on track.

The Story of Ed

Ed’s story is one of someone who is unfamiliar with the ebb and flow of a Kaizen. On day one, the team is learning how to be a team and picking simple things to work on. On day 2, after getting through the first projects, the team typically takes on harder work and is getting more into the true issues that hold them back from winning. On day 3, breakthroughs are made. Ed wasn’t willing to wait that long. Early on day 2, Ed came to me and said the team was working on the wrong things. He wanted me to tell the team this. Any good facilitator knows the team must own their solutions and should not try to redirect their efforts, unless there is a safety, policy, or rule violation. After discussing this for a while, I suggested that Ed make his pitch to the team to see if he could influence their decision.

Ed decided that he had enough of the conversation and didn’t want to try to influence the team. He still didn’t think they were working on the right things, but agreed to support them and see what was going to happen. About an hour after the conversation, I went to the production floor to see how things were going. Ed seemed very pleased with the progress of his sub-team and the earlier conversation seemed to be behind him.

On the third day, Ed didn’t show up to the plant. He had called out and I was concerned that he was still bothered by the work the team was doing. I didn’t know if he would make it for the fourth and final day, but he did. He was so impressed by the work of the team that he volunteered to present some of the findings to the leadership team. During his presentation, you could hear and feel his pride in the accomplishments of the team. Following the presentation, I had a chance to follow up with Ed, and he was apologetic for his earlier behavior and now was a believer in Kaizen and the power of teamwork.

The Story of James

James story was the most surprising to me, as he seemed aligned with the efforts of the team throughout the week. On the morning of the third day, James arrived ten minutes before the day’s kickoff and told the team leader and me he didn’t want to be on the team anymore. He felt he hadn’t been communicated with properly prior to the event, was forced to attend, and didn’t agree with any of the team’s efforts. Although he had been relatively quiet earlier in the week, he was participating and contributing ideas and efforts up until this revelation. He told us we weren’t listening to his issues and were working on the wrong things. We tried to reason with him and describe how things work in a Kaizen, but he was steadfast in his objections.

When he said, “I don’t want to be here,” we knew that we shouldn’t press the issue any longer. We thanked him for his contribution, told him we were sorry to see him go, and hoped that the efforts of the team would benefit him in his job at the plant. And then, he left to go back to his normal job.

I decided it was time to have a discussion with the plant manager, let’s call her Sue, and talk about these four team members and how things got the way they did. Sue was shocked to hear all four had different reasons to want to quit the team. From her observations, she thought we were heading in the right direction but was also concerned we wouldn’t make the typical Kaizen breakthroughs she had heard about and read about. This was her first Kaizen experience, and she was willing to let the week play out, based on my advice.

Sue was extremely surprised about James and wanted to try to convince him to return. Although I wasn’t sure if this was a good idea, Sue was the plant manager and had every right to try. Just about an hour later, James returned to the team who welcomed him back with kind words and handshakes.

The team leader decided to take James and some of the other team members down to the factory floor and let them show him their issues. He made a commitment to write work orders for any issue that couldn’t be resolved during the Kaizen.

When the afternoon of the third day arrived, James seemed extremely pleased his voice was being heard. Many work orders were written, and some work had already been completed, much to James’ satisfaction and the satisfaction of other team members.

By the fourth and final day, James was complimenting all of us around our support of him and the rest of the team. Although he didn’t present at the end of the Kaizen, he shared positive feedback to all that asked him about his experience.

After the presentation ended, I held a wrap up meeting with plant leadership. We covered many topics, most notably the things we could do to improve the experience for the next Kaizen team members. Now that the plant had a Kaizen experience, they could explain what would happen during the week. They also vowed to be more visible in their preparations and have one on one conversations with all potential team members, allowing them to ask any questions or raise any personal issues they might have.

This Kaizen week was one of the more exhausting ones for me, as I had to focus my energies on the people more than usual. The results and experience of the team members made it all worthwhile.

Don’t Shortcut the Process if You Want Results

Process Improvement Partners was asked to develop and deliver a global cost reduction ideation session for a leading consumer products manufacturer. In early phone conversations with the client, we discovered that prior attempts at this effort had less than desirable results. The next logical step was to visit the client and discuss the approach for the session.

The company wanted to develop a number of cost reduction concepts to be implemented in the current and following years. In past sessions, teams brainstormed cost reduction ideas and then handed them to project teams who were to turn those ideas into reality. Many ideas weren’t fully detailed, and the project teams became frustrated as they tried to understand the meaning of the ideas.

In order to get the proper amount of detail for the ideas, we suggested a two-day session. The client anticipated a half- day session, and his sponsors were only willing to commit that amount of time. It was clear we’d have to be prepared to make our case before requesting more time from the sponsor.

Our principle for an effective cost reduction session is that there should be no risk to safety, customer service, or productivity resulting from the ideas generated and implemented. To accomplish this, the team must understand what is most important to the customer, the employees, and the overall marketplace. During our sessions, the team receives Voice of the Customer, operational, and business information as the basis for their work. Then, the team is exposed to other ways of thinking around their current processes. Brainstorming and prioritization come next, and the highest priority ideas are developed into detailed concepts with logical thinking and financial calculations applied to them.

Once the team enters into the concept development phase, they continue to work until time runs out in the session, working from the highest priority/highest value projects to the lowest priority/lowest value projects. Most teams need two days to get enough projects detailed to meet the desired session objectives.

Once this approach was reviewed with the team leader, he agreed two full days were needed for the session. Now, we had to convince his sponsors to commit to a two-day session.

Fortunately, there was a leadership team meeting later that morning, and the team leader was able to get a 30-minute agenda commitment from them. The team leader introduced me to the leadership team and told them I would be describing the process for the session and asking for a two-day commitment.

This opening statement got the room buzzing. They didn’t feel like they needed two full days as they hadn’t had to do this in past sessions. One of the members of the leadership team commented that prior efforts hadn’t been successful, so maybe they should listen and consider a different approach.

This was my opportunity to talk about prior cost reduction sessions and the results they were able to achieve. I emphasized that the key to these sessions was to provide concepts to project teams that had the right amount of detail and logic, so the teams would have a solid foundation from which to build on. I explained that rushing through these sessions wouldn’t allow the teams to think through the logic and provide the necessary detail.

This got their attention, but they were still skeptical. They were willing to allow one day (a half-day increase from their prior commitment), but this still wouldn’t be enough. Knowing that these sessions were designed to save companies millions of dollars, I asked if they thought two days was reasonable for such a high return on their investment. One of the leadership team members asked, “Why wouldn’t we set a savings target and lock the team in a room until they reached this target?” I explained the team would be less likely to provide quality effort and more likely try to hit this target with “false” savings, in an effort to go home that evening. He seemed satisfied with my answer.

The leadership team members began challenging each other’s thinking and relived many failed attempts at cost reduction. I knew we were getting somewhere, but hadn’t yet gotten agreement to proceed with a two-day session. Finally, the Director of Finance looked at me and said, “What are you going to do that’s different from what we’ve been doing all of these years?” This was my chance. I fired right back, “I don’t really know what you’ve done in the past, but I can tell you what I would do.” From there, I described the full two-day process that had worked for dozens of teams over the years. The team leader supported me during this discussion and by the end of the review, the leadership team agreed on the approach. The Director of Finance even said, “Don’t be so cheap. Let’s give the team two full days for this important effort.”

This was the alignment and agreement we needed. We thanked the leadership team for their support and time and excused ourselves from the meeting.

A month later, we ran our first cost reduction session and the team beat their savings target by more than $10 million. Two more sessions were held in 2018 with similar results. These sessions will now be held annually, following this approach, with a two-day commitment every time.

Speaking Up Takes Courage

In 2011, I was asked to assist a team in Pensacola, Florida who wanted to improve processes in their distribution center. We were given four days to accomplish our task – reduce shipping damage by 50%. This was a tall order, but the team was up for the challenge.

After a half-day of training on Lean tools and techniques, the team took a walk in the distribution center and supplying processes and identified many ideas they thought would improve the situation for everyone who worked there.

All of the ideas were shared and the team prioritized the ideas they wanted to implement first. Breaking the team into smaller sub-teams, we picked the top three projects to work on. Each sub-team developed their solutions and began to implement them. At times during the day, we would come back as a full team and review each sub-team’s progress. Things were getting done, but it wasn’t clear that any of the projects would significantly reduce shipping damage.

On the morning of the third day, I asked the team if they had any feedback or ideas to help us make better progress against our goals. The room was silent. One of the team members, let’s call her Ruth, had an uncomfortable look on her face. I didn’t want to put her on the spot, so I asked each team member, one at a time, to give one suggestion they thought would make the day better for everyone. Most people said things like, “Let’s work better as a team,” or “We should try to get more done.”

When I got to Ruth, she blurted out, “I don’t think we’re working on the right things.” This took me by surprise. I wanted to know more. She then explained we weren’t focusing on the root cause of the shipping damage. She thought we were just working on things that were easy to implement, not directly impacting the causes of shipping damage.

I felt a sense of panic – we were in the third day and would be reporting our results at the end of the fourth day. There was little time to spare, but we had to resolve this issue or else we would fail. We were a team and the members started to share their thoughts with Ruth about the problem we were trying to solve. They realized Ruth was right. We were avoiding the real issues causing shipping damage. We brainstormed again and prioritized efforts based on the right things to do, not the easiest things to do. Relief started to wash over me as I realized the team was determined not to fail.

Once we finished prioritization, the team split into four sub-teams. Each sub-team had a sense of urgency and purpose and worked on their projects with energy and a “refuse to lose” spirit. If they had a question, or got stuck, they went to find help. Nothing got in their way. Almost all team members stayed late and everyone agreed to come in two hours early the next day to ensure their work would be done.

We decided to abandon the standard Power Point presentation of our findings and changes and worked right up to the time of the report out. When the leadership team came to see what we had done, we gave a tour of the changes we implemented to reduce shipping damage. They were impressed and believed we had accomplished our goal of 50% reduction.

I learned a valuable lesson from Ruth, and it’s one I share with all of the teams I work with. Understand the problem you are trying to solve. Once understood, focus on the thing(s) that will solve the problem, no matter how difficult they may seem. If you’re veering off course, have the courage of your conviction to steer people back on course. Never be afraid to speak up.

I now give all of my teams many opportunities to speak up and share their concerns. I also do it as soon as possible in every Kaizen event I lead or facilitate. It’s better to change course than end up in the wrong destination. Thanks to Ruth for being brave enough to steer us back on course.

The Team Has More Power Than It Thinks

A leading consumer products company shipped millions of boxes of goods weekly. Most of the time, large quantities of the same products were shipped on a wooden pallet, and loaded on a truck. The distribution center employees were used to picking full pallets of products out of racks, placing one label on the entire pallet, and then, placing the pallet of goods on a truck.  In recent years, Amazon entered into an agreement with the company, and turned their efforts upside down.

Amazon ships any quantity of products, be it one box, or a truckload of boxes to customers. Their customers expect to get the right product quickly and properly labeled. The consumer goods company would now have to label every single box shipped to an Amazon distribution center or an Amazon customer. They would also have to do it more quickly than they had to for any of their other customers.

In the years leading up to and including 2018, Amazon business exploded for the company, much like many others around the world. The company added staff to ship all of the products required, but they weren’t meeting Amazon’s strict delivery requirements and were starting to lose money on the relationship. At this point, they called in Process Improvement Partners to help them solve their problem.

We walked through the existing process together to see what opportunities might present themselves and if a Kaizen event could help solve the problem facing them – develop a system that would meet the growing Amazon business and delivery requirements and do it safely, productively, and profitably. It turns out they were applying their large volume/low product diversity approach to the small volume/high product diversity Amazon orders. We also found out they didn’t always receive Amazon orders in a timely or predictable fashion from their corporate customer order systems, so it caused them to staff the distribution center in ways that made people wait for orders to pick and ship.

We designed a 3-day Kaizen to get them back into compliance and decided to set an aggressive set of goals: 25% productivity increase, 50% cycle time reduction, and 50% reduction in fines relating to late deliveries to Amazon.

In a Kaizen, you should pick team members who will help you solve the problem and want to win. In this case, we picked employees from the distribution center and corporate team members who could provide perspective on the issue and could also initiate identified system changes. We advised all team members this Kaizen was critical to the success of the company and we expected full participation from each one of them during their time together. The team leader made a compelling case and received commitment from all team members.

On Day 1, after team introductions, the team leader explained the problem from his point of view. He thanked everyone for coming and asked them to keep an open mind and be willing to challenge their thinking during the Kaizen. Then, the Amazon customer service manager from corporate presented “Voice of the Customer” information to the team. This was an engaging discussion, and the entire team felt an urgency and need for change and improvement. Following these discussions, we took the team out on a process walk.

We started out in the office, looking at a computer work station. When we asked what was happening at the work station, a team member explained they were waiting for orders to arrive from the corporate system.  Until orders arrived, she was stuck and couldn’t provide any assignments for the distribution center employees. We asked her the reason and she explained the orders must have been received by the corporate system after 6 pm. Orders from Amazon were manually entered, and after 6 pm they wouldn’t be entered into the system because everyone had gone home for the day. Orders would wait until at least 8 am the next day to be entered, and by the time they were, the distribution center wouldn’t see them until 10 am or later. The distribution center employees work around the clock. This was a big opportunity for improvement.

We walked around the facility next, looking at the physical and other system issues in the way of safety and productivity for the distribution center. The team members took many notes and after 2 hours, we returned to the meeting room to review what we observed.

After sharing all of the issues as a team, we mapped out the existing process on a wall with sticky notes to identify the biggest pain points and opportunities. There were many issues and we wanted to make sure we would be working on things that would make the biggest impact and also were within the control of the team. We made quick estimates of the time it took to complete each step, including the minimum and maximum times. The idea was to work on the steps that took the longest time, as streamlining them would maximize the customer service improvement.

We identified some steps that could take more than 8 hours and up to 24 hours or more. Those were the steps to work on. The team prioritized those steps and came up with ideas to reduce the time. They avoided the step called, “Wait for orders from corporate”. This step was identified to take anywhere from 1 1/2 hours to 24 hours, so it would be extremely impactful if improved.

I challenged the team to consider improvements to the step. They didn’t feel like they could make any changes without proper approvals. I reminded them they were empowered by the simple fact they were the Kaizen team chosen to solve this critical business problem. If they didn’t feel they could unilaterally make changes, they should “phone a friend” who could approve their changes immediately. One of the team members, I’ll call her Ruth, left the room to make a phone call to the person who could approve the changes. After a few minutes, she came back to the room and informed the team the person she tried to call was out sick and she would try again tomorrow.

I knew we didn’t have time to wait, so I asked Ruth if she was willing to call that person’s manager or go to the person’s house, knock on his door, and gain his approval. She thought I was joking about going to his house (I really wasn’t), and decided to call the next level manager. She wasn’t available either. Finally, she called the Vice President of Logistics and Distribution.  After explaining what was going on and the approval she was looking for, she was informed that another team member, let’s call her Alice, had the authority to make the decision.  Ruth came back into the room, met with Alice, and secured approval for the change.

It turns out the change was so simple it could be executed by a few lines of programming allowing any orders coming in after 6 pm to be manipulated automatically and delivered to the distribution center immediately. This option was already being used for other critical customers. Adding Amazon to the list took no more than 10 minutes of effort. The team was so motivated by their win, they found many other quick improvements and letting nothing stand in their way, met or beat all of the objectives for the Kaizen.  They described how the only thing that was getting their way to improvement was their own way of thinking. Once they realized they were empowered, there was nothing standing in their way of victory.

Top 5 Continuous Improvement Books

I have read many books on Lean, Six Sigma, and other Continuous Improvement methods over the years. Some inspired me, some frustrated me, and all made me think. The following 5 (and two honorable mentions) are my all-time favorites.

Number 5: The Toyota Way – Jeffrey Liker

This is an easy read and talks about the principles behind the Toyota Production System.  It is the first book that I recommend to anyone who wants to know what “Lean” is.

Number 4: The Goal – Eliyahu Goldratt

All about the Theory of Constraints, this book reads like a novel. I wanted to see if they save the factory and live happily ever after. There’s a great story in it about a camping trip that really brings manufacturing issues to life. I have shared this book with others to give them insight into the world of manufacturing.

Number 3: Key Strategies for Plant Improvement – Shigeo Shingo

Written by the all-time greatest Industrial Engineer (my opinion, of course), this book provides quick ideas and ways of thinking that opened my eyes to possibilities. Many of the ideas can be implemented immediately, without any investment.  

Number 2: A Revolution in Manufacturing:  The SMED System – Shigeo Shingo

The first continuous improvement book I ever read. It probably influenced me more than any other. I was able to immediately implement SMED in the little factory I worked in and saw amazing results. I found it on the bookshelf of another supervisor, who gave it to me without reading it! There’s a great explanation of how Shingo’s feet blistered while playing golf and how it led him to a breakthrough in changeover reduction.

Number 1: Toyota Production System – Taiichi Ohno

Written by the man who was essentially responsible for Toyota’s vast success over many decades. This book explains what Toyota did, why they did it, and the results they were able to achieve. All the other “Lean” books just interpret what Ohno did and why he did it. He didn’t want to write a book, but thank goodness he did!

Honorable mention 1: The Innovator’s Dilemma – Clayton Christiansen

This book explains the impact of disruptive technologies on the world. It not only gives many case studies, but also explains what companies should do to become disruptive in their industries.

Honorable mention 2: Today and Tomorrow – Henry Ford          

Written almost 100 years ago, the very elements of Lean are described by the man who put a car in everyone’s driveway. Taiichi Ohno was inspired by Henry Ford and so was I.

PIP Visits Dogfish Head Brewery

One of the benefits of being in business for yourself is to decide what’s most important to you and then prioritize your time to let you do what you are most passionate about.

Recently, I had the opportunity to visit with Gordon Zavilla. Gordon and I worked together at Armstrong a few years ago and he was interested in accelerating Dogfish Head Brewery’s continuous improvement journey. Gordon invited his boss, Brian Hollinger to join us during the visit. We took a walk of the processes and shared ideas of ways to immediately improve safety, productivity, and customer service. We also discussed a strategic approach to the improvements they want to make. Their culture of employee engagement and creativity is a great foundation from which to build on.

One of the most creative tool boards I have seen was in their maintenance shop. Notice how there are actually three boards in one. No searching for anything in traditional tool boxes.

Thanks to Gordon and the great folks at Dogfish Head who taught me what it means to be “Dogfishy”.

PIP Helps Team in York, PA Improve Reliability of Critical Operation

Many consultants train and teach. I like to demonstrate and verify with teams that they truly understand the techniques for improvement that I am sharing with them. Most importantly, I want them to be able to take this work and transfer it to other parts of the factory without my assistance.

During an event in York, PA, I showed a team of maintenance technicians, engineers, and production operators how to level, square, and centerline equipment during a reliability improvement Kaizen. I demonstrated these techniques to show them how critical even the smallest improvements are. We were able to reduce the out-of-level condition on some conveyers from ½” to less than 1/16”. We also optimized the location of the product that was flowing through the conveyers and equipment. Immediately after doing this work, the production line ran smoother than anyone could remember.

When the team reported their results and findings, the audience was so impressed that they committed to doing this work all over the facility, using their new reliability experts.

What Happens in a Cost Reduction Session?

Most companies want to reduce costs in their operations. There are many ways to do this. Some companies choose to reduce their workforce, others decide to sell off under performing businesses. Companies that use this approach are just avoiding the problems and inefficiencies of their business practices and are not targeting the root cause of their problems.

At Process Improvement Partners LLC, we believe that the best way to reduce cost is to optimize your business to the benefit of your customers. Using that premise, we have developed an approach to leverage your team’s creativity to drive waste and inefficiencies out of your process, thereby reducing cost. In a 2 to 4-day session, teams will identify and build plans to take millions of dollars out of their operating costs, often greatly exceeding their cost reduction targets. The following summarizes how this can be accomplished.

Create Leadership Alignment

The first step in the process is to meet with Operations Leadership to gain their alignment and support for the approach that is being recommended. They have to stand by it, show their support for it, and supply dedicated resources that will participate fully in the cost reduction session(s). They should communicate with all potential participants and their managers well in advance, showing their support for the effort.

Event Preparation

Once Leadership is aligned, the event is scoped out, with a clear problem statement and objectives. When the scope of the event is known, we then plan the amount of time necessary for the team to achieve their cost reduction goal. Critical team members are identified who can help meet the goal, and then the event can be scheduled. All facilities should be reserved well in advance of the event, as meeting rooms come at a premium in most companies. There should be adequate space to move around and enough wall space to display information and ideas on. Typical supplies include flip chart easels, flip chart paper, sticky notes, pens, and a way to project presentations and information.

Session Kickoff

On the first morning of the session, an executive sponsor or key member of the leadership team kicks off the session, reinforcing the importance of the session and the targeted cost reduction that is to be realized. The sponsor should encourage team members to be as creative as possible and not limited by what has or has not worked in the past. It is not unusual for team members to be skeptical that their efforts will not be implemented, so the sponsor should meet that skepticism head on.

Voice of the Customer

Those who will be impacted by any cost reduction efforts must share what is most important to them and their customers. Often, Marketing will represent the customer’s interests, but other areas can do this as well, such as Operations, Research and Development, Sales, and Distribution. Some companies will bring in direct customers and this can be quite powerful. In the end, the team cannot and should not implement any cost reduction ideas that will negatively impact the customer. But, in some sessions that Process Improvement Partners has facilitated, cost reduction ideas created a positive customer experience.

Ideation

This is a free-wheeling exercise. In the early stages of ideation, it is more important to get as many ideas out as possible, regardless of their likelihood of success. Many team members will come to the session with ideas to share, so let’s get them all out on the table. When the team starts running out of ideas to share, facilitators will suggest topics and ask questions to encourage more ideas from the group.

Prioritization

Now that all of the ideas have been shared, the team needs to prioritize the ones that will make the most positive impact on cost, without negatively impacting the customer. There are many ways to do this, but we have used these in most sessions: Group rotation and review of all ideas, grouping of similar ideas, multi-voting with criteria, and a 9-block Impact/Difficulty matrix. The goal is to take literally hundreds of potential cost reduction opportunities and narrow them down to 20 to 30 of the best ones for the team to work on.

Concept Shaping

The team is divided into small groups of 3 or 4 people and asked to build more detail on the top priority cost reduction ideas. A focused, one-page concept sheet template is given to all team members, and they are required to answer all of the questions to the best of their ability. There isn’t a lot of time available, so team members are told that they should take one hour per concept. If they need additional information, they may phone a friend, or make their best educated guess. In all cases, they are encouraged to list their assumptions, so that others will understand their thought process. All concepts are audited for completeness and listing of assumptions, with the view that others who may not have been in the room may be assigned the project later on and must understand the initial thinking behind the cost reduction idea.

Managing System Development

Some teams work on the way that they will manage the cost reduction efforts after the session is over. This can include project communication, resource assignment, project visualization and management, and regular meetings to review status. Other teams just hand off their efforts to the session leader to take the work forward. In all cases, the results of the session should be communicated back to the sponsor and other stakeholders.

Reducing costs in your operation doesn’t have to be difficult or painful. When using people’s creativity and engagement and focusing on ideas that will benefit the customer, opportunities become apparent and a path to realize those opportunities can be identified. Then, everybody wins.

Who is Your Customer?

We are all customers. We want what we want, when we want it, at the level of quality we expect, in the proper quantity. We are the final say as to whether a business will thrive, survive, flounder, or die. The business must deliver to our expectations, or we will not continue to purchase products or services that they offer. 

It’s surprising how many businesses wrongly believe shareholders are their customer, rather than those who actually derive benefit from what they offer.

A key principle of Lean is that everything should be optimized to the benefit of the customer, and anything that doesn’t deliver value is considered waste and should be eliminated. 

It is therefore critical that you understand who your customer is, what is most important to them, and what they perceive as value.  

Identify Your Customer

Questions to consider to identify your customer(s):

1. Do they pay for your product or service?

2. Do they provide feedback about your product or service, and how it affects them directly?

3. Do your actions directly influence their behaviors?

4. Do they depend on you for the product or service that you deliver?

Sometimes, we need to look internally to identify our customer(s). For example, in a manufacturing plant, one department receives a product from another department. The receiving department is the customer of the delivering department, and requires the product to be the proper quantity, quality, and to arrive on schedule. Anything that deviates from this is waste and should be eliminated.

Likewise, the workers in the same manufacturing plant are the customers of the Leadership Team, who makes decisions on their behalf. Their families are also customers as strong business decisions keep paychecks rolling in.

What is Most Important to Your Customer

Once you have identified your customer(s), you then need to understand what they truly want from you or another provider. To find out, you can analyze market trends, speak to your Sales and Marketing departments, host focus groups, and/or go directly to your customers and find out. Oftentimes, customers may not be able to directly identify everything that they want, but with the proper questions, you should be able to get the heart of their issues. Consider these questions:

1. What do you like about the product or service that we provide?

2. What don’t you like about the product or service that we provide?

3. What issue or need are you trying to solve with the product or service that we provide?

4. What are we not providing that you wish we would provide?

5. What changes would you make to our product or service that would make things better for you?

6. What do you wish you could say to our CEO about the product or service that we provide?

It’s surprising how effective face to face communication can be with customers. It’s also surprising how few of us use this method to extract critical information from them. Most people appreciate the opportunity to have these conversations. Now let’s talk about value.

A Question of Value

If you have identified your customer and reviewed what’s most important to them, you should be close to answer how they define value. Value isn’t necessarily a monetary thing, but can be thought of as something that enhances the customer experience. Some examples include:

1. Reduces time and/or effort

2. Simplifies a task

3. Enhances quality of life

4. Makes them happy

5. Keeps them safe and secure

6. And the list goes on

Once you have identified your customer, what is most important to them, and how they define value, you are ready to attack and eliminate waste in your business. To understand more about waste, read the blog entitled, “The Eight Deadly Wastes.”

Use Standardized Work to Unleash Creativity

Most people don’t like being told what to do. They definitely don’t want to be told how to do it. But, with proper standardized work, we can show people the right way to do things and free their minds to work on more complex problems that they face. The key is to develop standardized work that engages people, speaks to them at the appropriate level, and captures the routine aspects of a task in a way that ensures everyone follows it properly and easily. Once that occurs, they can concentrate on solving problems that aren’t covered by the standardized work.

When I was very young, I was told, “Don’t touch the stove top. It’s hot!” Naturally, that sparked my curiosity. I wanted to know how hot, so I had to touch it. Unfortunately, I got burned and learned a lesson. I should have asked “How hot?” or, “What happens if I touch it?” If I understood what and why and the implications, I may not have received a boo-boo. This was a valuable personal lesson, but it also provides a good structure for standardized work. Now that I didn’t have to touch the stove anymore, I was freed up to use my creativity to create other mischief.

How to Engage Your People to Develop Standardized Work

People tend to do things the way they are taught, the way they observe, or the way that feels right to them. Unfortunately, they may be doing things improperly, unsafely, or inefficiently. So, it is incumbent on you to help them see the better way to do their work. The best way is to engage them in the development of the work. I have found that you should engage at least three people who are currently doing the work so they can share experiences, approaches, and break the tie, if a final decision on how to proceed is needed. You should set the expectations that work must be accomplished safely and productively, but give them the freedom to use their experiences to guide them in the process.

What To Do

The first part of standardized work is to define what to do and the order in which the work must be done. Once you have engaged people who do the work to participate in this effort, have each one of them demonstrate their approach to the work. Those who are watching should provide feedback and ideas that would make the work safer and more efficient. Once all ideas are shared, help bring the group to consensus around the final procedure. Once they have done this, they should practice the new procedure and see if they have missed any vital elements. Following that, document the procedures with pictures, videos, and/or written process steps. The more visual the better, as you want to be able to explain the procedure to anyone in a short amount of time, and you want them to be able to demonstrate their understanding without much effort. Once they have reached consensus, you must gain agreement that the procedure will be followed the same way by everyone who does the work. 

Why To Do It

You can’t guarantee people will follow the new procedure, just because it is safer and more efficient. They may not realize this is the case. Most people are willing to try something different than what they are used to if they understand why it will be a benefit to them. Therefore, the group that develops the new procedure should incorporate the “why” or benefits behind the steps in the new procedure. If they’re unable to do so, it probably means there aren’t real benefits and the procedure needs improvement. Keep working and improving the procedure until you have something that delivers a benefit. Once you have done that, it will be easier to sell the new procedure to others.

The Implications of the Work

The best standardized work results in safety and efficiency gains. These should be clear and measurable. After all, how do you know you’re winning if you’re not keeping score. So, the team should be able to identify and incorporate clear measures of the standardized work. For example, the procedure now takes six steps and 30 minutes, while in the past it took 12 steps and 48 minutes. Another example is the new procedure results in a higher yield rate than the old procedure. It is not uncommon to reduce the time required to accomplish a task by 30% to 50%, just by gaining alignment and simplifying process steps.

Using these three elements – what to do, why to do it, and the implications of the work should convince people to try this new way of operating. Once they are convinced, they should also see that by following this new process, their minds are freed-up to work on more complex problems, thus unleashing their creativity.  

Here’s a real-world example: A production line was shutting down erratically.  In the past, people would be blamed for not following procedures. With clear standardized work, the time to troubleshoot was reduced dramatically, as the human variables were eliminated. The team could focus on other reasons and quickly found the root cause of the problem, which was a switch that was shorting out.

We want people to be creative and improve things and solve complex problems. By creating clear standardized work that is consistently followed, we give people the opportunity to use their creative minds and drive positive results.

The 8 Deadly Wastes

The customer defines value for any product or service.  If they aren’t willing to pay for something, it has no value to them. In the terminology of Lean, anything that doesn’t directly provide value to the customer is called “waste”. Further, there are eight specific types of waste. Once you know what they are, you can begin to spot them, and then work diligently to reduce or eliminate them. If you do, the customer experience will be improved and so will your operating results.

These are the eight deadly wastes:

Transportation
The movement of anything from place to place is considered waste, because it adds no value to the product or service being provided. It only adds time, and the potential for loss or damage. It may seem necessary to move things around in a process – putting things in trucks, putting things away on shelves, sending electronic data from one server to the next, but there is no change to the form or function of the thing being produced. The question to ask is, “how can we reduce or eliminate transportation in the process?”

Inventory
Ideally, the only product you should produce is the product that your customer wants; no more, no less.  More production creates inventory. Less production creates a shortage. The risk of having too much inventory is that it may spoil, become obsolete, or never leave the shelf. Think about computer chips. Once the new version of computer chip comes out, who is buying the older version? Typically, nobody, or if they do, they are receiving a sizable discount.  Another problem with inventory is that the thing you need may get lost behind the thing you don’t need. So, you end up producing more inventory that can hide the next thing, and the cycle continues.

Motion
This waste addresses the effort required to complete a task. If you must reach over your head, or grab something from the ground, you are using extra motion. If you must go away from your area to track something down and retrieve something, you are using extra motion. Ergonomics, which is the study of people’s efficiency in their work environment, is a method to identify and reduce excess motion.

Waiting
Time lost while waiting for an answer, a return email, an earlier process step, booting up your computer, or general waiting around is considered waste. It can be frustrating, time consuming and adds to the overall time in the process, which delays delivery to the customer. The key is to find the things that force you to wait and strive to eliminate them. Empowering people to make decisions is a quick way to drive waiting time down.

Overproduction
Have you ever noticed people who print out every email that they receive? This is an example of overproduction. How about a production line that is running really well and the managers want to keep things running? While the current product gets produced, the next product waits. There is a risk there will be a shortage of the raw materials to make the next product, or that there will be a delay in shipping the next product to the customer.

Overprocessing
This waste refers to the complexity in the process. If there are more steps than needed, or if the product or service is delivering beyond the requirements of the customer, this can be thought of as overprocessing. In the 1930’s, there was a cartoonist named Rube Goldberg, who devised the most complex ways of completing simple tasks. It was entertaining and creative, but not the ideal way of accomplishing work.

Defects
When the product or service doesn’t deliver to the required level of quality, this is considered a defect. When something has to be reworked, this is considered a defect. Many companies try to instill a culture of “Doing it right the first time.” They want to ensure that each process step will continue adding value to the benefit of the customer.

Unused Employee Creativity
The people who do the work generally have ideas to make their work simpler and safer. The best companies listen to their employees to get improvement ideas. Other companies think they know all of the answers and ignore suggestions by their employees. We don’t want people to shut their minds off when they come through the door, or we will be responsible for the worst waste of all.

In order to reduce or eliminate waste, you must be able to identify it. These eight wastes are easy to find in any process, if you are willing to look. If you make it a habit to reduce or eliminate these wastes, your customers will benefit. If your customers benefit, so will you.

What Process Improvement Partners Can Do for Your Team

Process Improvement Partners LLC offers a variety of services that help teams achieve breakthrough results. Some are narrow in scope, while others are strategic in nature. Some are quite simple, and others are extremely complex. In all cases, we strive to apply the right service to our customer’s needs, providing hands-on assistance, where needed. Here is a summary of our services, and when you might want to consider using them:

Site Assessment
If you want to see what opportunities are available to you, or don’t know where to start, take this 5 to 6-hour test drive with us. Everyone learns something new in this session. Together, we will identify the highest value opportunities and develop the plan to realize those opportunities. Some teams decide to take on the work themselves, others choose to engage us. Either way, it’s time well spent.

Cost Reduction Ideation, Prioritization, and Implementation
If you need to drive out costs in your business without negatively impacting your customers, this session is for you. Team members are challenged to come up with new and more efficient ways to do what they do, focusing on the cost impact to the organization. Once they have heard from their customers, they creatively brainstorm cost reduction opportunities, prioritize those opportunities, and then more fully develop and analyze those opportunities for customer and cost impact. At the end of the session, the team has a roadmap to drive significant costs out of the business.

Strategic Planning (VSM)
The first step in any continuous improvement journey. This session opens the eyes of all participants to the wastes and inefficiencies in their current processes and provides a roadmap to improvement that will be a direct benefit to their customers. Often, the team identifies simple and quick changes (6 – 12 months) that will reduce lead time to their customers by more than 50%, free up space, reduce the need for inventory, and improve quality and safety performance. This session also changes how people manage and lead in their processes moving forward. The benefits are felt immediately by those who work in the process, as well as customers of the process.

Workplace Organization (5S)
This session makes an immediate, visible and measurable impact on safety and productivity in a work space. It’s fun and fast paced, as team members learn how removing clutter, organizing items into optimal locations, maintaining resources in top condition, and implementing audits of the area can improve the lives of the people working in the space. Team members may get emotional at the end of the session, as they are positively impacted by the experience.

Breakthrough Creativity (3P)
Based on the proven 11-step Nakao method, this session is designed to drive teams to places they never dreamed possible in a 4 ½ day session. It is extremely challenging and exciting, as team members find solutions to problems that eluded them previously. This session is not for the faint of heart, as team members will work at a rapid pace and for long hours. When the session is over, it’s not unusual to have reduced project time by 6 months or more.

Changeover Reduction (SMED)
If you find that you are constantly expediting orders due to long product changeover times, this is the session you need. Using Single Minute Exchange of Die (SMED) methodology, teams typically reduce changeover times by half or more by the end of the session. Your customers will see the benefits of this session too, as lead times will be reduced as well. Teams will be trained so that they can apply the approach to other areas of their business in the future.

Process Optimization (Standard Work)
This session brings people together to determine the safest, most productive way to accomplish critical tasks. The team is guided through this session to create the new standard work for the improved process and develop the managing systems to ensure that everyone follows it once implemented. 

Failure Prevention (FMEA)
An industry standard approach to stopping problems before they happen through the identification, prioritization, development, and implementation of preventative actions. This session stretches team member thinking as they are challenged to identify all of the ways a process could fail, whether the process has been implemented or not. Through a standard scoring system, these failure modes are prioritized for greatest negative impact to employees and customers. Once the session is over, the team will have a strong plan of action to keep these potential problems from occurring.

Plant Reliability Improvement (OEE)
This ongoing effort to drive to World Class Reliability utilizes Standard Work, Visual Management, Changeover Reduction, Shop Floor participation, Best Practice maintenance, and Continuous Improvement events. The team will build a road map of actions and strategies to improve Plant Reliability, and then they will be given assistance with any or all of their identified actions. We step back when the organization is ready to take full ownership of the improvement efforts.

Cultural Transformation
What does it take to drive an organization to a culture of continuous improvement? This ongoing effort utilizes leadership coaching, mentoring, demonstrations, and implementation of the key drivers of cultural transformation. The team starts with their vision and mission, and then designs all of their actions around them. Assistance is provided until the organization has shown that it owns the change that it seeks.

Visual Management and Shop Floor Participation (Gemba Walks)
The people who work in the process know what’s going on and are just waiting for an opportunity to share their ideas for improvement. This session engages the shop floor work force and improves accountability for daily results. The team builds a plan and leadership actions that will drive shop floor performance to higher levels and improve workforce engagement. Once the team implements visual management, there will be alignment and accountability for the most important results.

Best Practice Facilitation
How is that the best facilitators look like they aren’t doing anything at all, while the teams they are working with are making breakthroughs? This ½ day training session will provide the tools, methods, and hands-on practice to improve skills of the participants. The result will be more productive meetings and events.

If you don’t know which of these services to choose, just contact Process Improvement Partners LLC, and we’ll help you determine your best course of action. We are totally committed to your success. These sessions can drive your operating results to new heights.

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.

Why Request a Site Assessment?

When you call Process Improvement Partners LLC for a site assessment, you are making a choice to invite outside perspective for your organization. While there is a fee for this service, there is also a significant investment of your time and resources, so it is good to understand the value of your investment.

By the end of this 5 to 6-hour visit, you will have a greater understanding of where the highest value safety, quality, customer service, and cost opportunities are and how to leverage them. Here’s a typical site assessment agenda:

9:00 am - Team Introductions
A short review of each participant, their role, the company, and Process Improvement Partners LLC. We get to know one another and start the conversation on a personal and business level. It serves as a quick check of the team’s level of commitment, based on who is participating in the assessment and for how much time during the day.

9:15 am - Safety Review
How will we keep each other safe during the assessment? How important is safety to the site team and how strong is the safety culture of the company? During the visit, we will respect all of the safety requirements and expectations set by the team.

9:30 am - Review the Site Team Focus and Priorities
What are the priorities of the site team? What are the current pain points in their view?  What do they want to focus on during the assessment? These discussions keep everyone aligned around the purpose of the assessment and make it more meaningful for all involved.

10:00 am - Plant Walk (Gemba Walk)
We walk the process with the site team, visiting all areas, speaking with people in the process, and looking for waste and inefficiencies. The more engagement we have with people in the process, the better. When waste is spotted, we stop and discuss what we see as a team. All team members are encouraged to take notes, so that they document what they see while on the walk.

11:30 am – Review of Findings
What did we observe on the plant walk? What did we learn from those in the process? Does it validate or invalidate our initial thinking? Did we learn something new, just by the way we engaged with others on the walk? Might this be an approach to incorporate into the way we do business moving forward?

12:00 pm - Lunch
Keeping the team together during lunch is critical. Although this seems like a minor detail, it’s an opportunity to relax and discuss things in a less formal way. It also lets the team get a feel for how an ongoing relationship with Process Improvement Partners LLC might look. 

12:45 pm - Evaluate and Prioritize Opportunities
Based on everything we saw and discussed, what are the key things that the team wants to work on now and in the future? Using quick facilitation and prioritization techniques, the list of observations and ideas is narrowed to a top 5 to 10 that the team finds most important and impactful.

1:15 pm - Discuss Approaches to Leverage Top Priority Opportunities
We now discuss the tools and techniques available to drive improvement in the top priority opportunities. This is the time to decide whether the team wants to work on these opportunities without outside assistance, or with the help of Process Improvement Partners LLC. We will charter and write proposals for any work that the team feels it needs help with.

1:45 pm - Plan of Action
What are the next steps? Who is responsible? Does the team want Process Improvement Partners LLC to charter and write a proposal for the work? Is there a contact person for the work? We build an action plan that will be followed once the assessment is complete.

2:15 pm - Wrap Up and Feedback
An opportunity to review how the site assessment went for all participants. This is a learning moment for all involved, as we are applying process improvement in real time to the assessment process.

2:30 pm – Additional Time for Discussion or Adjourn
If the team wants more time to discuss the assessment, we always set aside additional time for them. If there is nothing left to discuss, the assessment is complete.

At the end of the site assessment, the team has a roadmap of activities that will help them improve their performance in safety, quality, customer service, and cost. In addition, they have had an opportunity to see how an ongoing relationship with Process Improvement Partners LLC can help them execute their roadmap.

How to Drive Teams to Success with Effective Facilitation

The best facilitators look like they’re doing nothing at all. The team is driving toward a solution, being creative, working together, and having fun. What’s the facilitator doing, just taking credit for the team’s hard work? As it turns out, the easier it looks, the harder it is. But, if you use these techniques, you have a chance to look like you’re doing nothing, and doing it really well!

1. Stick to the charter.
This is the reason the team got together in the first place. Make sure all activities are conducted within the scope of the charter. It’s very easy to get off-track, or work on things that aren’t explicitly in the charter. The team should be reminded and guided back to the charter.  An easy way to do this is to share a copy of the charter with every team member and have them read and discuss it at the appropriate time(s). They should be able to recognize if they are veering away from the charter.

2. The team solves the problem, the facilitator guides them to the solution.
Keep the roles separate, as the team will sometimes want the facilitator to give them the solution. This is not a good idea, as the team must own the solution and will not if they didn’t come up with it. The facilitator is responsible to come up with a solution path for the team, not the actual solution. There are times when a facilitator may have to provide direct help, but this should be rare, and only used as a last resort.

3. Everyone participates with an equal voice.
It’s very easy for some team members to dominate conversations, but in doing so, other team members may not have an opportunity to share their ideas. When this happens, there is no true consensus or full support for the solutions developed. Great care must be taken to give every team member an equal voice. One technique to do this is to give everyone a pack of sticky notes and let them write their ideas down, one per sticky note. Then, they share one idea at a time, one person at a time. Place each sticky note on a flip chart for everyone to see. Be careful not to let a team member share more than one idea before another team member gets a chance to share.

4. Keep the team moving.
I mean this both mentally and physically. If team members sit in one place too long or spend too much time on one topic, they will get bored, disengaged, and lose momentum. Get the team members out of their chairs, moving around the room, or out of the room. Break up activities into small chunks, so that there isn’t a chance for complacency or boredom. This tests the facilitator’s creativity, but it is vital for positive momentum and progress.

5. Time is precious. Break down barriers to progress.
Sometimes the team is looking for an answer and the expert is not in the room. A good facilitator will challenge the team to get the answer from someone else, in a different way, or by some quick estimate. In extreme cases, the facilitator will encourage the team to interrupt a meeting to get the answer they need. In even more extreme cases, the facilitator will get the answer for the team by interrupting a meeting or going to a higher-level leader for an answer.

6. The more ideas the better.
When a team is thinking up ideas and alternatives, their first ideas are typically things they are most comfortable with or don’t challenge them. Facilitators should drive the team to think of things that haven’t been tried before. The first step this is to ask team members for more ideas. Most people can come with 3 alternatives for almost anything. Ask for 7 in this case. If the team has stopped writing ideas, ask questions in as many different ways as possible, pulling more ideas out of the team. When we challenge ourselves, we are more often able to deliver breakthroughs.

7. Don’t let best get in the way of better.
We want teams to make improvements. Sometimes team members want things to be perfect before trying their solutions. The problem with this is that nothing is perfect and if we wait to have everything perfect, we will never test our improvement(s). So, the facilitator should encourage team members to try their ideas out before they are fully designed. It’s perfectly acceptable to make mistakes, as long as we learn from them and improve upon them. I tell teams to shoot for 60% confidence. It gives them more opportunities to try things quickly.

8. Use frequent check-ins of progress.
Once team members start working on their improvement projects, it’s easy to assume everything is going as planned and issues are addressed when they arise. However, that’s often far from the case. Team members often get stuck and struggle on their own until time runs out, if left to their own devices. Frequently connect with the team to check on their progress and determine any areas needed support. I have found that 1 ½ hours is about the maximum amount of time that team members should work independently before coming back together to share their progress. This is also a way to integrate efforts of different team members and eliminate duplication of efforts.

9. Teams that are having fun will accomplish more.
People like to win, laugh, have fun, and share in success. As a facilitator, you should be looking for ways to help the team win. Find activities that will make their time spent together engaging and fun. You may even need to develop team activities that help them work together better. 

10. Less you, more them.
The reason the team was brought together was to solve a problem. If you had the answer to the problem, you wouldn’t need a team in the first place. A good facilitator will encourage as much participation from the team as possible by asking probing questions and creating a participatory atmosphere. Once the questions are asked, you must allow the team answer to them, not you. Often, they will want an answer from the facilitator, but you must resist the temptation. This is their effort, not the facilitator’s, so it’s best to let them struggle through hard questions.

These 10 facilitation techniques take practice, but they will help you get the best out of the teams you are working with. Take pride in knowing your teams solved their problems and it appeared you did nothing at all to help them!

How to Use Kaizen to Ensure Teams are Invested in Process Improvements

In 2005, I was helping a team improve the safety and productivity of their operating line. During a 4-day span, each of the team members was able to try and implement many different ideas that arose from their creativity. At first, they didn’t believe that they would be allowed to make changes to the operating line, but after each successive attempt, they grew more and more confident, and the energy, enthusiasm and momentum grew. At the end of the 4 days, each of the team members reflected on their experience. One of the team members was a gruff mechanic who had been skeptical at the beginning of the session. He stood up with tears in his eyes and stated that this had been the most meaningful and impactful experience of his working life. I knew right then that I wanted to bring this joy to as many people as possible.

Kaizen brings people together to solve problems in their area of concern. They have the most understanding, experience, and vested interest in the effort. They also reap the benefits of the improvements moving forward. Kaizen asks us to make things better, not perfect, and go rapidly, without investing anything but the time and energy of the people making the changes.  There may be some minimal cost, but because things are going so fast, a significant financial investment isn’t likely. Using the speed of Kaizen and the creativity of the team, I developed 3 approaches to drive the deep and emotional connection to improvement that I was seeking.

1. Idea Gathering and Sharing with Sticky Notes
Each team member takes a pad of sticky notes with them as they tour the area of concern.  With guided questioning, the team members write down their personal observations or ideas that come to mind while touring. It is quick, personal, and drives ownership and accountability to come up with ideas for the benefit of the team and the people in the area. I ask each team member to write down one idea per sticky note, so that nothing gets missed and it’s easier to organize ideas as a team once we have reconvened. In the meeting room, I have the team members share all of their ideas, one person at a time, one idea at a time. Each idea is placed on a flip chart or on a wall for everyone to see. If there are 15 team members, I have each person share one idea until the team has heard 15 separate ideas. Then I give them a chance to share their second idea, third idea, and so on, until the team has run out of ideas. This creates an atmosphere where everyone has equal voice, regardless of position, experience, or pay grade.

2. Prioritization with Criteria
Once the ideas have all been shared and posted, the team may choose to group similar ideas together. This gives them the chance to see all of the ideas and remove any redundancy. Following this, each team member is asked to pick his or her top ideas using these criteria:

a. Provides the biggest benefit to our team and our customers

b. I personally want to do this

c. We can do this during the allotted time of the event

Everyone is given an equal number of votes (usually between 3 and 5), so no team member can dominate the conversation or the voting. These criteria are interpreted differently by each team member, but in the end, this approach creates a list of the team’s top priorities.  This approach generally takes no more than 10 – 15 minutes.

3. Pick Your Project
We now have a list of things to work on, prioritized by the amount of votes the team has placed on them. I then list the top 3 or 4 projects on a flip chart, depending on the size of the team.  Now it becomes personal, as I tell the team, “First come, first served. Place your name on the project you want to work on.”  More than a few times, team members rush to the flip chart to put their names on a project. They want to ensure they get the project that matters to them the most. This may sound risky, as a project may not get claimed. I have never seen this happen. Team members have different interests and you can’t always guess what they are, so I have stopped doing that. Also, if there aren’t enough team members on a project, I ask if there’s anyone willing to swap projects. Often, there are a few team members who don’t have a real preference, so they are happy to change projects. 

Now that we have personally observed and shared issues, picked our projects, and assigned the work to the people who want to do it the most, we have the foundation for the deep personal connection to the improvements that we seek. Sometimes a team member will find it moving enough to convince others to get involved in future efforts and find the same joy that they did.

How to Organize Your Work Space With 5S

In the world of Lean Manufacturing, 5S is used to organize workplaces to make them safer and more productive. Although many great manufacturing organizations and others have been credited with inventing or popularizing 5S, I’m pretty sure my mom invented it.

When I was young, I wasn’t very organized. My mother told me, “pick up your clothes,” “put your toys away,” “make your bed,” and most importantly, “there’s a place for everything and everything in its place.” Not only did she tell me to do these things, she showed me how to do them, nagged me about them, and checked my work quite often. I couldn’t get away with anything!

Although I really didn’t heed my mother’s advice as a child, as I grew older, I came to realize how powerful these statements were. When I entered the working world, I started applying 5S to many different situations and was amazed at the immediate positive impact that I was able to make. I also saw how deeply it moved those that were able to participate in 5S efforts. They became disciples of the effort and wouldn’t allow others to erode any of the benefits of the change.

As simple and powerful as 5S is, there are many who don’t understand what it is and how it should work and use it to just “clean things up.” I would like to share my understanding and approach to 5S and try to clear up some of the confusion. 

The first thing to understand is the purpose of using 5S. I believe 5S should be used to improve the safety and productivity of an area or work space. Once agreement and alignment around this purpose has been established, the team will make choices that will benefit the users of the area.

The first S, Sort, tells us to remove anything that is not immediately needed or useful in the area. Duplication, clutter, and non-working things are to be removed, discarded, donated, or sold. Three hammers turn into one, broken things are repaired or replaced. Things that were saved, “just in case,” are no longer allowed in the area. It’s not unusual to take away more than 70% of the tools, materials, documents, and other things that were just getting in the way.  Productivity is improved by reducing the time and effort required to find what’s needed.  Safety is improved, as you no longer have to move clutter out of the way to get to what is needed.

Set in Order, the second S, says to create visible, easy to find locations for all remaining materials, tools, and equipment in the area. Define proper inventory levels, place things within reach, make it impossible to lose anything or put it away improperly. As Mom said, “A place for everything and everything in its place.” Trip and bump hazards are eliminated in this step, greatly improving safety. Productivity continues to improve as it becomes difficult for anyone to be non-compliant to the system requirements.

The next S, Shine, tells us to clean and inspect everything that remains in the area, to ensure that it is in optimal condition. We are trying to prevent problems before they happen by identifying any issues, cracks, leaks, or poor performance that may occur with our tools, equipment, documents, and other things that help us do our work. Some think that Shine means “clean things up.” I believe Shine is much more powerful than that, as this effort can reduce risk of failure, greatly improving productivity. Safety is enhanced because we can rely on everything to work properly when called upon, creating no surprises. 

The fourth S, Standardize, tells us to create expectations and audits to involve everyone in keeping things as they should be. No longer is it the responsibility of just one person, but the greater community. When I work in an area, I may not realize that things are shifting to their prior condition, things are starting to return to the area that were previously removed, or people aren’t putting things away properly. With a series of audits and auditors, there is a better chance to catch issues quickly and hold each other accountable to follow the rules of the area. In context of my childhood, I thought my room was OK every day, but Mom didn’t always see it that way, and often pointed out the error of my thinking. The safety and productivity gains are maintained through the commitment of the community and its auditors.

The fifth and final S, Sustain, challenges us to continually improve the performance of the area. By scoring the performance of the area and tracking it for everyone to see, we can identify further improvements that would enhance the safety and productivity of the area.  Once an area has seen the benefit of implementing 5S, it is not unusual for people to see other things in the area that could become part of the overall 5S system.

I think we can all agree that being organized is beneficial. I think we also can agree that we should listen to our mothers more often. Because I don’t like my vegetables, I can’t guarantee that I will do everything that mom tells me, but I will definitely do my best to listen more.

Three Tips in Preparation for a Successful Improvement Event

Process Improvement Partners LLC was founded to help teams achieve breakthrough improvements in safety, quality, customer service, and productivity. Improvement Events are used to bring teams together to solve critical problems in a fast, engaging, and sustainable way. These Improvement Events, also known as Kaizen Events, can vanquish problems forever when they are done well. Preparation is a key component for success. In the spirit of helping teams achieve the best possible results, here are three tips to help you successfully prepare for an Improvement Event:

1. Develop a Strong Charter for the Event
At least 4 weeks before the Improvement Event, the Leader, Sponsor, and Facilitator of the event should come together and align around a charter for the event, which asks these four questions:

1. Problem - What is the problem that the team is being asked to solve? Why is it a problem, what is the impact of the problem on the business or the customer(s), and what would happen if the team could solve the problem?

2. Objectives - What are the objectives of the Improvement Event? What are the measurable results to be achieved? What would be the tangible evidence be that would show that the problem has been solved?

3. Team – Who are the people who can help solve the problem during the Improvement Event? Who has the interest, enthusiasm, and creativity to come up with potential solutions in a short period of time? Who can facilitate this event, to help the team on its way to a solution? Who will lead the team?

4. Output Owner – When the Improvement Event is over, who is responsible to implement the solutions developed by the team? Who will make sure that changes are properly communicated? This Output Owner should ideally be the Team Leader, as they will only agree to solutions that can implement and support.

Once the charter has been agreed to by the Leader, Sponsor, and Facilitator, the team is empowered to develop and implement their solutions to the problem that they are asked to solve. There is no need to gain approval for their solution after the Improvement Event. They are encouraged to get input and feedback during the event, to ensure that they have considered all aspects of the problem and potential solutions.

2. Create Leadership Alignment and Support for the Event
There should be an Executive Sponsor for the Improvement Event. This is the person that believes in the value of the event, supports the efforts of the team during the event, will remove roadblocks during the event, and will deal with resourcing issues that come up because the team members are being asked to fully dedicate their time to the event. The Executive Sponsor should communicate directly with the managers of each team member to gain their support and commitment to clear the calendars for their direct reports. Each team member should give their full focus and attention to the Improvement Event.

3. Plan Proper Facilities and Food
An Improvement Event is special. We are asking people to set aside their normal work and focus on a critical business problem. As such, we need to provide the proper food and facilities that will help them stay focused and engaged. Bring in morning and afternoon snacks, and feed the team lunch in their working space. If they stay together, they are more likely to stay focused on the problem at hand. If they disperse during lunch, they may get distracted, lose focus, or get drawn in to other business issues.The meeting space(s) should provide adequate space and privacy from outside distractions. There should be enough floor space and wall space to allow the team to try out and display their ideas and solutions. Improvement Events are interactive, visual, and energetic. People need to be able to move around freely and safely. If they need to use computers, there should be adequate power outlets available in the meeting space(s). Finally, they should have access to any resources necessary to solve the problem. Don’t move the team off-site if they need access to others in the company who may have vital information to share.

As you plan your next Improvement Event, keep these three tips in mind to give your team the best chance for success. The investment of time and effort will paid back many times over.