Gemba Walks
For those unfamiliar with the term, Gemba means “the real place, the place where the work is done.” A Gemba walk therefore means that you are going to walk through the real place and assess the work being done there. I tweak it a bit to mean, “assess the health of the operating system.” This sounds like an audit, and it is. For many companies, the idea of the Gemba walk is to take people out of their offices and walk through the process with their people. It’s not always the most comfortable thing for people to do. If done well, it can be extremely impactful. If not done well, it becomes a big waste of time. The idea is to make it as engaging and impactful as possible. The next story is how I helped a team in St. Helens Oregon develop a Gemba walk that was impactful and drove organizational behavior to higher levels of performance.
I was the Operations Manager at Armstrong World Industries’ ceiling tile plant in St. Helens Oregon for just under three years. During that time, I had the great opportunity to test and apply some of my continuous improvement principles to the manufacturing organization directly and get immediate feedback from my efforts. I am proud to say we had some of the best operating results in the company, and I’d like to think that my efforts contributed to that. There were a bunch of great team behaviors that already existed, and I applied my approach in a way that utilized and enhanced the strong culture of teamwork.
I spent a large percentage of my time on the manufacturing floor, engaging with the technicians and auditing the systems that were keeping us safe and productive. We used many paper documents in our work and everyone was required to sign off when they completed critical tasks. The Team Managers were required to audit their crews on a regular basis and then I would audit their audits on a less frequent basis. At one point, we were 100% compliant for all critical tasks for many months in a row. The plant was operating at peak efficiency.
A Slip in Efficiency
During an economic downturn in 2010, the plant reduced staffing and I was offered a position in the corporate offices in Pennsylvania. I hated to leave my team, but I felt like the plant would continue operating well, using the systems developed during my tenure. Sadly, this was not the case, and efficiency and productivity started to suffer. The plant recognized this and implemented a daily staff-led Gemba walk. After many months, performance wasn’t improving and I was asked to come back out to the plant to see if I could help. I was happy to do so. I missed my team on the west coast.
The first morning of my visit, I attended the daily Gemba walk with the staff and observed their interactions and engagements with the technicians. There were eleven staff members who walked all over the factory, stopping at designated locations to engage with the technician doing a task. During each stop, they would ask these questions: Is everything okay? Do you need any help from us?
Most of the time, the technician would say everything was OK (it wasn’t) and they didn’t need any help (they did). The person asking the question would engage with the technician. The rest of the team didn’t seem to know their role. They weren’t paying much attention to what was going on. Afterwards, we would thank the technician for taking time with us and then walk to another location in the plant.
After we completed the Gemba walk, the staff asked me for my opinion. I told them that their purpose wasn’t being supported by the activity of the walk. If their intention was to show support and help for the technicians, it wasn’t apparent during the walk. The terse answers by the technicians showed they didn’t believe they were being supported or that sincere help was being offered. The lack of engagement by the full staff was troubling and it was apparent to their customers, the technicians.
The good news was, if they were willing, we could easily change the Gemba walk and achieve their purpose. However, they would need to engage their customers in the redesign of the Gemba walk. They were willing and we agreed to bring a small team of technicians, team managers, and staff together in the next day to redesign the Gemba walk.
A New Kind of Walk
The next morning, I reviewed the principles of a Gemba walk with the team. These principles included: Be help to those you interact with, assess the health of the operating system, and engage and support your customers (the technicians). I challenged the team to develop a focused purpose for their Gemba walk. They decided they wanted a Gemba walk that would help them prioritize and take action on the top issues causing safety and productivity risks. They also wanted the Gemba walk team to expose issues the technicians were overlooking in their everyday work. Finally, they only wanted people to attend the Gemba walk if they sincerely wanted to be there and were helpful.
Based on a refocused purpose, the team started designing the new Gemba walk. Their new design improved the questions to be asked, the way the staff would engage, and how issues were to be exposed. The new questions weren’t yes or no anymore, they were more “show me” questions. “Show me the issue that caused you downtime yesterday or concerned you from a safety standpoint.” “Show me how the valve works when you switch from tank A to tank B.”
In order to expose risks and increase engagement of staff with the technicians, the team created seven different responsibilities to be given to different Gemba walk team members. Examples included: safety auditor, standard work auditor, housekeeping auditor, and equipment auditor. These duties were written on cards and given out randomly to members of the staff at the beginning of the Gemba walk. At designated stops staff were to review their findings with the technicians and the team. The team would then prioritize the top issues at the end of the walk and take action on them.
Simple Changes, Large Improvements
The team conducted a Gemba walk using the new process. During the “simulated” walk, we asked various technicians their opinion of the newly designed process. They were extremely positive about it and thought it would be more helpful to them than the prior Gemba walk. With feedback from a number of technicians, the team finalized their new Gemba walk by the end of the day. The next morning, they started the new Gemba walk and uncovered many issues that had been holding back the performance and safety of the plant. Engagement improved, as well as safety and productivity over the next months and years.
I have seen Gemba walks in many stages of effectiveness. Some Gemba walk teams take a specified tour of their offices or facility and then end up at a white board to review performance and make assignments. While this is a vast improvement over staying in your offices and reading reports, it feels as though the person reporting results at a board is in the spotlight, or on trial. It doesn’t feel as engaging and helpful, as most of the participants are firing questions to the person reporting results. Slight improvements would make all the difference, and I encourage those who do things in this way to review and reflect upon their Gemba Walk purpose and make corrections that would better support their purpose, much like the St. Helens team did.