Kaizen Snapshot
Setting: Armstrong's ceiling tile manufacturing plant in Macon, Georgia, in the late 1990s.
Challenge: Facilitate a weeklong Kaizen event with a team that hadn't been told it was participating.
Stakes: An unprepared team, an uncomfortable beginning, and valuable improvement time at risk.
Approach: Bring the team together, explain the objectives, engage participants at Gemba, and identify improvement opportunities.
Outcome: Despite the difficult start, the team implemented worthwhile improvements. More importantly, the experience changed how I prepared for future Kaizen events.
Key Lesson: Never assume the people assigned to a Kaizen know they're supposed to participate. Ask the right questions before the event begins.
Where's My Team?
Early in my career, I traveled extensively to Armstrong's ceiling tile manufacturing plants, facilitating weeklong Kaizen events.
One of those facilities was in Macon, Georgia, the largest plant in our division.
I had facilitated several events there and enjoyed working with the employees. I was still a relatively young engineer, and I loved getting out on the factory floor, working alongside operators, mechanics, and supervisors to improve their processes.
So when I arrived for another Kaizen, I was looking forward to a productive week.
I checked in with the plant manager, who was sponsoring the event, and began discussing our plans.
Then I discovered something rather surprising.
Nobody on the Kaizen team knew they were on the Kaizen team!
Not one participant had been told they were expected to spend the week working with me.
I had traveled to Georgia, prepared to facilitate a Kaizen, and we didn't have a team.
This was going to be an interesting week.
An Uncomfortable Beginning
Plant leadership immediately began contacting the employees who were supposed to participate.
Some were at home. Others had different work plans.
They were encouraged to come in, either later that afternoon or the following morning.
I remember feeling uncomfortable.
These employees hadn't been given an opportunity to understand the objectives, ask questions, or prepare for the event. Now they were being asked to change their plans with virtually no notice.
At that stage of my career, I wasn't particularly comfortable challenging a plant manager about how he managed his employees.
So I did my best to work with the situation.
But I knew this wasn't the way a Kaizen should begin.
Turning Things Around
When the team finally assembled, the atmosphere was understandably awkward.
Some participants weren't particularly happy about being there.
I couldn't blame them.
We explained what we hoped to accomplish and why their involvement was important.
Then we went to Gemba, where the work actually happened.
That's when things began to change.
As we observed the production process, employees began sharing their experiences and ideas.
The conversations became more productive, people started engaging, and the team gradually came together.
We ultimately made worthwhile improvements, and the participants seemed pleased with what they had accomplished.
But I don't remember the specific results nearly as clearly as I remember how the event started.
Because the biggest lesson wasn't about the manufacturing process.
It was about people.
The Lesson I Didn't Expect
Looking back, the problem seems obvious.
Of course people should know they're participating in a Kaizen well before the event begins!
But apparently, that wasn't something I had thought to verify.
I assumed that because the plant manager had agreed to sponsor the event, the team had been identified, informed, and prepared.
I was wrong.
And that taught me something important about my responsibilities as a facilitator.
I might not have had the authority to require a plant manager to prepare his team differently.
But I certainly had the ability to ask better questions.
Had the team members been identified?
Had someone spoken with them personally?
Did they understand why they were being asked to participate?
Had they agreed to commit their time?
Were their supervisors prepared to release them from their normal responsibilities?
Those were questions I could ask well before arriving at the plant.
And from that point forward, I became much more deliberate about asking them.
An Invitation Is More Than a Name on a List
Over the years, I've learned that one of the most important steps in preparing for a Kaizen is having the team leader or sponsor speak personally with each prospective participant.
Not simply sending an email.
Not just putting their name on a schedule.
And certainly not assuming someone else has told them!
I encourage leaders to explain why the event matters, why that employee's participation is important, and what the team hopes to accomplish.
Employees should have an opportunity to ask questions and understand what they're committing to.
That personal conversation does more than communicate logistics.
It begins building engagement and ownership before the Kaizen starts.
Although I can't tell you how many times my questions prevented another situation like Macon, I believe they helped avoid similar problems throughout my career.
The Improvements Begin Before Monday
I've facilitated hundreds of Kaizen events since that experience.
And one thing has become increasingly clear.
A successful Kaizen doesn't begin when the team gathers on Monday morning.
It begins weeks earlier, when leaders establish objectives, identify the right people, communicate expectations, and create the conditions for success.
The Macon team overcame its difficult beginning.
But we shouldn't have needed to overcome it in the first place.
That week taught me a lesson I've carried throughout my career:
Never assume your Kaizen team is ready. Ask the questions that make sure they are.
Sometimes the simplest questions prevent the biggest problems.
Want to give your next Kaizen the best possible start?