My management team feels tense and pressured about going to the gemba. Is this normal?
Dear Gemba Coach,
I’ve decided to take my management team to the gemba to get them to solve real problems but this is creating a lot of tension and they complain of the pressure. Is that to be expected?
To some degree, yes. When people haven’t had the experience to solve real coal-face problems together, at first they will tend to argue who’s to blame and find it difficult to work together. So some degree of tension is normal, certainly.
You might, however, without wanting to, be adding to the pressure in trying to get your management team to solve problems right away. Let’s take a deep breath and a step back. The aim of go and see is to get management to agree on problems and to support local staff in gaining autonomy to solve their own problems. The goal is NOT to get management t solve problems – it IS to teach management to teach their staff to solve problems across boundaries. Tricky.
When you start gemba visits what you really try to do is to get your management team to agree on problems, not solve them. For instance, in a hospital, how to you get the entire management team to agree that having stuff stored in corridors because the storage areas are full because logistics doesn’t deliver frequently enough IS a problem. This is not something they can solve on the spot. This is an issue they have to understand before they can work together at improving.
Secondly, you also need to educate your team to the fact that you’re not looking for a perfect solution right away. What you’re really looking for is a step forward to improve performance. In the hospital case, before you change the entire logistics system, your first expectations would be 5S in the storage areas to “clean the window” and understand what is what.
Thirdly, we are aiming for teamwork, not one person being burdened with the problem in its entirety. Which means that each member of your management team should attack their end of the common problem with their teams and that, somehow, you can coordinate this so that each silo sees the impact they have on other silos.
Gemba Walks: Not for Solving Problems
And last but not least, it’s your job to make sure the customer is not forgotten as people start to tackle their technical problems. “Customer First” remains the starting point, and it’s your job to represent the customer in any discussion of possible solutions. For instance, in the hospital case, my experience is that you can get early agreement on operational issues. But getting your team to face patient issues, such as measuring complications, or counting beds in corridors in the emergency room and tackling that, is much, much harder. So you start where you start, but it’s your job to keep steering your team towards issues with real impact on customer satisfaction.
This is quite a lot to swallow for any management team. What could you do to make it easier for them to follow you in this approach – other than resist simply because they don’t get what’s in it for them and feel uncomfortable (or even threatened) by where you’re going? If we draw a page from social psychology we learn that people’s mid-term attention is grabbed by:
- Shock: something jarring (positively or negatively) that will shut up the homunculus in the mind that is busy with internal files and will make people look up and pay attention. Gemba walks are a great tool for this because you can show your management team that something they consider banal and routine is, in fact, a real problem in the making. The reality of what happens as opposed to what people assume happens is usually unexpected enough that it shocks managers into paying attention (as well as trigger defensive reflexes you need to ignore).
- Frame: experience rarely actually translates into learning, unfortunately. People need to put their experience in the right mental context to understand the experience and build new hypotheses and arguments, which will lead to real learning, eventually. Framing means making explicit the goal/method you’re pursuing. In lean, the goal is performance improvement and the method is kaizen (process improvement by the workplace teams themselves). To make this easier, you can set up an obeya room where performance indicators are clear (accidents, customer complaints, service lead-time, inventory turns, productivity and so on) and where PDCA problem solving (for instance, in the shape of A3s or simpler if you like) are displayed. By doing so you create a space to think framed by the business performance you want to improve, and the kind of process improvements you value. This is extremely helpful in getting your management team to put the gemba experience in context and understand what you’re trying to get them to do – as well as getting them to work together on specific issues.
- Incentive: where’s the pay-back? Incentives are not restricted to monetary gains (indeed, you have to check that your bonus scheme encourages working together and not, as most do, looking smarter than colleagues). Incentives could be better business results, more recognition, better work atmosphere and so forth. Still, you need to think long and hard about which incentives would encourage your managers, one by one, to enjoy gemba walks and not just fear them.
This to say that lean thinking applies to gemba walks just as it applies to everything else. How would you define a successful gemba walk? And a less successful one? What is the performance improvement you expect from your management team? And what aspect of your own gemba walks you have to improve to obtain this?
Gemba walks are the starting point of lean thinking but their aim is to create space to think about our deeper challenges by looking at specific work instances, not to solve immediate problems through management pressure. Indeed, your management team might be resisting this new exercise (some certainly are), but their gripe about pressure has to be taken with respect.
The gemba walk is not where we solve problems, it’s where we try to understand them (ask “why” again) and share them. Solving the problem is the local manager’s daily job, with the support and coaching of her own manager. Gemba walks frame lean thinking in practice. One-by-one problem solving within the department trains people to better understand their processes and come up with new ideas to improve their work.
Seeing the Work of a Daily Management System
Daily management systems tap visual elements that expose problems, and also use obeyas as thinking spaces for reflecting on broader challenges, says Michael Balle.
What's wrong with taking a tools approach to lean management?
Dear Gemba Coach,
I keep hearing that a tool approach to lean is wrong, but tools deliver results – how can that be wrong?
How effective is a book club?
How effective is a book club?
It really depends where you want to take your lean journey. What are you trying to achieve? A core part of kaizen is not just looking for the results of the physical improvement, but the opportunity to grow, develop people – or self-develop, so that the learning can be applied to every other work situation.