How do you measure knowledge?

If you produce a physical product, it’s easy to see things being created. You can count them, measure them, and identify the cost to produce them. But what happens when you create knowledge or a new product idea. How do you measure your output? More importantly, how do you measure your effectiveness and identify when you need help?

The technology group of a global ceiling tile manufacturer that I worked for decided it was time to figure this out. For many years, our leaders requested resources and money for projects based on anecdotal evidence and gut feelings. In the business world, you must show a return. If you can’t, somebody else will get the resources and investment.

Resources had become scarce and there wasn’t a clear way to show the return on investment, when requests for money or people were made. We needed to come up with a metric of contribution for our group.

We had four distinct Value Streams: Innovation, New Product Development, Capital Engineering, and Business and Operations Support. Each one worked at different points in the business cycle. Innovation was at the very beginning, when an idea was generated. Business and Operations Support engaged after a project was complete. Was there any way to create a metric that made sense for all four Value Streams?

Developing a New Way to Measure Value

Our plants had a single metric of performance, called Plant Reliability. It measured final output against the maximum output achievable during a defined timeframe. This number, measured as a percentage, could be anywhere from 0 to 100. Each percentage point was worth a defined amount of value to the business, depending on the size and complexity of the plant. When the number went up, cost per unit went down and customer satisfaction rose. It was difficult to “game the system” and each plant could be compared to itself and other locations. Plant Reliability helped the business choose where to invest money and resources to improve performance.

After much discussion, I was able to get alignment of the leadership team to develop a metric based on the concept of Plant Reliability. The twist was that the four value streams would use the same metric to compare performance to themselves and to the other value streams. Then, we would make investments based on the opportunity identified. But only if we could somehow tie the metric into financial results.

Our value stream leaders were talking in terms of Net Present Value (NPV) when they discussed the efforts and results of their teams. In Innovation, for example, they would assign a team to work on a product idea with the expectation that it would generate future revenue. This information could be entered into a spreadsheet and the Net Present Value of the project was determined. These numbers were estimates, but the only way a project could be approved to proceed was using the analysis that determined the NPV.

Measure, Communicate, Adjust, Repeat

We decided to give NPV a try. Each value stream figured out how they would calculate it for their part of the business cycle. Once we approved the calculations, we needed to figure out a way to display it in a meaningful way and determine a target to achieve.

We created an overall NPV display board and each value stream incorporated NPV into their individual team display boards. Once this was done, we educated our teams, customers, and suppliers. Then, we started using NPV as a key discussion point when evaluating work and investment of resources. Instead of gut feel and emotion, we were now using facts and data. The allocation of resources and investment across value streams became a simpler decision to make. The business ultimately got a boost in outcomes from the results-focused behavioral change.

The Journey is Long

After five years as Lean Champion, my voice wasn’t being heard so well. Sure, I was able to promote and facilitate Kaizen events and help people solve problems, but I was unable to move the leadership team to take the next steps in our Lean journey. Any time I spoke to our leaders about strategy, they were too busy to consider anything that deviated from their current operating approach.

I realized that I needed to engage an outside voice. Someone with credibility, who could say the difficult things I was saying with different words. Someone who could influence our leadership team to change their behavior in a way that would support our Lean transformation.

You’re Never Too Good for Growth

Two years into our Lean transformation we had undertaken a Lean assessment to see where we were and where the opportunities existed. Looking back, it was more tactical than strategic, but was appropriate for our maturity.

Now, I had an idea. What if we tried another Lean assessment, this time focusing on the leadership and strategic aspect of our efforts? When presented to our four Value Stream Directors, they seemed satisfied with their efforts and indicated they had this “Lean thing” down. I knew right then we were in trouble!

I met with my manager, the Executive VP of Technology, and convinced him that we needed something to open our eyes to the possibilities for the next steps in our transformation. But, if we used our internal resources to conduct the assessment, we would rate ourselves too highly. We had become complacent and overconfident. Our results were impressive. The product portfolio had doubled and time to market had been reduced from eighteen to ten months.

After receiving approval, I reached out to Mike, a consultant from Shingijutsu, who I had met four years before. He taught me that no matter how good you think you are, there are always ways to improve and grow. He agreed to join us at no cost. He was interested in how we were doing and had the freedom to do what he wanted. He flew in from Seattle and I joined him for breakfast on the first day of his visit. We talked about the current situation. He assured me that he had seen this many times before. He knew he could help.

Our first meeting was with the Leadership team. As they introduced themselves, most of them talked proudly about their team’s accomplishments and how they incorporated Lean into their processes. Each time, Mike asked them probing questions about their progress and approach. He exposed gaps in their efforts and understanding of Lean in a way that was respectful, but eye-opening. Team members took many notes during the discussion.

The Beginning of Breakthrough Thinking

For the rest of the week, Mike and the assessment team participated in many meetings and activities and identified huge opportunities in our Lean journey. Mostly aligned with my prior efforts, Mike had a way of communicating to the organization that had credibility beyond any internal resource.

At the review of findings, we presented four recommendations:

1.      Learning starts at the top – leaders must demonstrate the behaviors of the change they want to make

2.      Linkage – become in lockstep with customers and suppliers to ensure that everyone gets only what they need, when they need it

3.      Stability – level the flow of work to drive the production system stress level down

4.      Cycle time and quality – deliver only what the customer wants, when they want it, at the appropriate level of quality

Although these were not new ideas, the leadership team saw them as breakthrough thinking and instantly committed to them. One Director admitted that prior to the assessment he thought he knew Lean very well. Now, he was sure that he had much learning to do to become competent.

Following the assessment, there was a renewed commitment to Lean in the organization and many breakthroughs were made over the next year. For my part, I was extremely appreciative of the time Mike gave us and the renewed interest that was generated by his visit.

Cream Rises to the Top

I was working with a team in New Jersey to implement Training Within Industry (TWI) on a critical household cleaner line. Plant leadership saw this as a key element in their strategy to improve overall line performance.

In the initial Kaizen event, I trained twelve team members to competently create standard work and train others using the TWI method. Much like my first experience with TWI, the training method wasn’t natural for the team, but by the end of the Kaizen, they had all shown proficiency with it.

One of the hourly team members, Rita, seemed inspired by this “new” method for training. The rest of the team members agreed she had a flair for it and would do quite well training others on her crew.

When I got home at the end of the week, I was confident that TWI would help the plant improve line performance. I hoped the enthusiasm for TWI would continue. Over the weekend, I received a text from Rita, who was excited by what she had learned and had done further research on TWI and other Lean concepts. While this isn’t unheard of, I am always impressed how a winning Kaizen experience can move certain team members to want to learn more.

I sent Rita a congratulatory note and provided a list of my five favorite continuous improvement books for her consideration. She thanked me. I wondered if she would continue to take the initiative to learn more.

Boosting Confidence Through Training

Over the next few weeks, line performance wasn’t improving. I was asked to return to the plant to support the TWI rollout. Other issues had taken priority and the trainers hadn’t been given the opportunity to create standard work or train their coworkers.

I suggested that we have a refresher for the trainers and then practice training their coworkers with the standard work created during the initial Kaizen. Leadership agreed, and I was assigned to four team members, including Rita. I was curious to see what she had done in the weeks between the Kaizen and my visit.

It turned out she had been training some of the people on her crew and getting really good at it. She even gathered feedback at the end of each training session, asking for the level of confidence before and after the training. When her coworkers expressed their level of confidence had risen, it reinforced how important the training was to Rita.

It Takes One Good Leader

Over the next two months I returned to the plant for a few days each week to continue the training rollout. Rita participated every time. It was clear that she had become an amazing trainer. During one session, she taught the plant manager to change over a critical piece of equipment that only the highest skilled workers had previously done. We now knew this was going to work. Other trainers saw what Rita was able to accomplish and it boosted their confidence.

The following month, the line reached its performance objective and has stayed there since. I am convinced that the training process and Rita’s leadership contributed to this success.

Words Matter

Training and Review is the second spoke on the Wheel of Sustainability. The basis for Training and Review is Training Within Industry, which was developed at the onset of World War II to quickly train inexperienced workers to produce all the necessary armaments and supplies in support of the war effort. It’s one of the reasons the US and its allies won the war.

Training Within Industry (TWI) is an extremely disciplined approach to ensure that the person doing a job learns it in the safest and productive way and never forgets the right way to do things. Recently, I had the opportunity to help a team apply TWI to a new laundry detergent line that was being installed in their factory in Ohio. The goal was to use this training approach to ensure the line started up at high-performance rates.

I had limited experience with TWI, so I did research and found a book and other materials to prepare me to deliver a winning experience for the team and the company. After reading the book about a dozen times and practicing the exercises to reinforce TWI, I was ready to facilitate my first TWI Kaizen event. The team leader and I agreed that we would follow TWI exactly as designed and not take any shortcuts.

We had 24 team members, mostly from the production floor, with a few support staff sprinkled in. On the first day, I taught the TWI approach and its key principles, including:

·        Focus must be on the learner to maximize their experience

·        Words matter

·        All training is presented from the perspective of the person doing the work, not the equipment

·        The simpler the instruction, the easier it is to follow

The Value of Different Perspectives

We practiced building standard work by making paper airplanes. This exercise illustrated how much we take for granted when we’re trying to explain what to do. From time to time, I had to correct errors in approach, as team members were getting different elements of TWI confused.

After the team successfully completed the exercise, we took a Gemba walk to identify real-life plant activities to build TWI standard workaround. As the TWI method was time-intensive, the team was directed to pick work elements that took one minute or less to accomplish.

We created six four-person sub-teams. I rotated through and coached them as they built their standard work. Because TWI was brand new to everyone on the team, each team member needed personal attention to properly build the standard work. Some caught on faster than others, and by the end of the first day, I was mentally exhausted from the coaching. I know many of the team members were tired too.

After the standard work was completed on day two, sub-teams were instructed to practice training each other using the TWI method. I planned to rotate through each sub-team to coach them through the training process. With four members on each of the six teams, they were instructed to conduct four rotations, where each team member would be able to participate as one of the four positions:

1.      Trainer – responsible to use the TWI method exactly as designed

2.      Learner – fully focused on the Trainer’s instructions and coaching

3.      Auditor – responsible to ensure the training process was followed properly

4.      Improver – responsible to look for improvements to the standard work

On my first team rotation, it was apparent that TWI wasn’t as natural as it appeared, and it took more than 40 minutes to get through one round of training (for one minute of work content). I had to step in and coach many times, as the Auditor wasn’t catching the nuances of the training process. After I completed my time with the first sub-team, I was then able to coach the second and third sub-teams before the end of the afternoon.

Knowing that I couldn’t complete all rotations before the end of the day, I brought the full team back to the meeting space and gathered their feedback. Many team members noted that it would have been nice to be corrected immediately around the TWI method, rather than waiting for me to rotate to them when available. I apologized and said I hoped that they were learning what “right” and “wrong” felt like, especially from the perspective of the Learner.

Do you really understand?

On the morning of the third day, I met with the fourth sub-team. I was in for a wake-up call, and so were they. Matt was the Trainer and Roy was the Learner. Just like the Trainers on the other three sub-teams, Matt had difficulty with the structure of the TWI. I stepped in and corrected him, and asked him if he understood my instructions. He said he did, but then made the exact same mistake in the next attempt. This went on for forty minutes. I must have corrected Matt half a dozen times. Each time, he said he understood my instructions. But he truly didn’t. I knew I had to do something, but what? Then it dawned on me.

Me: “Time out. Let’s move away from the equipment.”

Matt: “Sure thing, what’s up?”

Me: “Look, you keep telling me that you understand what I’m asking you to do.”

Matt: “Sure, I get it.”

Me: “Clearly you don’t. We need to get this right and we’re going to stay here until we do this right, even if it takes the rest of the day.”

They all looked at me as though a light had turned on – this was serious! Once I gained agreement from all four members to follow the method exactly, we started the training process again.

Focused Practice Makes Perfect

Matt was now focused. He followed the TWI method to the letter, and the training proceeded without any issues. Roy was able to concentrate on the training and demonstrated his knowledge very well. The rest of the team was able to see the value of the approach and why the words mattered. I could finally move on to the fifth and sixth sub-teams.

The rest of the event proceeded without major issues and by the end, we had not only created twenty-four TWI believers, but also developed a strategy for TWI implementation that could be supported and audited by the team and plant leadership.

When it came time to get feedback from all team members, I was pleased to hear that they appreciated the personal coaching that I provided and that my “tough love” wasn’t so tough! More than that, they realized that words really do matter, and by being focused and disciplined, they would be able to efficiently and safely train the rest of the workforce.

We Won the Battle but Lost the War

During my corporate career, we identified a critical gap in our safety training system. There wasn’t a good way to ensure traveling engineers, scientists, and technicians were compliant for annual safety training requirements. We had to get everyone immediately compliant and then develop a system for annual recertification.

Working with a small team and under the direction of the Global Technical Services Vice President, we established “Technical Services Safety Days”. No one was allowed to travel during the week of training.

We developed interactive safety training activities that included everyone in the group. This would allow us to achieve compliance and provide useful skills for work and at home. We added some fun activities and games to encourage team building and networking. When training wasn’t occurring, employees were encouraged to catch up on paperwork and reconnect with others at the corporate center.

Technical Services Safety Days was a success. One hundred and fifty employees learned and practiced firefighting, equipment lock-out, chemical hazard identification, and many other critical safety topics. Tell, Show, and Do was used extensively. People appreciated the personal touches throughout the experience. My team won an award for putting together this meaningful activity and restoring safety compliance in short order.

For the next three years, Technical Services Safety Days was an annual event. People looked forward to it. Everyone blocked out their calendars for the week. For some, it was their only time in the office and they took advantage of the opportunity to network with their co-workers. They honed their skills through the creative training of best safety practices.

Then, everything changed. The company purchased a computer-based system to deliver required safety training. Employees could review the training on their own time and at their own pace during the year.

Except, it really didn’t work that way. Most waited until the end of the year and then crammed the training in to get it done. There was little engagement or knowledge retention. It seemed like a good idea and a better use of resources, but in the end, we lost the immeasurable value of having interactive Technical Services Safety Days.

Lean in Action

I was Lean Champion for the Global Technology group at a ceiling tile manufacturer for six years. During that time, I was responsible to train all new employees in Lean principles and techniques as they joined our group. The goal of this training was to help them understand what we were doing and how we applied Lean to our work. My aim was to generate interest and engagement around Lean. In the early years, things didn’t always go the way I expected.

When I first started training new employees, I created eighty PowerPoint slides that described as many Lean concepts as I could squeeze into the two hours allotted for the training. I reviewed the slides, gave participants a chance to ask questions, and then declared them “trained.” I never got many questions during this training and new employee participation in Lean efforts was hit or miss once the training was completed.

I knew I had to do better if I was going to realize my engagement and participation goals. The first thing I did was develop activities to demonstrate the various Lean concepts I was trying to reinforce. From an interactive 5S number search to a triangle peg jumping game, new employees started to draw value from the time they spent with me. I saw a slight increase in engagement and participation. I wasn’t satisfied. What else could I do, I wondered?

My breakthrough came one day when one of the trainees asked, “This is all well and good, but how does it apply to what we do in Global Technology?” I knew what I had to do. Make the training specific to the actual work we did and give demonstrations of Lean in action.

The first thing I did was test my training against the Global Technology Vision and Mission. If parts of the training didn’t support our Vision and Mission, I either removed it or modified it. Now the theoretical became practical. Power Point slides were reduced and made more relevant.

Focusing on the suggestion of Lean in action, I added a Gemba walk to the training. After an hour of classroom training, I led an interactive tour of areas that had applied Lean thinking to their processes. From the Pilot Plant to the Capital Engineering Records Room to the New Product Development Project Board, new employees could observe and interact with people using Lean. They had a more definitive picture of how Lean worked in practical settings.

The training still took two hours, but was much more interactive and engaging. Because I took a different tour route each time, I was more energized by it as well. Most importantly, participation and engagement of the new employees rose to record levels.

Attention to Detail

In 2007, I moved my family across country to take a new role as Production Manager for a ceiling tile plant in Oregon. The plant had a strong team-based culture. People genuinely wanted to help each other work in as safe and productive manner as possible. It wasn’t unusual to see the Plant Manager on the factory floor, assisting the technicians with their work or helping them stay safe.

Plant performance had deteriorated over the years and we were operating at less than budgeted levels. I was determined to identify the reasons and work with the technicians to turn things around.

The first two months of my time at the plant, I spent more time on the factory floor than in meetings or in my office. I came into the plant at any hour of the day or night, trying to assess and understand the reasons for the lowered performance. People had the right attitude. They wanted to win. What was holding them back?

The Team Managers had strong relationships with their people. The equipment was in generally good condition and there was an established preventive maintenance program. Something was missing and I had to find out what it was.

One morning, while taking a walk around the plant, I noticed papers on clipboards at each operating station on the line. They were titled “While Running Tasks.” Taking a closer look, I saw operations checks to be completed and signed off by the technicians on shift. There were many blank spaces on the papers, meaning that checks weren’t completed during the week.

I reviewed these papers and found that less than half of the checks had been completed and signed off. The Team Managers told me the checks were defined as critical to the performance and safety of the line. Teams of technicians had identified and agreed to the tasks. They met every three months to review and update the “While Running Tasks” as new issues arose.

I reviewed the forms to see if there was any correlation between tasks not completed and downtime or scrap events. In a two-month sample, more than one-third of the downtime and scrap events could have been prevented if the checks were completed properly and on time. I now knew what had to be done.

Working with my three Team Managers, we came up with a plan to rapidly improve performance. We would rededicate ourselves to the “While Running Tasks.” Nothing less than a 100% completion rate was acceptable. Technicians would be accountable to complete and sign off on all tasks during their shift. Team Managers would audit the tasks on every shift, and I’d audit randomly every day and do a complete audit at the end of every week.

My Team Managers wanted to conduct crew meetings and share the new requirements with their crews. I told them I wanted to be a part of every meeting, sharing my logic and belief in our new requirement. They agreed and we planned crew meetings for the next day at 6:30 am, 3:30 pm, and 10:30 pm.

I kicked off each meeting. I told the crews how impressed I was by the teamwork I had observed. I also talked about the honesty of people working there. No one ever signed off on anything unless they had actually completed a task. Now, it was time to use our teamwork and honesty to improve performance at the plant.

I reviewed my findings about the “While Running Tasks.” I shared examples of line failures and scrap events directly impacted by the incompletion of the critical work they had identified and agreed to. We owed it to each other to perform the work we agreed to. Next, I laid out the principles and expectations moving forward:

1.       Attention to detail will improve performance and keep everyone safe.

2.       While Running Tasks are the first line of defense to prevent problems and reduce safety risk.

3.       We must achieve 100% compliance to While Running Tasks – anything less increases risk for downtime and injuries.

4.       Completing While Running Tasks is a condition of employment.

I then handed the meeting to the Team Manager, who described how he would work with his crew to attain 100% compliance. He described how he would hold himself and each crew member accountable to their “While Running Tasks.” Crews were also encouraged to review their “While Running Tasks” and verify they were practical and designed to prevent problems.

We received many questions. It was easy to answer any concerns. We truly believed this approach was going to keep everyone safer and more productive. People were worried they were going to be fired if they forgot a task once in a while. We understood and put in levels of discipline. We didn’t want to fire anyone. We did believe that 100% compliance was the best strategy to improve performance at the plant. We couldn’t compromise our beliefs.

During the first two weeks, there were a few “forgotten” tasks. There was some discipline recorded. No one was fired. The first month, compliance reached 90%. Plant performance was noticeably improved. The second month, compliance was 98%. The third month, we achieved 100% compliance. Everyone could tell the difference. The plant was running significantly better. For the next year and a half, compliance stayed at 100%. During that time, the plant attained company records for performance. Attention to detail cost us nothing; except time, focus, and commitment.

A Wakeup Call

In 2001, I was the Business Unit Manager at a Vinyl Flooring Plant in Pennsylvania. Responsible for one of the four business units on site, I had a unionized workforce of 160 employees, three supervisors, and eight technical staff. My job was to turn the shrinking business around and keep my employees safe and productive.

With many layoffs over the years, the shortest tenured hourly employees had more than twenty-five years of service. They had seen many Business Unit Managers come and go over the years and were determined to outlast me. All three supervisors had been promoted from the ranks and were also of the mindset to survive until the next Business Unit Manager arrived.

This wasn’t the best situation to drive change, but we had to do many things better, and fast. One such change was to do a better job protecting the safety of our employees. We instituted a stronger safety program with improvements in the way employees interacted with and locked-out (an OSHA mandated program) their equipment. Although we were convinced that we were doing the right thing, we had major pushback from the union and even the supervisors, who saw all of the new requirements as a waste of time and effort. After much discussion, my staff and supervisors agreed as a team to be consistent in our safety message, approach, and accountability. At least that’s what I thought.

One day I overheard one of the supervisors telling his crew they needed to follow the new safety protocols because, “The company is making me do this.” Much to my concern and disappointment, this statement confirmed he didn’t believe in what we were doing. At that moment, I knew he would never hold himself or his crew accountable to keep themselves safe.

I couldn’t let this continue and immediately stepped in. I corrected the situation and sent him packing. It sounds harsh. There’s much more to this story. He had been demonstrating a pattern of subversive and destructive behavior for many months. This was the final straw. I was unwilling to put my employees at risk and knew a change had to be made.

Although firing someone is a life changing event for them and for those they work with, it ended up turning out fairly well for everyone involved. The remaining supervisors and crew took safety more seriously and the fired supervisor later admitted this was a wakeup call for him, as he was able to take a renewed commitment to safety to his next employer.

Let’s See How Things Go

During my tenure as Production Manager at a ceiling tile plant in Oregon, I implemented strict rules around changeovers:

·         No one is allowed in the breakroom during a changeover without Team Manager approval.

·         Everyone is available to help during the changeover.

·         Everyone is at their stations when the line is ready to start up.

·         One Best Way changeover procedures are followed to the letter. No deviations. The procedures were developed by the technicians. There was no reason not to follow them.

These rules came from my observations the first two months after I arrived at the plant. Those not directly involved in the changeover used that time to go to the break room. We lost vital minutes waiting for technicians to return from break when a changeover was completed. Sometimes help was needed to verify changeover settings prior to starting the line back up. If resources weren’t available, things took longer. Technicians were frustrated when they had to wait for help.

Technicians didn’t like the “no break during changeover” rule. I explained changeovers were the most critical activity during the production run and everyone should be helping to execute the safest, most accurate changeover possible. It couldn’t be done from the breakroom.

Some argued they wouldn’t be able to get their breaks under these new rules. I felt they’d have more flexibility around their breaks once changeover performance improved.

Immediately after the new rules were implemented, employees came to my office to express their displeasure. After listening to their arguments, I explained why I felt the rules were necessary. The plant had a culture of teamwork and help. There was no way to help teammates from the breakroom. Then, I told them, “let’s give it a chance and see how things go.” They didn’t like my answer. I was firm in my convictions and sent them on their way.

At the beginning of every changeover, I took a walk to the break room to ensure people were following the changeover rules. I didn’t want to put all of the burden on my Team Managers. I held myself accountable for rule enforcement. From time to time, I found people in the break room during a changeover. I always asked if their Team Manager had approved the break. Most of the time, they got up and went back to the line, indicating they hadn’t.

After four weeks, changeover time was reduced by 33%. Not only was the time reduced, it was more predictable. Just by having everyone available to help with the changeover and in place when the line was ready to start up. My team noticed the results. Visits to my office by “dissatisfied customers” came down significantly.

Team Managers felt more comfortable enforcing the changeover rules. They knew I had their back and they were seeing results. They were able to explain the rules and the reasons for them. It was no longer “Adam’s rules for changeovers”.

Two weeks later, a technician came to my office. He said, “Adam, I know you’re just going to tell me ‘let’s give it a chance and see how things go.’ I just wanted to tell you how I feel about the changeover rule anyway.” I thanked him for the feedback. He knew what I was going to say. There was no point repeating it.

Changeovers became a source of pride across all of the crews. Teamwork strengthened and performance continued to improve. What was once difficult and frustrating was now safe, simple, and predictable.

Four Value Streams = Four Boards

I reported to the Vice President of Global Technology for a ceiling tile company as Lean Champion. During my tenure, we kicked off our Lean transformation and established four Value Streams: Innovation (R&D), New Product Development, Capital Engineering, and Business and Operations Support. Each Value Stream Director guided efforts to deliver value to the internal and external customers who relied on their critical results.

While the Value Streams had different customers and missions to accomplish, they interacted frequently and shared resources. I supported all Value Streams and had the opportunity to build relationships across all areas of the business. One area we worked on was how to keep critical information in front of us and engage in it at all times.

In the early days of our Lean transformation, we identified the need to create white boards to display the most relevant and urgent information for everyone to see and act on. Using weekly huddles, the boards would be reviewed and decisions were made and documented. Some of the teams took this need for a white board to be a requirement and put together their boards and huddles just because they thought the Global Technology VP and Lean Champion said it must be done.

It quickly became apparent these boards weren’t helping the teams accomplish their work in a manner more productive or safer than they had been before the boards were established. In fact, one of the teams got a bit rebellious and started to make their huddle a grind, rather than a value-adding exercise. Snide remarks and rushing through information replaced deep discussion and problem-solving.

I called a meeting with the Global Technology VP and the four Value Stream Directors. After much discussion, I was able to draw out their resistance to the boards and huddles. Probing further, we identified the issue. They thought the design of the boards was prescriptive, leaving them no room to design for the purpose of their individual Value Streams. Directors thought everything had to look the same and act the same, even if it didn’t work.

Now that we had revealed the problem, we were ready to improve the situation. We quickly agreed that design of the boards and huddles should be left to the Value Stream teams. They’d decide what was most relevant and useful and then design the boards and huddles to highlight only that.

I offered my assistance in helping the teams design their new boards and huddles. Two Value Stream teams took up my offer. Two others decided to do it on their own. We agreed to these design principles:

1.       Design the boards and huddles with the tools and information that help your team make decisions in the best possible way.

2.       Don’t worry what your board looks like. If it helps you, that’s all that matters.

3.       Make it easy to know when help is needed.

4.       There’s no standard board layout. We’ll teach our leaders how to read the boards and support your efforts.

Within four weeks, all Value Stream teams redesigned their boards and huddles and started to use them. None of them looked alike. Over the next months and years, Value Stream teams redesigned their boards and huddles many times, based on what they believed was an improvement. The information they shared became more relevant, urgent, and beneficial to their employees, the overall Global Technology group, and their customers.

From time to time, other organizations benchmarked Global Technology due to our impressive results. Most people who visited with us asked why our boards looked different by Value Stream. They thought all boards should be standardized, allowing anyone to read and understand any of the boards without training.

The Value Stream teams came first, I told them. The teams did what was right for the business. We successfully taught our leaders how to read the boards and support the teams. Those who challenged my thinking didn’t always like my answer about standardization. I knew we were giving our employees all the tools they needed to make the best possible decisions for themselves, their customers, and the business.

From Tool Boxes to Tool Stations

In 2011, I was asked to facilitate a changeover reduction Kaizen event at a ceiling tile plant in Florida. Most changeover reduction events have a goal of reducing time by 50%, while maintaining or improving quality and safety. In this case, the team was asked to reduce changeover time by 90%. This would be a challenge for the team and my ability to facilitate them to a solution.

The area chosen was the edge finishing line. The line cut and painted edges on the ceiling tiles before sending them on to the packaging line. Using a panel saw called an equalizer, tiles were cut to a rough size. Four tenoners cut and painted the edges of the tiles to achieve precise outer dimensions and edge finish. The tiles were designed to fit snugly into ceiling grid. A portion of the tile hung below the surface of the grid, creating a three-dimensional visual.

The tenoners had dozens of adjustment points, requiring wrenches and other tools to meet the strict dimensional tolerances. All technicians had their own personal toolbox, which they stored far away from the line. When it was time to adjust or set up the tenoners, they gathered their personal tools and brought them over to the tenoner they were adjusting at the moment.

After training the team in Lean principles and Single Minute Exchange of Die (a changeover reduction approach) we watched a changeover conducted by the crew on shift. What we saw was a tremendous amount of movement by the technicians conducting the changeover. Most of the movement was due to each technician gathering and moving tools back and forth between the line and their personal toolboxes which were stored thirty yards from the tenoners.

The changeover took ninety minutes. Our goal was to achieve a consistent nine-minute changeover. I wasn’t sure it was possible, but there appeared to be a tremendous amount of opportunity, especially in the area of tool use and placement.

After brainstorming overall improvement ideas, I facilitated the team to focus on ways to eliminate the huge amount of movement we observed. The plant was built in the 1940’s. Most technician habits developed over many decades of production. I wasn’t sure people would be willing to change their approach and give up their personal toolboxes.

They weren’t willing to, but it didn’t matter. The team realized their toolboxes should be set up to do unscheduled repairs and adjustments. Placing tools right at the place they were needed, would save a huge amount of time during changeover.

We identified three tools used to set the tenoner saws and edge paint sprayers precisely. They were needed in eight separate locations. Were we willing to replicate those three tools eight times?

If we wanted to cut the time by ninety percent, we had to be willing to try extreme measures. I went to the hardware store and bought eight sets of tools. The team mounted them exactly where they were needed for the changeover.

In addition to the tools, we created visuals to show the steps and installed a large digital clock on a post. It displayed the changeover elapsed time. We tested our new procedure with all of the improvements and were able to complete the changeover in fifteen minutes by the end of the Kaizen event.

Although we didn’t meet our goal, changeover time was reduced by 83%. The team felt like they had won and the plant reaped the benefits of a safer and quicker changeover for many years thereafter.

This Stuff Works

At a gummy vitamin manufacturer in Pennsylvania, I was asked to facilitate a team of mechanics responsible for supporting and maintaining the manufacturing operation. They had difficulty keeping their maintenance area compliant with strict food production regulations. Our goal was to develop a system to guarantee compliance, while improving their ability to service their customers.

On the morning of the first day of the Kaizen event, I taught Lean principles and how 5S is used to optimize safety and productivity in a space. It all sounds good in a classroom. The team wondered how it applied to their situation. After training, we took a Gemba walk through their workspace. They thought they were in pretty good shape. The space was cluttered and lacked any hint of organization. They had nothing to compare to and hadn’t been exposed to other examples of 5S in the facility. After generating ideas in their work area, I took them to two locations in the plant that had used 5S: a production line and the Weld shop.

Our first stop was the production line. I asked one of the technicians operating the line to give the team a tour and point out what they had done and the benefits he had seen. He obliged and described 5S and its benefits as best he could. Team members were paying attention to what he was saying, but asked few questions and wrote fewer notes. I thanked the technician and took the team to the Weld shop.

On our way to the Weld shop, I asked team members what they thought of the production line. Feedback fell into two categories:

1. It looks pretty good.
2. I can’t see how it applies to our area.

I knew the next tour stop would be more inspiring. I was intimately familiar with what was done in the area. I could provide a more compelling review for the team.

When we got to the Weld shop, I noticed Jimmy working on a project. He was the team leader when we applied 5S to the Weld shop.

Jimmy: “What are you doing here?”

Me: “This is the Kaizen team from the gummy vitamin maintenance area. I’m giving them a tour of the Weld shop and showing them what your team accomplished.”

Jimmy: “Okay, just don’t get in the way. I’ve got lots of work to do.”

Me: “Thanks Jimmy. If you want to give the tour or share your thoughts, please do.”

Jimmy: “That’s fine. You can give the tour.”

Jimmy is not someone who likes to speak in front of groups or work with teams. Jimmy is also one of those folks who isn’t a fan of management or consultants. But, if he believes in something, it’s useful and helpful to him and others. He doesn’t give out compliments often (ever?) and doesn’t fall in line and do whatever he’s told.

I started the tour pointing out various ideas and improvements the Weld shop Kaizen team made six months earlier. Jimmy was paying attention to what we were doing, but didn’t say a word. I think he was interested to see how I’d describe the work of the Weld shop team. I did my best to represent their efforts and as I did, you could see the pride grow in Jimmy’s face.

My next stop on the tour was at the tool board created by the team during the Kaizen event. As I started describing and demonstrating the use of the tool board to the team, Jimmy got more and more interested. My new team was asking many questions and taking notes on my responses and their observations.

Rob (team leader): “This looks good and all. Does it really stay this way?”

Me: “I don’t think they cleaned up for us.”

Ben (team member): “Does this really work?”

Jimmy: “Look, this may sound silly and it may sound stupid. This $#*% works!”

This was the moment of clarity and credibility for the team. If Jimmy thought so, it must be so. I stopped the tour. The team had seen everything they needed.

I thanked Jimmy and took the team back to the meeting room to review their observations and ideas. On the way back, I challenged them to beat the results of the production line and the Weld shop. They told me they were up for the challenge.

The rest of the week, the team did amazing work, identifying the critical tools needed (All Tools Available), giving them the most visible and logical homes (Visible Evidence) and even telling the leadership team what they needed them to do to sustain the efforts from now on (Layered Audits and Accountability). I am not sure their area was any nicer or better thought out than the Weld shop or the production line, but they thought so, and that’s all that matters.

You’re Never as Good as You Think You Are

Of all the Kaizen events I have facilitated, there is nothing like 3P. It’s the most exciting, energizing, and exhausting way to create breakthroughs with a team. 3P stands for Production Preparation Process. The idea is to design a new product or process with the least amount of waste possible.

Production Preparation Process uses an eleven-step method to open people’s minds to what’s possible and make them as creative as their 8-year old selves. The technique was invented by Chihiro Nakao, a legend in the Lean community.

I was first exposed to 3P by consultants in 2010. We used the technique to design a new product in half the time it would have taken us to using our standard product development methods. I had the opportunity to facilitate half a dozen 3P events and was able to achieve similar breakthroughs with other teams.

I was always curious about the thinking behind 3P and had the opportunity to participate in a 3P competition, run by Sensei Nakao’s company, Shingijutsu, in 2013. During the week, I was able to pick up the nuances and deeper thinking behind 3P. I realized I had been taking shortcuts during the events I facilitated and because of that, we were diminishing our breakthroughs and results. I didn’t get to meet Sensei Nakao at the competition, but gained a deeper respect for the man and his thinking. I decided I would have to meet him one day, if the opportunity arose.

Meeting the Sensei

In 2016, I found out there was an opportunity to meet Sensei Nakao, as Shingijutsu was running another 3P workshop at a plant in Connecticut. He was the overall sensei for the week. I convinced three other coworkers to register for the workshop and we drove up to Connecticut together. During the drive, we discussed our expectations for the session. I wanted to learn from the master, but I also decided I had to have the ultimate tourist experience: be scolded in Japanese by Sensei Nakao.

The host plant made parts for the aircraft industry. More than sixty people signed up for the workshop. We were divided into eight teams, each having a part of the process to improve using 3P. After some initial training in Japanese (with English translation) by Sensei Nakao, teams were assigned a sensei (facilitator) and toured their area of responsibility.

I had met my sensei at the 2013 competition. He chose me to be on his team for that reason. He also knew I had some experience in 3P and its facilitation, so he gave me more responsibility than the rest of the team.

We took a tour of the operation and spent many hours on the factory floor, engaging with the technicians and gaining deeper understanding of the process. By the end of a very long first day, I was exhausted and glad when the team dinner was over. I knew I would need a good amount of sleep to prepare me for the next day’s activities. I felt confident, having much experience with 3P. What could they throw at me that I hadn’t seen before, I wondered?

Go to Gemba

The next day, after a quick review, the team went back out to the factory floor to gather more data and test ideas. I was asking an operator some questions when our sensei motioned to me. He asked me to join him away from the line. He was working with another team member and wanted me to help facilitate the next step of the eleven-step method. They were drawing some pictures on a large piece of paper taped to a wall, just fifteen feet from the production line.

As I was helping my teammate at the wall, I felt a tap on my shoulder. I looked up and it was Sensei Nakao. He didn’t look happy. I got my wish. I was being scolded in Japanese! I only understood one word: Gemba. The interpreter told me that I should be spending more time in Gemba and not away from it at a wall. All learning was to be done in Gemba. There was nothing I could say, but I could see my sensei looked uneasy.

Achieving My Goal

My sensei must have said something to Sensei Nakao, as he was taken aside and spoken to in Japanese. He looked like a beaten puppy. When Sensei Nakao finished with him, he left and went to visit with the next team. I waited a few minutes and then said to my sensei, “You got scolded, didn’t you?” He looked at me sheepishly and finally admitted he had. We both laughed. I had realized my tourist objective.

The rest of the week was a blur. We were able to solve the problem we had been assigned. I learned deeper meanings of 3P and was able to bring back refined skills to my company. I continue to learn more about 3P. No matter how many 3P experiences I have, I can always do better. Sensei Nakao’s scolding reaffirmed it.

It’s Better to Beg Forgiveness than Ask Permission

In 1998, I was invited to Hoogezand, the Netherlands, to help a team make improvements to their ceiling tile production line. Little did I know it would be the longest Kaizen event in my life. I had been to the plant three months before and identified significant changeover time reduction potential. It was time to put my money where my mouth was. In advance of the trip, we identified members of the team and the need for an interpreter. I didn’t speak Dutch and still don’t. We’d have two weeks to work on the line and were to coordinate with the Production Manager any time we needed to shut the line down to work on or test the equipment.

I arrived in the Netherlands on Sunday and met with the team in a conference room on Monday morning. After introducing myself, getting to know each of the team members, and providing some Lean and changeover reduction training, we took a tour of the line to identify the highest priority areas to improve and also to get a sense for the team’s interests.

The line wasn’t running very well and I was informed this was typical. Most of the equipment was in need of repair and the maintenance department wasn’t in tune with the needs of the production organization. I told the team I wanted to meet the Maintenance Manager. They looked at me like I had asked for something outrageous. When he came out to the line, I could see why they were a bit apprehensive.

Progress vs. Paperwork

Ullrich was a very tall German man, perhaps six foot eight (I am five foot seven on a good day). With a shaved head, hands twice the size of mine, and a very low and stern voice, he introduced himself by grabbing my hand and saying, “You vill not touch or modify any equipment without filling out the proper paperwork!” Taking my hand back before it was crushed, I assured him we would follow the rules. Although he didn’t seem satisfied, he left to go to the maintenance office.

Realizing we couldn’t fill out paperwork while we were making our improvements, I promised the team I would fill out the forms at the end of each day. The team didn’t look like they believed me, but knew I didn’t want any broken fingers. There were so many problems on the line. Two weeks weren’t enough time to fix everything. With focus, dedication, and proper prioritization, I was sure we’d make significant progress.

The top priority of the team was to improve the reliability of the equalizer, which cut the ceiling boards into finished tile dimensions. Operators had a difficult time setting up the proper cutting sizes. It took hours for them to get the proper cuts. We asked the Lead Operator to shut down the line, to allow us to assess the situation and find out why it was so difficult to set up to the proper size.

Five minutes later, the Production Manager came by to find out why the line was shut down. We told him we were trying to figure out what was keeping the equalizer from being set up consistently. He reminded us we were supposed to let him know any time we were going to shut down the line. I apologized and said it wouldn’t happen again. Knowing it probably would happen again; I advised the team to remind me to let the Production Manager know our intentions before shutting the line down. They promised they would. I wasn’t so sure.

Asking the Right Questions

The equalizer used precision screws to guide the saws to their final positions on the cutting bed. Operators turned a handle to move the saws on the screws. Watching the saws move as the handle was turned, I could see the saws weren’t moving consistently. With the first full turn of the handle, it appeared the saw moved twice as far as it did with the second full turn of the handle. This situation had to be resolved. First, we had to figure out why things were acting in this way.

We tracked down a dial indicator with a magnetic base. We wanted to see how much variation was occurring when we tried to move the saws. On our first test, the handle was turned one full revolution and the saw traveled 0.020”. We turned it one full turn in the opposite direction and the traveled just 0.005”.

The team was convinced the precision screw had worn down, causing variation in movement. Thinking about this, I knew this should not be the case, but I also know what my eye had seen. Then I asked the question, “What is riding on the precision screw?” It turns out it was a brass bushing. My next question was, “Which component is more likely to wear down, the brass bushing or the hardened steel precision screw?” It had to be the brass bushing. My next question was, “When was the last time the brass bushings were replaced?” No one remembered it ever happening.

We tracked down Ullrich, explained the situation and found enough brass bushings to replace all of the assemblies on the equalizer. Four hours later, we had replaced bushings worn down to the nub with brand new brass bushings. After, we tested out changes and now had saws able to repeat their locations within 0.001”. Ullrich reminded me to fill out the proper paperwork, but was impressed enough to shake my hand. This time, he didn’t crush it.

Making Progress and Earning Trust

Over the rest of the first week, we made similar improvements to all areas of the line. We never filled out the paperwork in advance, but our earlier success at the equalizer reduced the pressure on me, the team, and my hands. We also made a game of shutting down the line and then betting on how long it would take the Production Manager to show up to see what we were doing. We were improving so many things so quickly he also gave us the leeway to shut the line down without approvals, but kept playfully reminding us to follow the rules.

The team enjoyed the work so much they decided to work on Saturday and then take Sunday off. I took Sunday to go sightseeing and got lost in the village of Makkum, 80 miles to the west, known for their ceramic tile craftsmen. That’s a story for another time.

Monday, the team was ready to make more improvements to the line. We improved almost every part of the production line by Friday morning. Our report out was scheduled for Friday afternoon. The entire plant staff showed up at the production line and listened to the team explain and show their improvements in Dutch. At the end of the report out the team said, “Adam leerde ons dat het beter is om vergeving te smeken dan om toestemming te vragen!” After much laughter and clapping by the staff, Ullrich, and Production Manager, I was told the translation was: “Adam taught us that it is better to beg forgiveness than ask permission!”

Let It Go

In 2010, Armstrong World Industries emerged from bankruptcy. A minority stake of the company was bought by a private equity firm. This firm knew there were many improvement opportunities and brought in consultants to help create a culture of continuous improvement across the global organization. Their approach was to hold many Kaizen events on a weekly basis, exposing as many people to the principles of Lean as quickly as possible.

Having recently completed my assignment as the St. Helens Oregon Operations Manager, I was asked to provide support to the consultants. Sometimes I co-facilitated Kaizen events with the consultants. Other times, I was asked to facilitate Kaizen events independently of the consultants. This story is about one of the first Kaizen events held at the Marietta, Pennsylvania ceiling tile plant.

Paired with a consultant, I co-facilitated a team using 5S to improve the safety and productivity of their packaging area. 5S stands for: Sort, Set in Order, Shine, Standardize, and Sustain. Using this methodology, teams take a step by step approach as they make quick and meaningful changes to a target area. Lean was new at the plant, so we provided extensive Lean training to the team. The team was comprised of line operators, mechanics, a supervisor from the area, and a few staff members.

After the training, we took the team out to Gemba (the place where the work is done) to assess the materials that were no longer needed in the area. This is the first S, Sort. During Sort, the team is to decide what is absolutely necessary and what is clutter. The clutter is then disposed of or removed from the area. Once done, the team then moves on to Set in Order. The packaging area was built twelve years earlier and it was apparent most things in the area were from the first days of production.

A Case of Clutter

Many of the team members were having a difficult time finding things to dispose of. When something was found that didn’t look current or relevant, people would say things like, “We may need it in the future.” Or, “If we fixed it, we could use it.” After a few hours in the area, it didn’t look the team was willing to take a leap of faith and remove much of the unused and unusable equipment and materials.

The consultant and I stepped away from the team to discuss a strategy. “Adam,” he said, “we need to demonstrate it’s alright to remove and dispose of the clutter. Let’s pick a few things to remove, do it ourselves, and see if we can get others to join in.” I agreed, knowing we had to demonstrate it was okay to do something drastic to get breakthrough results. We took a walk around the area and found a few items that looked like they didn’t belong and then happened upon something that definitely needed to go.

Underneath a platform was an old rolling toolbox, covered in dust. Except it was unable to roll. One of the wheels was missing. When we looked through the drawers, all we saw were various nuts and bolts covered with years of grease and grime. The toolbox hadn’t been used in years and it looked to be an ideal candidate for the dumpster. It was pretty heavy, so we asked one of the team members to assist us as we pulled it out from under the platform. After getting it out, we placed it on a skid, ready to be taken away by a forklift.

A Toolbox Road Block

Except we couldn’t. Just as soon as we had called for the forklift, the supervisor on our team came at us with an angry look in his eyes. “What do you think you’re doing?” We explained what and why we were doing what we were doing. His face turned red. “I bought that toolbox for $300 and it’s served us well. I can’t believe you would just throw it out. We could fix it and use it.” When we pointed out the three new, clean rolling toolboxes in use in the packaging area, he stormed off.

We decided to talk with the rest of the team members. They told us no one had used the toolbox in years, the other toolboxes were sufficient, and the materials inside the old toolbox were of no use to them. They agreed to dispose of it and started to find other things in a similar condition to be removed as well.

The supervisor didn’t return that day. At the end of the day, the consultant and I were called to the Plant Manager’s office to talk about what had happened. The supervisor had stopped by the office earlier. After describing what we had done and the reaction of the supervisor and the team, we were told to tone down our approach. Lean was new to the plant and the people working there, and not everyone was on board. The supervisor was very proud of his accomplishments, helped design the packaging area, and took ownership for everything in the area, even the broken-down toolbox.

The Plant Manager told us it was more important to get the whole team engaged, rather than take extreme measures to prove a point. We agreed, and after leaving what felt like the principal’s office, we developed our strategy to reengage the team and improve relations the next day.

Taking a New Approach

The next morning, with the full team in a meeting room, we apologized for taking such drastic actions. We promised to get full team approval before making any more changes. When the team went back to the packaging area, they were energized. The consultant and I were able to step back and let the team make all of the organizational decisions in the packaging area. By the end of the week, the team removed more than 80% of the supplies, tools, equipment, and materials in the area. What remained was logically organized, in pristine condition and very visual. It was easy to see the condition of the area and if anything was out of place.

After a tour of the area, plant leadership remarked how much better everything looked and felt. Team members talked about the impact of the work and how it would benefit them in their normal jobs. This was the first of hundreds of Kaizen events at the Marietta ceiling plant over the next decade. Everyone learned valuable lessons. But I may have learned the most valuable lesson of all – pay strict attention to the team and understand what engages and motivates them. Even small changes are important; you don’t have to shoot for the moon every time. As long as the team owns the change, it will be sustained.

Virtual Kaizen Events

For many years, I have led, facilitated, or participated in hundreds of Kaizen events. During those events, people worked together in the same location to solve important problems. Sometimes team members traveled to the location of the event. Other times people weren’t able to travel to the event and the team carried on without identified experts. I loved the interaction and energy of those events, but wondered if there might be a way to hold an event that was as effective as putting people in the same room, but would be less difficult from a travel or logistical perspective.

This year, out of necessity to work virtually, I challenged myself to develop a virtual version of a Kaizen event, and I am excited to say that I have been able to emulate the elements of my traditional Kaizen events and even believe there are some logistical advantages to the virtual Kaizen event. I now realize that it may be advantageous to consider a virtual Kaizen event and want to give you an image for what that can look like.

First and foremost, the team can come from anywhere, across any time zone. As long as they have an internet connection and some basic video conferencing technology such as Zoom, Microsoft Teams, Google Meet, or the many other options available these days, they can be part of the event. Most of the aforementioned technologies are free or have a minimal cost. Not bad when you consider the cost of travel. There are a number of software platforms that help the Kaizen facilitator (me) integrate with the video conferencing software and allow for and enhance collaboration during the Kaizen event.

Next, the topic of the Kaizen event is not limited to correcting virtual problems. While it might be a stretch to say that a virtual Kaizen event could be held to make equipment modifications or reducing physical effort or reducing changeover time, I am sure with some creativity it could be accomplished. More likely topics could include: strategic planning (VSM), cost reduction ideation, standard work development and improvement, business process improvement, process mapping, and many others. A successful Kaizen event must be chartered, so everyone is aligned around the effort and committed.

The flow of a virtual Kaizen event looks very similar to one done on site, and I have verified that all of these aspects can be accomplished virtually and efficiently. For your reference, here is the typical flow of a Kaizen event:

1.       Sponsor kickoff

2.       Background of the problem to be solved

3.       Charter review

4.       Voice of the customer

5.       Lean principles overview

6.       The Wheel of Sustainability explained

7.       Gemba Walk of the Current State

8.       Identification of the top pain points in the Current State

9.       Brainstorming of opportunities to reduce/eliminate the pain points

10.   Prioritization of the opportunities

11.   Visualization of what good looks like in the Future State

12.   Work on the top opportunities in sub-teams

13.   Reviews of progress to achieve synergies across the total team efforts at multiple times during the event

14.   Application of the Wheel of Sustainability and Lean principles to the work

15.   Finalization of all work – testing against event objectives and the Wheel of Sustainability

16.   Road mapping of any outstanding work and implementation planning

17.   Report out to sponsor(s) and other stakeholders

18.   Team recognition

Just a note or two about how technology can be used during the event. If a physical Gemba walk is needed, assigned team members can take their smart phone or a Go Pro or something else with them that can transmit to the team in real time. Also, they can answer questions during the walk or engage with others doing the work during the walk.

I have also reconsidered how a full day in a virtual Kaizen event might have to be managed, especially for those working from home. Sometimes you have to tend to your family, your pet, or yourself. So, we would have to be quite flexible around how breaks are managed. But, that can all be sorted out prior to the event. If nothing else, the past few months have taught me to be much more open and flexible in my thinking. But isn’t that what continuous improvement is all about?

For those of you who have put off Kaizen events in your business due to the current situation, I encourage you to consider trying a virtual Kaizen. If you wait too long, competition will pass you by. I would love to help you stay ahead.

Call 911

In 2005, a ceilings manufacturing plant on the West Coast was experiencing high downtime rates. I was asked to come to the plant and run a Kaizen event to reduce the impact of downtime on the plant.

I was given a small team consisting of four production technicians, two mechanics, one electrician, one engineer, and one supervisor. Our mission wasn’t to solve the specific mechanical or electrical downtime problems, but rather to understand why the response to and recovery from downtime took so long. This was a new concept for the plant and for me, but we felt we were up to the challenge.

On the first day, after getting to know everyone and aligning around our mission for the week, I trained the team in Lean principles. After the training, we decided to walk out to the shop floor and gather feedback from technicians, mechanics, electricians, engineers, and others impacted and frustrated by the downtime in the plant. Almost to a person they told us they felt there was a basic training issue related to the skills of the mechanics and electricians that serviced the lines and didn’t understand why the plant didn’t invest more time and training in their people.

Not satisfied with this and knowing we wouldn’t be able to train all mechanics and electricians during the week; I knew we had to look for other issues we could impact. Back in the meeting room, the team discussed other reasons they thought downtime was so high. After a while, it became apparent we were just finger-pointing and guessing. So, I proposed an experiment. I suggested we stage a downtime event and then observe it from all angles. We would observe the technician making the call for help, the mechanic taking the call for help and others who were involved with the downtime event. Three team members went to the maintenance shop, two went to the supervisor office, and the rest of the team stationed themselves at the point where the downtime would be staged.

One hour later, with everyone in position and the crew aware of our experiment, we staged our downtime event, which was designed to be an electrical fault in one of the paint dryers. After a few minutes of trying to correct things, the production technician made a call to the maintenance shop to tell them about the downtime event. Five minutes later a mechanic and electrician came out to the line. They looked a bit bewildered. The technician that called them wasn’t around, he had gone to the breakroom. It was hard not helping the situation get resolved, but we were observers and had to let things play out naturally.

Ten minutes later, the technician came back and told the mechanic and electrician about the downtime issue. They realized they didn’t have the tools they needed and went back to the shop. Minutes later, they returned and found the technician, who directed them to the location of the downtime. They were on the wrong side of the line, so they carried their tools over a series of steps in order to get to the area to be worked on. They looked annoyed.

About five minutes later, the line was back up and running. The team went back to the meeting room to assess the full downtime event. It turns out that the line was down for more than thirty minutes, of which five minutes was the actual repair and restart of the line. Twenty-five minutes was wasted effort, waiting, and frustration. After a review of Lean principles and much heated discussion, the team came up with a solution to improve the effectiveness of downtime response and recovery. In essence, they crafted three questions to be asked and answered at the time of any downtime incident. They were:

1.       Who am I speaking with?

2.       What is the downtime issue?

3.       What is the exact location of the issue?

The team realized they were essentially creating a script, much like those used by dispatchers during 911 calls. By answering these three questions first, they could reduce the efforts and frustration of the maintenance team by helping them identify the tools and skills they would need, direct location to go to and who their point of contact was. The team also agreed the person making the call shouldn’t leave the area until the maintenance team arrived.

Knowing that they were creating a new way of doing things in the plant, they decided to make it easy for everyone to use. They posted signs at every phone on the manufacturing line in the plant and also in the maintenance shop and engineering offices. They also trained the crews and management and demonstrated how downtime calls should look.

Over the next few weeks, team members were assigned to different locations and helped out any time a downtime event occurred, ensuring the three questions were asked and answered. It took a while, but eventually it became a habit in the plant. Not coincidentally, downtime and general frustration were reduced. The simple communication not only improved productivity but also teamwork between the production and maintenance departments.

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

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

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

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

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

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

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

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

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

Best Event Ever

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

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

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

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

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

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

Macon Progress

Once upon a time in 1998, I helped a team in Macon Georgia improve the reliability and safety of one of their production lines. The work was exciting, the team was enthusiastic, and we were making breakthroughs beyond what I ever imagined could happen. Something was missing, however. For some reason our sponsor, the Business Unit Manager, never came out to the line to see what we were doing. Although the team didn’t seem to mind, it really bothered me. After all, we were doing things so quickly and effectively, and solving so many problems that others weren’t able to solve, I wondered why he didn’t appear to be interested in our progress. If you know me, you could predict I would do something about it. And, I wouldn’t be subtle about it.

On the evening of the first day, after the team left, I went to the sponsor’s office. I wanted to see if I could convince him to come out to the line the next day while we were doing our work. I thought his visit would reinforce the importance of the team’s work and might also show him what his people were capable of accomplishing when empowered to do so. During our discussion, I shared my observations of the team’s progress and how well they were working together and being open to changes in thinking. Then I asked him if he thought he might have some time the next day to join us for a while, so the team could show off their accomplishments. He informed me he would be tied up in meetings all day and might check things out when he had time. I left his office a bit frustrated, but hoped he’d stop by during a break, even though he made no commitment to do so.

The next day, the team made even more breakthroughs and were extremely proud of their efforts. We were having fun and people from the crew and the maintenance department came by to see what we were doing. It made the team feel good that people were noticing their work. By the end of the day, we still hadn’t been visited by our sponsor or any member of the management team. It didn’t feel right and I was determined to do something about it. I wanted to visit with my sponsor that evening, but I found out he had left the plant early to play golf or watch a high school baseball game, or something else that was a higher priority for him. I was getting really frustrated and probably should have left it alone, but I couldn’t.

On the third day, during a break, I decided to walk to the sponsor’s office and spend some time with him, if possible. Luckily (or unluckily), he was in his office and agreed to spend a few minutes with me. I started off by describing the great effort of the team. He listened to what I had to say, but seemed to be waiting for what I was really there to discuss. I then talked about how the team had been visited by others and how it seemed to drive enthusiasm and pride in the team. Finally, I told him that although it was great to have his sponsorship to do this work, it was disappointing that neither he nor the management team had come out to the line at any time during the week. I understood how busy things were at the plant, but I also felt it would be impactful for him to visit and demonstrate his commitment to the efforts of the team during the week.

I could tell I had struck a nerve. “Adam,” he said, “If you are questioning my commitment, you can do it from Lancaster (corporate headquarters)!” At that point, all I could do was try to dig myself out of a pretty deep hole. I really don’t remember what I said, but I wasn’t fired and I wasn’t sent home, so I guess that’s a win. I tried not to let my disappointment show to the team and the rest of the week we continued to make amazing breakthroughs. At the end of the week, we were able to get some management team members to join us for a tour of the changes. The sponsor showed up too. To this day, I don’t know if he would have showed up without our conversation, but I learned an extremely valuable lesson in that moment. I needed to develop a process to align with leadership and gain their commitment.

Now, many years later, I am able to provide the image of commitment to leadership teams. I illustrate what’s going to happen, how they can support team efforts, and what’s expected of them. Then, I can look the leadership team in the eyes to see if they are willing to commit. There have been times that I have had to walk away from an assignment or a potential client engagement, as it became clear they wouldn’t commit as much as I believed was required. It’s hard to walk away from a paying job, but I feel like my role is to give teams the best chance to win. If I don’t think they have the support to do that, I don’t want to subject them to a frustrating experience.