Championing Change in Technology

In 2010, a private equity firm took a minority stake in Armstrong World Industries.  They brought in many leaders at executive levels and committed to a strategy of Lean transformation. Their initial focus was manufacturing, and then when ready, they would expand efforts to the supporting organizations.  From 2010 through 2012 in the manufacturing organization, emphasis was placed on Lean training and conducting hundreds of Kaizen events.  In many cases, outside consultants were brought in. But, where there was experience, internal resources worked with teams and facilitated Kaizen events.

I had many years of experience facilitating Kaizen events and I was given the opportunity to travel all over the world, helping teams solve complex problems and keep them solved in a sustainable way.  Although I wasn’t part of the manufacturing organization at the time, I was often requested to facilitate, especially when there were complex problems to solve.

I enjoyed the work, but I also knew I needed to focus on improving my organization, Global Technology.  For years, I tried to convince leadership to utilize Lean to improve their critical processes. While they were interested, they never made the commitment to the continuous improvement effort.

Applying Lean Principles to Global Technology

In January 2012, everything changed.  Global Technology named a new Vice President, who had an extensive manufacturing background. He returned from an assignment in Europe, ready to make an impact on his new organization.  I worked for him indirectly a few years prior to his return, so we already had a working relationship. After letting him settle into his new job for a few weeks, I requested a meeting to discuss the application of Lean to the Global Technology processes. Luckily, I had two sponsors who had seen what Lean was able to accomplish in some global technology test areas, most notably the Pilot Plant.

Together, my sponsors and I met with the VP in March to promote our idea – apply Lean principles to Global Technology in a way that would improve the results of our projects and grow customer confidence. He was intrigued and wanted to know what we would do first. My suggestion was to run a Global Technology Value Stream Mapping event, identifying the highest value opportunities from our customers’ perspective, developing strategies to make improvements over the coming months and years. He was excited by the idea and invited us to present our recommendation to the Global Technology leadership team at their April meeting.

After reviewing year to date Global Technology results, the VP introduced me to the leadership team and told them about the recommendation for the Value Stream Mapping event. He explained how important and critical this work would be and he wanted everyone to clear their calendars so we could get started quickly. Then, he turned the discussion over to me. Most of what I wanted to cover had already been explained, so I started off by saying, “What he said!” Then, I described the Value Stream Mapping process and how we would apply it to the Global Technology processes. The leadership team seemed skeptical, but willing to give this new approach a try. When the VP said he wanted to start with an event in May, I knew we were on a fast-moving train and I had much work to do to prepare.

Identifying the Customers’ Perspective

Over the next few weeks, we contacted some of our critical customers from the plants, Marketing, and other areas of the organization. We also gained commitment from all Global Technology leadership team members to participate in the entire 3-day event, which would be held at a local hotel. I was able to get a co-facilitator who was not part of the working team and together we built a plan for the Value Stream Mapping session that would be relevant for our non-manufacturing processes.

On the first day of the event, a team of 25 high-level participants were in the same room and they heard the VP describe the importance of the effort. Then, he turned the meeting over to me. For the next few hours, I described Value Stream Mapping and then split the full team into working groups to identify the most critical customer requirements. After reviewing those requirements, we mapped out two critical Global Technology Value Streams:  New product development and capital project execution. By the end of the first day, we had a pretty clear picture of the current state and issues that were keeping the team from executing the processes well from their customers’ perspective.

Champion of Lean

The VP sent the team to dinner and asked me to stick around to talk for a few minutes prior to dinner. The first thing he said was, “You’re pretty good at this, how would you like to do this full time?” Immediately I responded, “Absolutely!” He was surprised by my quick answer and told me he hadn’t even made a financial offer. I told him that I trusted him to do the right thing and it was more important for me to do what I love, rather than worry about pay.

The next two days were a blur. Significant progress was made and clear strategies were developed to improve project execution and customer service in the new product development and capital project execution Value Streams.

For the next six years, I was the Lean Champion for Armstrong’s Global Technology organization. During that time, I was able to help teams drive new product development time down from 18 to 10 months, grow the new product portfolio from $150 million to $380 million, and increase customer confidence in the work of the Global Technology organization. More importantly, we were able to create a culture of engagement, empowerment, and improvement in the organization.

From Russia with Love: The Spirit of Kaizen Lives in All of Us

A Russian ceilings manufacturing plant asked me to help them facilitate their strategic road map in 2017. This was an activity they did annually since the plant opened in 2015. I had been to Russia one time before, during construction of the plant, so I had some experience travelling there and working with the people. This time, I would be coaching their continuous improvement leader in how to organize and facilitate this important session.

I met the continuous improvement leader on Sunday afternoon at the plant. My goal was to prepare him for what was about to happen and give him some tips on engaging the workforce and getting quick results during the session. It turns out that he was somewhat familiar with the techniques I was teaching, but frustrated by the culture of the leadership team. I assured him we would be able to break through and get strong engagement and quick results, but didn’t really know what I would be up against. In Russia, if someone at a higher level is speaking, someone at a lower level did not. Things also took longer to accomplish than what I was used to, so this was going to be a challenge.

We agreed we would use a modified Value Stream Mapping approach to develop the strategic road map. Rather than going into great detail when mapping the process, we would stay at a high level, but still have the team map the current state and identify opportunities for improvement.

On Day 1 of the session, I found myself in a large room of 30 team members and 7 interpreters. Each interpreter was paired with an English-speaking participant. The interpreter spoke into a microphone and the English was relayed to a headset. Amazingly, there was only a 1 – 2 second delay from the time someone spoke in Russian, to the time I heard the English translation in my ear.  It was hard to concentrate at first, but in just a few hours I was able to find a comfortable rhythm as I facilitated the team.

After introductions and Voice of the Customer, we took a Gemba walk of the process on the factory floor. I advised all team members to take sticky notes with them, so they could write down their ideas in real time and not have to remember them. These ideas would form the basis of the improvement efforts we would be mapping out later in the session.

When we got back to the meeting room, we mapped the current process on a wall. We used sticky notes, and I encouraged all team members to write process steps and waiting steps on their sticky notes and then place them on the wall where they thought they should go. If there was an error or a better way to write the step, I asked the team members to go up to the wall and replace the original sticky note and place it in the more appropriate place on the wall. When we exhausted all of the steps, I asked the team to review the map and make sure they believed they had the correct steps and sequence. If someone didn’t go up to the wall, I encouraged them to verify things were accurate, or at least close to accurate.

Next, I asked the team members to look at the steps and put a mark on the ones they felt caused the most problems or pain to them. Once we saw the steps with the most marks on them, I encouraged the team to come up with ideas that could solve that problem, writing their ideas on different-colored sticky notes. After all ideas were written, it was time to share the ideas and make sure that everyone on the team, from line operators to the plant manager, had an equal voice. This was accomplished was by going around the room, one person at a time, one idea at a time. When an idea was shared, we put the sticky note on a large sheet of flipchart paper for everyone to see. When we exhausted all of the ideas in the room, I encouraged all team members to look at the many flipchart pages with ideas, find their 5 favorite ideas, and place a mark on each one. The sticky notes with the most marks were the highest priority ideas for the team to pursue.

Once we determined the highest priority ideas to work on, we broke the team into sub-teams of 3 or 4. The sub-teams were tasked to work on each of the high priority ideas and build them out into future work for the plant. One of the sub-teams was assigned a project with $800,000 annual savings. After an hour and a half, I asked each sub-team to report on their progress, and the rest of the team was to provide support and feedback. The sub-team with the $800,000 idea hadn’t made any substantial progress. After all sub-teams reported on their progress, I decided to spend time with the $800,000 team and took the continuous improvement leader with me.

When I asked what was going on, the team members told me they thought their idea was a good one, but it would never be approved by upper management. When I asked why they thought this way, they said that because no one from upper management was in the session, they wouldn’t understand the idea and wouldn’t support their efforts. I asked them if they could phone the appropriate person in upper management to give them a better understanding of the idea. They were uncomfortable with my suggestion.

I stopped by the plant manager’s office and talked with him about the situation. He informed me a high-level executive was at the plant, but not in the session, and she was working on another project for the company at the time. I asked him if he thought we could get a few minutes with the executive. He gave me one of those looks I tend to get from my wife when I say something she doesn’t like.  I decided to spring into action anyway.

I asked the sub-team and the continuous improvement leader to come with me. We were going to get an immediate answer to our question. We walked over to the office the visiting executive was using and waited outside the door. She was on the phone. The sub-team wanted to walk away, but I wouldn’t let them. The executive looked up from her call and saw us waiting outside. Instead of waving us in, she looked back down and continued her call. Once again, the sub-team wanted to leave, but I wouldn’t let them. The executive looked up again, saw us still standing there, hesitated, and then motioned for us to come into the office. This was our opportunity!

Being the outsider, I felt it would be easier for me to explain the situation. I apologized for the interruption, thanked her for inviting us into the office, and explained what we were doing. I then asked if she had a few minutes to spend with us to review the $800,000 idea. She said, “I’m really busy right now.” Then, thinking better of it, she said, “I can give you a couple of minutes, then I need to get back to what I am doing.” We thanked her again and I asked one of the sub-team members explain the idea to her. As he explained, I could see the executive getting interested in the idea and even offering advice on how to make the idea better. Fifteen minutes later, she told the team they had her full support and they should pursue this fantastic idea. We thanked her for her time, told her she had the spirit of Kaizen in her, and left so that she could go back to work. Later, she came to visit the sub-team to see how they were progressing on the idea. The enthusiasm of the sub-team spilled over to other team members and before too long, many additional ideas were being developed to make the plant safer and more productive.

By the end of the session, the plant had a strategic roadmap designed to help it meet its goals for the next 3 years. The teams remarked they had never been in a session where everyone was given equal voice and where so much had been accomplished in such a short amount of time. It turns out that the only thing in their way was their thinking. We also discovered that no matter your cultural background, the spirit of Kaizen can live in you!