Last week, I taught a pilot session of a new class on Kaizen and continuous improvement that I taught for visitors to the ThedaCare Center for Healthcare Value. Unlike other workshops that have assumed people are starting from scratch, this was designed around exercises, simulations, discussions, and two “gemba visits” to see daily team huddles (one at ThedaCare and one within the Center).
I used an exercise that has worked well in the past to demonstrate how Kaizen is done – solicit, discuss, and test ideas.
Some photos from different steps in the exercise:
The initial process flow and layout is intentionally bad. The five stations are far from each other, which necessitates batching. Here is the layout and the initial “spaghetti diagram” showing the flow (or lack thereof) of the envelopes being stuffed.
After the first round of envelope stuffing, I led a team huddle for the participants, trying to demonstrate how the Kaizen Board is used and what behaviors we try to exhibit while doing this.
The team identified problems and came up with ideas for improvement – either on their own or because I asked them and prompted them to think about it. “What do you think we could do?” is a key question to use in the workplace. If staff have been dependent on the manager having all of the answers, you have to break that habit and help develop people.
They came up with a number of ideas to test, including:
- Moving the five workstations so they were in line with each other and next to each other
- Reducing the batching to single piece flow (now that the layout was better)
- Rearranging some of the stations
They had more ideas, but we chose to just implement a few — focusing on better, not perfect.
Here is the layout they came up with, and the expected spaghetti diagram:
I’ve seen teams do this simulation and Kaizen process probably 25 times.
I could have jumped in with a suggestion, but I held myself back. My idea (or the problem I saw) wasn’t a matter of life or death. If it were that critical, I would have had an obligation to speak up.
Here, I was wondering why they didn’t point the long table toward me, putting the last operation next to me (the customer).
They ran the second round of the exercise. The time required to deliver five envelopes, as usual, was reduced by about 65% — through a better layout and less batching.
I asked them what waste they saw this time or what Kaizen opportunities there were.
Sure, enough, one of the participants realized what they should have done and, had we done a third round, they would have rotated that long table 90 degrees.
Had I spoken up and made that suggestion before round 2, they would have had their improvement a little sooner.
But, would I have shortcut their own learning, development, and confidence?
When they brought up the idea, I didn’t say, “Why didn’t you notice that earlier???”
I did point out, for the sake of illustrating my thinking as a facilitator, that I intentionally hadn’t spoken up. I didn’t give them the answer. I trusted they would figure it out eventually.
I’m paraphrasing John Shook from the Lean Enterprise Institute, who said something to the effect of:
“When you give an employee an answer, you rob them of the opportunity to figure it out themselves and the opportunity to grow and develop.”
I don’t think people get better at problem solving and Kaizen by being given answers. They get better by thinking, experimenting, learning, and adjusting. It’s the PDSA cycle in action.
Can you think of situations, in the workplace, where you gave somebody an answer and regretted it? Have you gotten better at not giving people answers? Have you tried to coach others and encourage them to let people figure things out on their own?
Where do you strike the balance between “improve now” and “develop people?”
Thanks for reading! I’d love to hear your thoughts. Please scroll down to post a comment. Click here to receive posts via email. Learn more about Mark Graban’s speaking, writing, and consulting.