Surviving a Brutal Work Environment

I have experienced two mergers/joint ventures in my corporate career at Armstrong. The first one was a ceiling grid venture between Worthington Industries and Armstrong. It was extremely positive and productive and is still doing well to this day. The second one was a ceramic tile venture between Armstrong’s American Olean Tile and Dal-Tile, based out of Dallas Texas. This one didn’t go nearly as well. I learned many lessons from the Dal-Tile experience, mainly about my ability to survive.

When the “merger” was announced, I investigated other opportunities for my career, including a chance to go back to Thomasville Furniture as an assistant plant manager in Winston Salem, and an offer to do work at Armstrong’s corporate center. My recent experience with the Worthington and Armstrong joint venture was positive and I learned a lot at the beginning of the venture, so I thought I would see a similar approach to this combination of companies. Boy was I wrong.

Our Plant manager left us without saying a word. We only found out a week or so later he had gone to the Dal-Tile headquarters to prepare for the merger through a mysterious sounding voicemail. On the official first day of the merger, executives came to our plant and told the acting plant manager he had to fire five staff members by the end of the day.

I was the industrial engineering manager at the plant, and the only way I survived was that I was named as a supervisor. Dal-Tile only staffed their plants with plant managers, supervisors, and ceramics engineers. Any other staff was excess in their view.

I took the supervisory role because I was promised a job at the corporate headquarters in Dallas Texas. My favorite manager from American Olean would be my manager in Dal-Tile corporate. Even though things were challenging at the plant, I had something exciting to look forward to.

When I got to Dallas Texas, I found out we were in charge of assuring environmental, health, safety, and mining compliance across the entire company. There was a department responsible for this already. But they weren’t very helpful to the manufacturing and mining sites. The VP of operations put us in the middle of the plants and them.

We tried to work with the existing EHS and mining group, but they went to great lengths to avoid us. One time, my manager and I walked over to their offices to meet with them impromptu. Instead of meeting with us, they locked their offices and refused to talk with us. What a culture!

Another thing Dal-Tile was proud of was their firing practices. The employee manual started off with a paragraph explaining that Texas was an “at-will” state, which meant they could fire you at any moment, with or without justification. This was on the first page of the manual! I met many people who had been fired and then re-hired and then fired again. Amazing.

I knew the only way I was going to survive this brutal culture was to make myself as valuable and helpful as possible. I took every assignment, put in outrageous hours, and traveled at the drop of a hat, to support any of our twelve manufacturing facilities and multiple mining sites.

I had good relationships with the plant staff. Once they got to know me, they trusted me. They didn’t trust the EHS and mining group, that was for sure. They knew when I arrived, I would be there to help. Nothing more and nothing less.

I had many amazing experiences I would never have had in a more positive working environment. But, after 18 months, I was free to return to Armstrong (there was an agreement that we were off limits for that period of time). I made a few calls and was able to join the corporate group in Lancaster, working for the same manager I followed to Texas. He had left a month or so earlier and was able to convince his manager to hire me.

When I returned to Armstrong, I realized most people wouldn’t believe how we were treated at Dal-Tile. They never experienced a brutal corporate culture. So, I kept the stories to myself or commiserated with those few who survived their time in Dallas Texas and returned to Armstrong like me. Very few made it through unscathed. Those that did had some scars from the battles we fought but were also proud that we made it.

To this day, Dal-Tile is my example of “if you think your job is bad, check this out.” No one should be treated the way we were. Because of this, I really appreciate what I have and my determination to survive.

Five Tips for Effective Meetings

Have you ever had a meeting where it seems like nothing was accomplished? Is every meeting this way for you? Do your meetings start late? I have facilitated hundreds of meetings and Kaizen events and have learned over the years these five key tips to an effective meeting.

1.      Define the purpose.

2.      Create a clear agenda.

3.      Facilitate the meeting.

4.      Set expectations.

5.      Hold accountability for actions.

Define the purpose of the meeting.

Why are we meeting in the first place? What are the expectations for the team members in the meeting? Why are they there? If everyone knows why they’re there and what’s expected of them, they will more likely prepare and engage in the meeting. It also makes it easier to choose team members for the meeting. Simply put, if someone is not aligned with the purpose, they shouldn’t be invited.

Create a clear agenda.

The path from the beginning of the meeting to the end should be mapped out. How do we get to a decision as a team? What information will be shared? Who is expected to share it? What preparation should happen prior to the meeting? Does the agenda lead us to our purpose? Taking the time to create an agenda helps to remove any of the excess or unnecessary parts of the meeting, resulting in shorter, more focused meetings.

Facilitate the meeting.

Don’t leave things to chance. Someone should run and manage the meeting. This person can help the team stay on track, not wandering “into the weeds.” It’s best to use a facilitator who isn’t deeply invested in the topic being covered, but that may not be practical. Facilitation is a skill that’s highly valued, so rotating this responsibility will help team development.

Set expectations.

Start and end on time – that’s the first expectation of any effective meeting. It seems so simple, but we let things get in the way of being punctual. Other expectations should be shared as ground rules for the team. Examples include: One voice at time, be open to others’ views, work collaboratively, no calls or texting during the meeting, and others the team may develop. If anyone breaks a ground rule, the facilitator should call them out immediately and correct their behavior. The sooner this is done, the more serious the rest of the team will take these expectations. Following ground rules is a sign of respect for the team and the topic being discussed.

Hold accountability for actions.

Every meeting should have an outcome. Sometimes it’s the sharing of critical information. Other times, there are action items that must be completed. Team members should know what they’re accountable for and be responsible to meet their obligations. Therefore, assignments should be listed visually, with owners and due dates. Updates should be a part of the meeting agenda. Don’t wait until an assignment is due. You want to make sure the assignment owner has a chance to complete his/her task(s). If they’re on track, thank them. If not on track, provide help.

These tips work. It takes a while for the team members to get used to them. But once they do, your meetings will be more productive, effective, and engaging.

Leadership Commitment in a Most Challenging Situation

Last year, Dave, a network connection, reached out to me to see if I could help him in his continuous improvement journey. His wife had worked with me at Armstrong, and one evening he was talking with her about some of his frustrations at work. She said, “If you want to get the right help, call Adam. He is tenacious and won’t let you or your team fail.”

Dave invited me to his factory, which was quite large and had several furnaces that smelted and poured molten metal into ingots for high value customers. They had a problem with tools and equipment going missing, which led to significant productivity losses. He wanted to reinitiate and strengthen their 5S program. I knew I could help, and wrote a proposal for the work, which was approved quickly.

We scheduled the Kaizen event for eight weeks from my initial visit. This would allow Dave to prepare leadership and gather the proper team for the Kaizen. We had already chartered and scoped the event to cover one of the furnaces. Our idea was that our improvements could be replicated to the other furnaces in the facility.

In the meantime, I spent a day at the facility getting required safety training and preparing Dave for the event. We picked a conference room and identified the supplies necessary during the week.

Three days before the Kaizen event, Dave called to tell me he had contracted COVID. I asked him if he wanted to postpone the Kaizen. He told me no and if I could pick up the supplies from his home (in his driveway), one of the team members would fill in as team leader until he could participate at the facility. He would use Zoom to attend and participate on the first day of the Kaizen. His five-day isolation period would then end, and he could attend in person on the second day, but would have to wear a mask.

I wasn’t sure what to make of this. All my Kaizen events (up to that time) were in-person, and I didn’t really know how engaged Dave could be attending virtually. But I was willing to give it a try and make the best of it.

On the Sunday before kick-off, I met Lisa, who was going to fill in for Dave as team leader. She helped me prepare the meeting room. We talked about how we could engage all team members, including Dave on the first day of the Kaizen. We set up a laptop for Dave that we could point toward the team and the screen, so that he could engage with the team and keep up with the discussions. Luckily, he and I had spent time in the workspace, so he had a list of ideas to share during that portion of the Kaizen.

At kick-off on Monday, we introduced everyone and shared Dave’s story and said we were going to make the best of a difficult situation. For Dave’s part, he stayed on Zoom the entire time, engaging and speaking with the group at appropriate moments. When we went out to the facility floor, Dave waited for us to text him that we were returning to the meeting room. The team had many ideas and Dave was able to share his as well. When we prioritized the many ideas into a vital few, Dave was able to participate as if he were in the room. We took the laptop over to the list of ideas and Lisa voted on Dave’s behalf.

Now it was time to work on the high priority projects. Dave couldn’t really do that, so he signed off until we met to wrap up for the day. He listened intently to the team’s progress and gave them encouragement and told them he couldn’t wait to come in the next day and help them in their work.

The second day, Dave showed up with a facemask and kept his distance from the team members. He jumped on one of the project teams and was able to participate in the improvement work. Throughout the week, the team felt more comfortable letting Dave engage in the work and by the end of the week, he was able to help complete many critical tasks.

At the end of the week, the team had made significant improvements to their furnace area. We did a quick estimate on the impact on productivity and changeovers and felt we had made a huge impact on both. Time would tell, of course. For his part, Dave earned the respect of the team and had his first true win in his position as Continuous Improvement Manager. I was impressed by his dedication and commitment and was thankful we didn’t have to postpone or cancel this Kaizen event. I also learned it was possible to engage remote team members in Kaizen events.

A Picture is Worth More than a Thousand Words – It’s Priceless

Earlier this year, I received an email from someone I never met, asking about my approach to 5S – organizing a workspace to improve safety and productivity. He heard about me from another location in his company, who I helped six months earlier. Later that week, we were in a Zoom meeting, and he invited me to his factory in Oregon to see if I could help jump-start their 5S efforts.

Three weeks later, I was on a plane, heading to the west coast. I arrived early in the afternoon and met with Ben, my sponsor. We took a tour of the factory and strategized about my approach with the leadership team the next day. I saw many places where 5S and other Lean tools could help them out. People in the factory were engaged and appeared ready to take a first step on their continuous improvement journey.

That evening at dinner, Ben told me about past continuous improvement efforts. There weren’t many success stories shared. I was told one consultant had visited and said he couldn’t help them. I couldn’t understand how that was possible.

The next morning, Ben and I walked around the factory again. It helped ground me and remind me of the complexity of their processes. A little later, I attended the morning leadership walk around the factory. Although there were a dozen staff members attending, only one or two were engaged at any time. I took a risk and gave Roy, the facility manager, some feedback about how he might engage his staff more effectively. He took my feedback in stride (he didn’t kick me out of the plant, so that was a good sign).

After the leadership walk, Ben and I talked about what I had seen, and we prepared for the leadership review at lunch. We created a list of the top three areas that could use my help. There were unlimited opportunities for improvement at the facility.

At lunch, we crammed into a small conference room. There may have been a dozen people seated around a table designed for six. I introduced myself and thanked them for giving me the opportunity to visit and learn about their processes. I spoke about what I saw and where I thought I could help. I wasn’t getting much engagement from the leadership team and realized my words weren’t connecting with them. With a less than successful history of continuous improvement efforts at their factory, they were naturally skeptical.

That’s when it hit me – talk about the successful Kaizen event from their sister facility. I started describing the work I did with the team. We were able to reduce a critical changeover by many hours, leading to substantial savings for the company. The leadership team started asking some questions. Then, I asked Ben if he had the report out from the Kaizen. He projected it on the screen. Now the questions were flowing. People were amazed at the “before” and “after” photos. How did we do this? Is it still working? How might we apply a similar approach locally?

Next, Roy asked where I would start. I reviewed the three areas Ben and I had prioritized. Roy said those were good choices, but he preferred to start at the beginning of the process, where quality would be most affected. I was happy to oblige, as it was much more important to gain alignment than to worry about where to start. Ben agreed and now we were talking about when we could kick-off the first Kaizen event.

I said I would charter the event with Ben, and then we could review it for approval. From there, I would write a proposal and then, once receiving a purchase order, the work could begin. I normally like to think for 24 hours before writing my proposal. But speed was critical. After chartering with Ben, I found a quiet office to write my proposal for the Kaizen. Then, Ben and I met with Roy and we were met with enthusiastic approval. I left the facility with a purchase order. The following month, I ran their first “successful” Kaizen event. But that’s another story for another day.

A Challenging Place to Work

During Armstrong’s Lean transformation, we took many benchmarking trips to learn from companies that were further along in their Lean journeys. One memorable trip included visits to Boeing and Nucor Steel in South Carolina on an extremely hot day in July.

At the Boeing plant, we were amazed by the one million square feet of air-conditioned space where the newest Dreamliners were being assembled. These amazing aircraft were filled with the latest technologies and miles of wiring. Using Lean principles, everything came together in a choreographed way. The area was bright, everyone wore clean clothes, and no one looked like they didn’t know what to do. At the end of the tour, we were escorted through a gift shop and many of our attendees bought souvenirs to take home with them.

Our next stop was Nucor Steel. As we walked into the facility, the environmental contrast with Boeing was stark. It was dark, dirty, and hot. No air conditioning to be found. The Lean approach was almost the same as at Boeing. People were clearly aligned around critical metrics. They were following standard work, and everyone knew what was most important during their workdays.

We entered the furnace control room (which was air-conditioned) and were shown many cameras and monitoring devices that assured the steel wouldn’t have any contaminants. Everyone’s pay and bonus was dependent on the amount of quality tons of steel produced during the day. This aligning metric kept everyone focused on the most important thing their customer valued.

From the control room, I watched a worker on the deck of the furnace wearing a Tyvek suit. He was using a ladle to take a sample of molten steel to test its purity. As hot as it was in the plant, wearing a Tyvek suit had to add to the discomfort of his task. To make matters worse, there was a hole where the molten steel was sampled from. The heat coming off it almost pushed me back when I walked by.

I had to believe this task was one where workers rotated throughout the day, as no one could take the heat for extended periods of time. When I asked our tour guide about the job, he told me it was a high paying position. People in the plant coveted it. They would work anywhere from 8 to 12 hours a day.

I couldn’t believe it was humanly possible to survive a full day doing that job! I would’ve passed out in the first hour. Surely this was a mistake. I was told I could speak with the technician in-between the samples he was taking. My curiosity was strong, and I asked him about his experience. He told me it was his favorite job in the plant. He was assuring their customers were getting the highest quality steel possible. He did admit it was extremely hot, but he was used to it, having worked there for three years. I thanked him and rejoined the tour group, my mind blown.

As we walked out of the plant to our cars, I was struck by the cooling wind outside. It wasn’t until I saw the car register 103 degrees that I realized just how hot it was in the plant and the extreme lengths people go through to do their jobs.

Like a Pro

For the early part of their Lean journey, I was the interim Lean Leader for Armstrong World Industries’ Hilliard Ohio plant. I was returning to the corporate office in Lancaster Pennsylvania from my assignment as Operations Manager at the St. Helens Oregon plant. I spent two out of every three weeks at the plant, until my family moved from the West coast to join me.

During my time at the plant, we ran many Kaizen events and made impressive improvements to safety, productivity, quality, and customer service. We involved everyone, from hourly technicians to the highest plant management positions.

One week, we focused on changeovers at the main fabrication line. This line was responsible to reduce 4-foot by 8-foot boards to 2-foot by 2-foot tiles and many other sizes. After the proper size was achieved, panels received a finish coating of paint. The bottleneck of the changeover was the equalizer (table saw) that had to be changed precisely to the finished size of the tiles. Over the years, operators had marked the equipment with lines for the many different tiles that were cut on it. Unfortunately, these marks were interpreted differently by the personnel, and it caused extra scrap and time to get things into specification.

Our team was comprised of several production, maintenance, and supervisory personnel. One team member was Henry, the acknowledged equalizer “expert.” He was soft-spoken and meticulous. He liked to take extra time to dial the equipment in to the appropriate size, as it was critical to the customer’s expectations.

During the week, Henry made sure we didn’t sacrifice the integrity and repeatability of the equalizer. We realized we could make more consistent cuts if we precisely measured and pinned the top 10 sizes cut by the equalizer. Once the pin was in the appropriate hole, it guaranteed our tiles would be cut within specification without additional adjustments and testing. This was going to save tremendous amounts of changeover time. We labeled all pin holes, so even the most inexperienced technicians could easily and quickly find them, guaranteeing a consistent, quality ceiling tile. All changes reduced changeover time by more than half and reduced changeover scrap by more than ninety percent.

On the day of the report out, Henry said he didn’t want to speak in front of an audience. He didn’t know what to say and told us he was shy. This wasn’t surprising, but it was a requirement for everyone on the team to say something during the report out.

I encouraged Henry to tell the audience about holding the team accountable to protect our customers’ interests through cutting quality tiles. He said he would try to say something, but he couldn’t guarantee anything.

The report out started, and team members spoke proudly of their Kaizen event experience and how they had reduced changeover time, while improving quality, safety, and consistency. Then it was Henry’s turn. He started quietly. Yhen his voice rose as he shared his pride and ownership of the changes we had made during the week. Then he was lecturing the audience about the benefits of Lean and changeover reduction. It was as if he was the professor and we were the students. Five minutes later, he was done. We were in awe! No one had ever heard Henry speak so passionately. The experience had moved him, and it showed. I knew I wanted all my future team members to have a similar experience. I have honed my approach to create the same level of ownership and passion that I saw in Henry that day.

When You Want Something Done Right – Outsource It

I was asked to create a discrete event simulation program for a planned factory expansion many years ago at Armstrong World Industries. What is that, you may ask? Basically, it’s a computer model of a process as it operates. It tries to mirror the behavior of the process, allowing the user to try various “what if” scenarios, such as adding capacity, downtime, resources, or speed. Having not built any simulations since my college days, I started doing research on options and whether or not I should try to build it myself or hire an outside vendor.

No one at Armstrong had experience with simulation. The last person who did left the company three years before. The software he used was no longer available, and the owner of that company had died. I had to start from scratch.

After a few weeks of research, I found a simulation program called Simul8. It seemed intuitive and relatively inexpensive, so I bought a copy and started playing around with it. It didn’t take long to figure out I was in over my head! Instead of giving up, I found a company in Canada that was a licensed distributor and trainer for the software.

I signed up for a training course and flew up to their headquarters in Toronto. Because I had purchased additional coaching, I was able to get direct assistance on the project I was working on. During the week, I made significant progress on my simulation program and felt confident I would be able to complete the work in a reasonable amount of time.

When I got back to my office at Armstrong, I stayed focused on the simulation and from time to time, I would get stuck. The trainers were available to coach me through my issues for a fee, and eventually I finished the program.

We were able to simulate the plant expansion and try many experiments and “what ifs” related to various plant scenarios. Everything worked, except the program was slow. I knew that it was due to my lack of experience. I wasn’t using the power of the program and taking advantage of the shortcuts an experienced programmer would know.

That’s when I realized I could play a more valuable role for future simulation projects. Now that I knew the ins and outs of the program and what it was capable of, I could help other project managers assess whether or not simulation would help them deliver their projects in an efficient way. Then, if we agreed that it would, I would engage the experienced simulation programmers from Toronto and let them write the code in a much more efficient and logical manner.

It cost more money directly, but because their programs ran many times faster, we saved a lot more money in the long run. And, through the years, our vendor learned so much about our process, it took less time to complete the work for us.

The lesson I learned from all of this is that you can’t be an expert in everything, but if you can find the person who is, you can maximize your return by using their services.

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.

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.

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.

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.

Things Aren’t Always What They Seem

In 2011, Armstrong’s Marietta ceiling plant was utilizing technical resources and replacement workers to run the plant. Management and the labor union were unable to come to an agreement around their contract, and for seven months, the union workers were locked out.

During that time, I assisted with day to day production operations, maintenance activities, and many process improvements. I worked all over the plant, identifying and implementing as many improvement projects as possible. I was extremely motivated, as the projects improved safety, quality, and productivity for the rest of the plant. The work helped me through the long days, energizing me as I could see instant results from my efforts.  Others were mostly happy with my work. I say mostly, because not everything worked as planned or as expected.  This one of those stories.

The Lamination Line

One of the most critical lines in the plant was the lamination line. It put a top layer on the ceiling tiles. Customers were willing to pay a premium for these tiles. The lamination line was producing at a lower than budgeted rate and had a large amount of downtime. I decided to see if I could help reduce the downtime and increase the production rate.

When I arrived at the line, I met with Wayne, an innovation scientist who was running the line and teaching others to operate it efficiently. We discussed the issues causing line downtime and reduced output rate, then he gave me a tour of the line. On the tour, it became apparent that the position of the board as it enters the laminating process was most critical. I noticed boards were entering the process at an angle. Wayne told me most of the time the angled board could be cut into usable pieces and when it appeared to be too much of an angle, he would stop the line and make adjustments.

I took a look at the conveyer before the laminating process and noticed a series of angled rolls. These rolls were angled to move the board over to one side of the conveyer and keep it against a guiding rail. There were 36 total rolls along the conveyer, and of those, 28 were angled. I believed there were too many angled rolls. They were driving the board at an angle past the guide rail, keeping the board from entering the laminating process squarely.

A New Way to Roll

I asked Wayne if he was willing to try an experiment. I wanted to straighten out most of the rolls, leaving just a few angled rolls. The board would be driven to the guide rail using the angled rolls and then the straight rolls would keep it straight as it entered the laminating process. Wayne asked me how long it would take. I estimated four hours of effort with his help and the help of a mechanic. The line was scheduled to be down for maintenance the next day. If we could do the work then, he would be happy to help.

The next day we started the work with the help of a mechanic. We identified the center of the laminating process and positioned the guide rail parallel to the direction of travel of the board into the process. Next, we moved the guide rail to the optimal position to guarantee the board would be centered entering the process. We marked the original position and current position, just in case we had any issues. Next, we started straightening the rolls.

An engineer came by to see what we were doing. When I explained, he told me he had installed the laminator a few years back and was responsible for all of the angled rolls. He didn’t agree with what we were doing and tried to convince us to stop our work and put everything back. I assured him we were experimenting and were willing to put everything back to its original position if necessary. Although he didn’t seem satisfied, he decided to go elsewhere while we did our work.

Sometimes Less is More

After just under four hours, we were done. Before starting up the line, I called the engineer to see if he wanted to see the results of our experiment. He said he would come over later that day. We didn’t want to wait, so we started up the line and sent some test boards down the line. The first time, we had a jam. When we looked at the cause, we realized the new position of the rolls and the guide rail had an adverse effect on equipment on the other side of the line. We shut down the line and made some adjustments to take into account the new arrangement.

On our next attempt, the test boards entered the laminating process in a straight and square fashion. We were excited, but weren’t ready to declare victory. We started up the line and put it into production. We were amazed, the boards were not only going in exactly as we hoped, but they were spaced out more evenly as they came down the line. Wayne was excited and now wanted to speed up the line. He made small changes to speed until the line was running 20% faster than it had ever run. Right in the middle of this, the engineer came by to see what had happened. He was surprised things were going so well, but admitted he had angled so many rolls without considering the impact on the overall process. He then said, “Maybe less is more - too much of a good thing may be a bad thing.”

Over the next few months, we made additional improvements to the laminating process and the plant had a much more productive and safe operation than before we started.

Trust, but Verify

In 2005, I was asked to be part of a team to help Armstrong’s Mobile Alabama ceiling tile plant improve their performance.  Production output had steadily declined over the first few months of the year, and they were well behind budget.  The team was tasked with identifying and implementing improvements to the operation that would drive performance back to budget for the full year. The team leader called the effort a “Full Court Press”, meaning we would not give up until we accomplished our mission.

The Mobile plant had one board forming line and two fabrication and packaging lines. The board forming line was clearly not the problem, as the quality, productivity, and safety were well above budgeted performance. The fabrication and packaging lines were where the losses were occurring, so we agreed to focus our efforts there.

On our first day at Mobile, we attended the morning production meeting. We introduced the team to the staff and reviewed performance. The plant staff members were open to our help, but weren’t sure what we would be able to deliver in a short time. We assured the staff we would do our best and coordinate any efforts through them. Once the meeting ended, we took a tour of the fabrication department. During this tour, we observed many problems and spoke with operators, mechanics, and other staff to get feedback and ideas. Many were disappointed with the performance and hoped we would be able to help them turn things around.

Each of our team members had a specialty. One was interested in the programming used to control the equipment, another was fascinated by the coordination of materials and resources. My area of expertise was flow of materials through the production line. During the tour, I noticed many line-stops and jams. I knew I could provide help.

With the agreement of our team leader, another team member and I took a detailed look at one of the main fabrication lines. This line was led by a technician named Walter. Walter was extremely interested in what we were doing, and asked if he could tour the line with us. We were happy to have him along, as he introduced us to all of the crew members and lent credibility to our efforts. He also appreciated our approach of watching the line carefully to identify the causes of the line-stops and jams.

Something Isn’t Hitting Right

On our tour, we stopped at the punch press to watch its operation. Something didn’t look right to me. The press creates holes in the ceiling tiles which allow air and sound to enter the tile. It’s critical for the ceiling tile to enter and exit the press squarely and centered. Following the press, there’s a gate that stops the tile while the press completes its work. If the tile is angled, the edge of the tile gets damaged when it hits the gate. As I watched the tiles enter and exit the press, I noticed they weren’t exiting the press squarely and hitting the stop-gate at an angle.

I asked the press operator if he was concerned about the tiles hitting the stop gate at an angle. He told us he thought any damage would be cut out later down the line. It looked to me as though the amount of damage wouldn’t cut out completely, but the operator was convinced otherwise. I made notes of what I had seen, and we continued our tour.

Following the press, tiles were being painted and then cut to final size. After the cutting station, tiles went through an inspection station, where two operators were visually checking the quality of each and every one. While we were there, the inspectors were rejecting one-third of the tiles they were inspecting. There was so much scrap being generated they were having a hard time keeping up and had to stop the line many times.

During one line-stop we asked the inspectors what they were seeing. They showed us the broken edges of the tiles. The edges had cracks down the length of the tiles at an angle. They looked just like the angle of the press stop-gate we had seen earlier. I asked the inspectors for a few samples, which they were more than happy to share.

A New Angle on the Situation

We took a walk back to the press with Walter. We showed the press operator the sample ceiling tiles. He was shocked. He didn’t realize the stop-gate was causing so much scrap. He immediately shut the line down to make adjustments.

While the line was down, I asked if I could take a look inside the press to see if there might be a reason the tiles were hitting the gate at an angle. After locking out the press, I took a closer look and was amazed at what I saw. The guide rails in the press were not straight as designed, but curved. These rails were causing the tiles to turn at an angle when they entered the press. All plants had scheduled maintenance to replace press guide rails every six months. When I asked the press operator when the last time the rails had been changed, he didn’t remember, but thought it had been years. I then asked if they had backup press guide rails in their storeroom. Luckily, they did. Even luckier, they were straight.

Setting Things Straight

We replaced the curvy press guide rails with straight ones, and started up the press. Immediately we stopped the press. We were still damaging the edges of the tiles, this time at a different angle. We quickly identified the problem. The stop-gate was angled for the curvy guide rails and had not been adjusted for straight press guide rails. Once we straightened the stop-gate, the edge damage disappeared. After a few handshakes and high fives, we created a monthly press guide rail inspection and a six-month replacement program for this critical component.

During the week, the team made many other quick improvements and planned out other work that helped the Mobile plant return to budgeted performance for the year. If there’s a lesson to be learned from Armstrong’s Mobile plant, it’s to trust your processes, but verify them on a regular basis. Trust alone cannot eliminate inefficiencies or waste from creeping in, but consistent verification can identify these issues quickly so that they can be corrected.

The Gift of Kaizen

It was shortly after Thanksgiving, late one afternoon on a cold day in November.  I had just gotten home from what I thought was my last business trip of the year.  I was tired and wrung out from all the travel, not to mention all of the hubbub of gearing up for the holiday season with friends and family, dinners and parties, and you get the idea.  I had just sat down in my favorite comfy chair and put my feet up and closed my eyes when a call came in to the Process Improvement Partners Hotline.  The voice was deep, full of life, and familiar.  “Adam!“ It wasn’t a question, it was a statement.  It was as if he knew me and somehow, I knew him.  I had spoken with him before, but I couldn’t put my finger on when and where it might have been.  “Speaking,” I said.  “This is …aah… Mr. C., we’re having some trouble at our Northern toy factory.  If we don’t get all of our orders out in December, we’re going to have some really disappointed customers.  Can you help us?” he asked.  “Of course, just tell me when you need me, Mr. C.”  He let out a big belly laugh and said, “Right now!” 

When you get an urgent call like that, you do whatever it takes to respond.  So, I packed a bag, my extra socks and my warm hat just in case, booked a flight, called an Uber, and got ready for my adventure in the North.  Twenty minutes later a long red car pulled up with the oddest-looking driver I ever saw.  He had pointy ears, said his name was Brucie, and that he would be taking me directly to the factory.  I told him I had already booked my flight, but he said I wouldn’t need it, he had a way of getting me there sooner.

We started talking and he told me how the workers had been getting behind at the factory due to more issues than they could handle.  As we talked, I felt myself drifting off to sleep.  When I woke up, I was at the North Pole.  “Holy Smokes, the North Pole!  Glad I packed my extra socks and hat, I’m going to need them,” I thought.

Assessing the Situation

Brucie took me to the Big Guy’s office.  We embraced like old friends.  He told me I was on the Naughty List for a few reasons I won’t elaborate on here.  If I could help them resolve their issues, I might wind up back on the Nice List.  I told him I would do my best, but first we would need to take a walk through his factory to see what was going on.

Brucie led the way.  It turns out he was the operations manager, and he wanted to see what I might be able to offer.  As we walked through the factory, I saw piles of work in process inventory.  I could barely see the workers themselves.  They could see me, however.  Every time I passed a worker, I would hear a giggle.  Apparently, I looked a bit out of place in their factory.  My ears weren’t pointy, I didn’t have bells on the ends of my safety shoes, and they seemed to know why I was on the Naughty List.

Brucie told me his workers were making mistakes and when they asked for help, no one could hear them, because all of the piles of inventory muffled their voices.  He also felt he needed a way to see progress during the day and assess whether or not he was on track to meet all of the orders.  The Big Guy looked concerned.  He didn’t want to disappoint any of his customers and he felt that his workers were losing hope that they would be able to complete all their work in time.

I spoke with a number of the workers on the tour.  To a person … no, to an elf, they seemed worried.  They knew they had to complete their work, but didn’t know what to do about it.  They wanted to help, but didn’t know how.  They were working as hard as they could, but just didn’t know if it would be enough to be ready for the big delivery.  There was also something somber about the atmosphere in the plant.  It seemed like elves should be having more fun doing their work, but the energy level and joy was not there.  I was hoping they weren’t considering striking.

After the tour, we sat down for a lunch of milk and cookies to discuss what could be done.  I told Brucie and the Big Guy that I could facilitate a session with 6 of the production workers, Brucie, Kittie from HR, and two maintenance workers that would solve the problem in three days.  They looked skeptical, but were willing to commit the time and resources.  This was way too important to shortcut.  We had to solve the problem.

The Kaizen Begins

The next morning, the Big Guy kicked off the session with inspiring words of encouragement and faith in his team.  He knew his team wouldn’t fail and that I would be able to help them do what needed to be done.  It’s great to have such outstanding leadership and support and also knowing that my sponsor could get me off the Naughty List.

The Big Guy left, and I spent a few hours teaching Lean principles and techniques to the team.  Instead of Power Point slides, I used Flipcharts made of taffy.   Once we finished with a sheet, I’d hand it to the team to munch on.  Elves are little, but they really like the sweet stuff.  And boy can they eat!  Early in the discussion I got some pushback from Kittie, who said, “We’ve been doing things the same way for centuries, what makes you think you can help us solve our problems with this Lean stuff?”  I assured her and the rest of the team they would look at their situation differently using Lean principles and I had confidence in their spirit, enthusiasm, and creativity.  I also told them I believed in them and knew we were going to do the right things to win.  Plus, I had to get off of the Naughty List!

After that they asked many good questions and were able to make a connection to the problems they were facing in the factory.   They realized some of these principles might help and translated some Lean terms into Elfish, so that the others in the factory would understand what we were trying to do.  We then took a walk through the factory to generate ideas to improve the situation.  The team members were really getting into it, even Kittie.  They started to understand how to apply what they learned in the classroom to their situation.  When the team returned to the meeting room, we took a break to have some hot cocoa and peppermint sticks.  I don’t normally eat like this, but it seemed like the right thing to do and it was really yummy!

After our break, the team prioritized all of their ideas into three major categories:

1.       Improve the flow of work

2.       Visual management to assess progress of the production lines

3.       Managing systems to provide help immediately to anyone who needs it

I broke the team into three sub-teams and they got to work in the afternoon.  I have worked with many Kaizen teams in my career, but I have never seen any team get as much work done in a few hours as Team Elf.  It was almost by magic. By late afternoon, each sub-team had put together some really solid work plans and were ready to implement their solutions the next morning. 

That evening, we had a team dinner at the most beautiful and coldest restaurant I had ever been to.  The Big Guy and his wife joined us, along with some of the other staff, including Dancer, Rudolph, and Olive, the other Reindeer.  During dinner we talked about all we had done that day and what we hoped to accomplish by the end of the Kaizen event.   There was much laughing and toasting.  Stories were told about me I had forgotten about from my early childhood.  How did they know about my adventures at the Rolling Stones concert or that my first-grade teacher used to love my piano playing or that her name was Mrs. Simonds? 

I must have gained ten pounds that evening, as nothing I ate could have been healthy.  After dinner, I was shown to my room for the night.  It was cozy and small, but I felt right at home.  It’s very cold at the North Pole, but there was a warm fire in the hearth.  Good thing I packed my favorite footie PJs.  After a cup of the best hot cocoa I ever had, I drifted off to sleep.  That night I dreamt about Lean Toy Delivery, figuring out ways the Big Guy could get down chimneys in a safer, more efficient manner.    

Implementing Solutions

We kicked off the morning of the second day with a few Christmas carols and other elf favorites.  Rudolph came in to see what was going on and used his nose to act as percussion.  You could feel the team’s optimism, energy, and excitement.  I reviewed some Lean concepts then set the team off into their working groups to implement their ideas.  I reminded them that it was helpful to get others’ input and even utilize their help, just in case it would be needed.  Everyone in the factory was a Kaizen team member, they just didn’t know it.   We were going to do everything possible to win.

In the middle of the morning, I noticed the “Improve Flow” team had rearranged the workstations in the factory.  Instead of one elf building hundreds of the same toy assemblies before moving it to the next elf, he or she would build one sub-assembly and pass it on to the next elf to do their part.  This improved flow, identified quality issues more quickly, and reduced the piles of inventory.  Everyone could now see each other, help each other, and hear each other.  They looked so much happier and started singing Elfish songs – the type of songs that stay in your head and can’t escape until another song takes its place.  I’m hearing one now, I kid you not!

The “Visual Management” team put together some large display boards, made out of white chocolate.  These boards showed the hourly production results with targets and actuals listed.  Each line leader was responsible to post his/her team’s results.  If they met the hourly target, they put a green spearmint candy on the board.  If they missed the hourly target, they put a red cinnamon candy on the board.  I noticed that the first time a line hit its hourly target, there was a spontaneous cheer, laughter, and dancing from the workers.  It was contagious, and I found myself dancing with them.  I hope no one filmed it and put it on their social media site, Elfbook.  It would be too embarrassing!

The “Managing Systems” team installed pull cords at all of the work stations.  If someone was falling behind or had a question, they could pull their cord and a yellow Gummy Bear light would flash at their work station.  They would get help immediately to get them back on track or answer their question.  The team also created an hourly, daily, and weekly audit to ensure everyone understood and followed the new process.  The line leader was to do the hourly audit, Brucie was to do the daily audit, and the Big Guy did the weekly audit.   They made the audit fun by giving out random treats to the workers as they walked around the factory.

By the end of the second day, I could see the team was well on their way to solving the problem and making all of their customers happy.   The team was energized and excited about what they were doing.  They had a few more things they wanted to do, but I sent them home for the evening, confident they would get it done on day three.  I went back to my room and tried to relax.  It was happening so fast and there were so many customers to serve.  Would we make it?  Would I get off of the Naughty List?

On day three, the team came in and got right to work.  They put together a training plan for all of the workers in the factory.  Instead of writing work instructions, they wrote songs to sing while the elves were working.  Each song contained the information they needed to make all of the toys in the safest, most efficient, and highest quality manner.  Elves love to sing, so this was a brilliant solution to an age-old problem.  I don’t know if my other Kaizen teams would be willing to use this method in the future, but you never know what might work.  Kittie even admitted she was impressed by the solutions of the team and really believed these improvements would work and save Christmas.

The Report Out

After filling ourselves with snickerdoodle cupcakes and chocolate milk for lunch, the team went out into the factory and presented their efforts to the rest of the elves.  The Big Guy spoke first.  He started by telling everyone what a great job they were doing and how important their efforts were to their customers.  He then gave his support to the team who had worked so hard for these three days and handed the presentation to the team.  The team reviewed and demonstrated all of the changes they had made.  Finally, they sang the songs they had written and invited the other elves to sing along.  There was a joyous sound throughout the factory as everyone started singing and following the musical work instructions.  After the singing was over, the team high-fived, hugged, danced, and clapped for each other.  The Big Guy even gave me a hug.  He could have crushed me, but I felt warm all over.  It was the nicest recognition I ever received. 

I was relieved and exhausted when it was all over and I was ready to go home.  My Uber showed up, with Brucie as driver again.  We talked about all of the great work of the team as he drove me back, and once again I drifted off to sleep.  When I woke up, I was home in my bed.  Was it all just a dream? 

On Christmas morning, I came downstairs to get breakfast and saw a candy cane taped to an envelope with my name on it on the kitchen table.  I ate the candy cane and opened the envelope.  Inside was a note that said, “Adam, thank you for your help at the factory.  We were able to make all of our deliveries this year and think we should be OK for years to come.  Love, the Big Guy.”  This was great news, but I was still wondering about one more thing.  I walked into my office and on my white board was a note that said: “And yes, you’re off the Naughty List … for now!”

Shine a Light on the Problem

The Corporate Quality Manager of a suspended ceiling manufacturer had a problem. When he wanted to check for defects on ceiling tiles, he had them shipped from the manufacturing plant and installed in ceiling grid in the corporate testing facility. This 12’ x 24’ ceiling grid configuration was adjacent to a large bank of windows. He then waited for the weather to cooperate. You see, he wanted the proper angle of sunlight to shine across the face of the tiles, and depending on the time of year and weather conditions, he might have to wait weeks to assess the quality of the tiles. The windows were often obstructed with testing materials, which made access and viewing even more difficult.

The ceiling manufacturer was about to introduce a large quantity of new products and the installation setup would not be sufficient to check all the new products’ quality prior to product launch. A change had to be made. As Lean Champion for the company, my help was enlisted to solve the problem. After some initial discussions and a tour of the area, the Quality Manager and I agreed we needed to think differently about the setup and process of quality testing. We decided to use a Kaizen event to optimize the design of the required testing space.

We assembled a team of testing technicians, quality technicians, scientists, and marketing representatives to think through the testing requirements and systems to install. We also identified a space to use for the new quality testing area. After a few weeks of touring various buildings and negotiating for space, we chose two adjoining 20’ x 50’ spaces on the ground floor of the testing facility. These spaces were filled with equipment and materials from many years of testing and development. We were sure we would be able to remove most of it and re-purpose the space for the benefit of the company. Although these spaces were large, they had no windows to the outside, so we would have to figure out another way to provide proper lighting to the face of the ceiling tiles.

On the first day of the Kaizen, we reviewed Lean principles and spent extra time on 5S. Next, we took the team on a walk of the current testing area and then to the identified spaces. Their first reaction was surprise and disappointment. They thought we should use the existing space by the outside window and reorganize materials and tools.

Our goal was to be able to assess tiles for quality at any time, regardless of the weather. This goal forced us to rule out the current location for testing. In the new space, the clutter got in the way of the team’s vision of what was possible. So, we did the first S, “Sort”. During Sort, the team removed 90 percent of what was in the space. Some equipment, which had been purchased to provide critical data in years past, was no longer useful, and was removed. The team contacted as many of the equipment owners as possible, to ensure we wouldn’t throw out anything critical. Everything would be removed from the space, no matter what.

Once we cleared out the space, we developed our concept for testing. The idea was to create a number of testing spaces, or pods, in which to install and check various types of ceiling tiles. These tiles needed to be at least seven feet off of the floor, so that they could be observed from below as well as from the side, using some form of raking light. The light had to go across the painted face of the tile, so defects and inconsistencies would be readily apparent. The team agreed the size of each pod should be 12’ x 12’. This allowed us to create three pods in each 20’ x 50’ space, for a total of six. We now had three times the capacity of the existing testing space. But, how were we going to create the necessary lighting?

The first thing we had to do was to identify the intensity and angle of light we needed. Fortunately, we were able to do so on the second day of the Kaizen, as the sun came out and provided the necessary lighting required in the existing testing space. Using light meters and the experience of the team, we identified the proper number of lumens (intensity) and optimal angle for the light in the pods.

The next step was to build the ceiling grid configurations in the pods. We put together three installations of ceiling grid in one of the two rooms. Each was squared up and then ceiling tiles were installed. We made sure we had enough space on all sides of the installations, so we could view the tiles from any angle, without obstruction.

Now it was time to go shopping. We purchased enough lights for one of the pods, before committing to all six. We bought a number of different fluorescent lighting configurations (and kept the receipts) to allow us to test and identify the optimal configuration.

On the morning of the third day, we performed our first lighting tests in one of the pods. A technician climbed a scaffold and held one of the lights up to the ceiling tile installation. The team wasn’t pleased. They asked him to move the light a little further away and a little higher. Things started to look better. Then, after a slight adjustment in location and height, they felt they were getting the type of lighting required. Using light meters, they verified a consistent result compared with the natural light measured on day two. The team collected several measurements and developed plans to assemble permanent lighting fixtures for all pods.

Later in the day, the first lighting fixture was installed and the team verified their results. Everything was as expected. Then the team realized an opportunity to provide the same lighting at a 90-degree angle to the original light fixture. They would just need to install an additional fixture and connect it at right angles to the original fixture. This gave them additional inspection capability they never had before.

On the fourth day, the first pod was complete and plans were made to install the same lighting in the other five pods and to hard-wire everything to make it as safe and efficient as possible. Now the team had a new problem. With the extreme increase in productivity and complete elimination of wait time to test, everyone would want to use the pods at the same time.

The solution was to designate an owner for the area and a system to ensure the area was well-managed and organized. To reserve the use of a testing pod, a white board was installed to make reservations visible, by pod. If someone used a pod longer than the requested time, the area owner would follow-up and hold them accountable to honor their commitments.

At the report out, the team proudly reported on their results. They were able to take a process that used to take weeks and reduced it down to minutes. They also increased the capacity of the area by a factor of three. Anyone could now use the pods safely and productively and testing would no longer slow down any new product development or testing project. In the next six weeks, all lights and wiring were installed, and the space has been in continuous use for years.

The team learned how to shine a light on the problem and solve it creatively.

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.