What is a Gemba Walk?
Gemba - 現場, or Genba, means an “Actual place” in Japanese. Practitioners of Lean methods use Gemba walks to drive strategic objectives. Unlike typical western management models, where leaders are removed from the workers in their ivory offices, Lean encourages managers to go on Gemba to observe, learn, connect with the teams, and to offer help. But what does one do on a Gemba walk, and how can Kanban practitioners benefit from this amazing tool, besides getting some physical exercise?
How to do a Gemba walk?
Observe the facts, then ask why things happen the way they do. The Gemba walk is rooted in facts. What is happening at the place of work? How many people are overloaded and how many are standing idle?
Step 1: Notify the team of what you’ll be doing, ahead of time
Most practitioners agree that it’s good to let the team know ahead of time, that a Gemba walk will be taking place. Not to put extra stress on them or cause any atypical, forced behavior, but so that they understand that the purpose of Gemba is the observation of how the process works on an everyday regular basis. Let the team know you’re open to a conversation!
Step 2: Be prepared
A good idea is to have a plan, regarding what aspects of the process you’ll be paying attention to, what questions you’d like to ask the team, what information you’re after. Although it would not be possible to always know the answer to these questions, their goal is to stop you from ..just walking around aimlessly through the factory or office floor!
The best place to start, when drawing a plan for your Gemba, is to focus on the Value Stream - if you know it, follow the value stream in its actual steps across the floor, to find improvement opportunities, and if you have not yet mapped it out, Gemba can be of help in doing so. Take a look at what happens at the process steps that bring value to your customer, and learn from the team members themselves, how their work could be made easier and more effective.
Step 3: Go where work is being done to observe it
The crucial thing to do here: go to the place where work happens and observe, to get a better grasp of the process by seeing it for themselves. Though it’s the key step here, as shown - it shouldn’t necessarily be the first thing you do, if you’re keeping the best possible outcomes in mind.
Step 4: Respect people, don’t judge
An important thing not to do is to go and judge or check up on workers. Gemba walk is not an excuse to spy on employees sleeping on the job, although that is a no-no. A leader on a Gemba walk would ask themselves why are people sleeping on the job, are they overworked, or have they no assignments? Respecting the people that are working with or for you is just one of the points where Gemba and Agile align perfectly. The Gemba walk should give you further insight into what you’ve already been seeing on your Kanban board. If there are bottlenecks on your board, you should also come across them in practice.
Step 5: Take a moment to recognize the difference between a developer’s desk and their mind - where is Gemba?
Not disregarding the value in visiting the development team’s office to see what they’re up to and asking them for thoughts on how the process works, as it often will tell a lot about if the process is working or not, in some cases you will get more information by looking at that team’s Kanban board. That’s because a Kanban board will often become the representation of an actual place of work - Gemba - for knowledge-based processes.
In creative and intangible use case scenarios such as software development, content creation, or much of academic research, while people are of course usually sitting at their designated workplaces, the actual work process happens in their heads, not on their desks. Here is where a visual Kanban board comes to help, presenting their entire process in steps, leaving you able to peak into the value stream, to see what stage they’re at, which part is usually creating the most difficulty, where more resources may be needed, etc.
Did you know?
Kanban Tool® boards let teams create a workflow that matches their process perfectly, and to automate the repeatable portions of it. Try it out with your team to have instant access to the process flow!
Step 6: Conclude and make changes
If this final step is omitted, then the point of your Gemba will only be an intrusion of the team’s workspace. Once you’ve learned how they work, what obstacles they meet, and what impedes the value stream, create an action plan to change that. Make sure to make it as detailed as necessary, for the changes to be possible to implement. Don’t stop at stating: you need to pay more attention to how you test your code. Be specific, set concrete goals, and follow up on whether they are met.
For that reason, it makes sense to limit your Gemba to one aspect of work per session - otherwise, the action plan will become too big to handle, and no changes will take place. Better an incremental change creep than a revolution that damages morale, production, and profit all at once.
Example In a timber factory, a leader on a Gemba walk could observe the following facts:
- Workers are hauling large pieces of timber from one side of the factory to the other.
- Team members processing the inventory often stand idle waiting for the delivery workers to cross the floor with goods.
- Processing team members spend about a third of their time searching for wood cutting tools, scattered at different stations all across the factory floor.
Having made these casual observations, the manager could then ask the team why this happens. They might explain that the delivery of timber is dropped off at the entrance to the factory because there is no access to the rear of the factory. The foreman on the floor could explain that the heavy wood cutting tools need the heavy-duty power sockets, that are located only at the rear of the factory.
The manager could then measure the time it takes for workers to cross the floor and decide, that by implementing high power sockets at the entrance of the factory, they will save 3 hours each day. By applying this change, the manager would improve throughput, and reduce waste - the unnecessarily spent workers’ energy in this case. Within a week from this change, the manager would see that the cycle time on his Kanban board has decreased, as the process is executed much quicker, and safer too.
What to look out for?
While there is no silver bullet to doing a Gemba walk right, here are a few key points, paying attention to which can help:
- Is work carried out in a standardized fashion, or are people just picking up random tasks?
- How clear is the work environment, how free of clutter is it, and how often are workers bumping into items that shouldn’t be there or weren’t planned? This is true of both physical and virtual environments - do employees have to wade through a lot of irrelevant information to find the item they are looking for?
- Is the work environment safe, or are there any potentially dangerous accidents waiting to happen? Do junior developers get access to your production code, are private data documents held in unlocked cabinets, etc.
- Is there a lot of motion happening without much results produced? Look out for unnecessary traveling, walking, meetings, or reporting.
- Talk to workers, be interested. Why do they do what they do, what are some of the problems they experience which are not at all apparent to an onlooker? Yes, sometimes you simply need to ask!
- Is there a lot of idle time in the process? How much time are people spending just waiting for things to happen, for the previous process step to complete, for a task to be authorized, etc.?
- Are workers waiting on machines or are machines waiting for workers? While the latter is acceptable, the former never should be. Giving the team access to fast, robust tools is not only a talking point aimed at attracting new workers to the company - they are necessary for them to keep your process efficient and frustration-free.
- Are designated areas marked, or - in a knowledge-based scenario - is access to information readily available for workers to draw from? Do they know where to go for information on what or whom to ask for assistance?
Whatever you do, do not send your subordinate to go and observe for you. You, as the leader, should be there at the coalface, where your product is being made, looking at what’s happening. You will probably save a lot of money through the improvements it will help you bring, and you might get to know your team a little better. Happy walking!