Lean teams use gemba walks because reports and dashboards hide the details that matter. Seeing the work firsthand shows waste, workarounds and unclear standards. It also builds trust when leaders follow up on what they hear.
Where it comes from
Going to the gemba is a long-standing principle of the Toyota Production System. Taiichi Ohno, who led its development, encouraged managers to watch the work closely at the gemba.
At a glance
A gemba walk route
Swipe sideways to see the whole diagram.
How to apply Gemba Walk
- 1
Pick a purpose
Choose a focus for each walk, such as safety, flow, quality or a specific process. A clear theme keeps the walk from becoming a general tour.
- 2
Prepare questions
Write a few open questions in advance. Good examples ask what the standard is, how people know they are ahead or behind, and what gets in their way.
- 3
Go and observe
Follow the flow of work from start to finish. Stand still, watch several cycles and note what you see before drawing conclusions.
- 4
Talk with the people doing the work
Explain why you are there and ask respectful questions. Listen more than you speak, and avoid fixing problems on the spot unless safety is at risk.
- 5
Record what you learned
Capture observations, ideas and open questions in a simple notebook or app. Separate facts you saw from opinions you heard.
- 6
Follow up visibly
Assign owners and dates for any actions and report back to the team. Closing the loop is what makes people willing to speak up on the next walk.
Worked example
A distribution center manager walks the returns area with a focus on flow. She notices items waiting in carts because labels print at a single shared station. She asks the team for ideas, and they trial a second printer the following week.
Common mistakes
- Turning the walk into an audit that blames individuals instead of studying the process.
- Walking through quickly without stopping to watch the work long enough to understand it.
- Collecting ideas and never following up, which teaches people that speaking up is pointless.
When Gemba Walk is not the right tool
A gemba walk is for learning, not for inspection or blame. Walks that turn into fault-finding make people hide problems.
It also needs follow-through. Questions raised on the walk should lead to actions, or people stop taking it seriously.
Gemba meaning
Gemba is a Japanese word that means the real place. In lean it is the place where value is created: the shop floor, the ward, the warehouse or the desk where a claim is processed.
A gemba walk is a leader going to that place to see the work, ask questions and learn. It is not an inspection and not a chance to give orders on the spot.
Gemba walk checklist
Before the walk, pick one theme, such as safety, flow or quality, and tell the team you are coming. At the gemba, watch one process from start to end and ask the people doing it what gets in their way.
Look for the standard and whether it is followed, for work waiting between steps, and for problems people work around. Write down what you saw and agree on one or two follow-ups. The gemba walk checklist guide has a printable list of questions.
Questions to ask
Useful questions focus on the work. What is the standard here? How do you know you are on track? What got in your way today, and what help do you need?
Leaders listen more than they talk, and they note problems to follow up rather than fixing them on the spot.
Part of leader standard work
The Lean Enterprise Institute lists gemba walks as part of leader standard work, alongside reflection meetings, andon response, accountability and mentoring.
Jim Womack's book Gemba Walks collects his own walks and what he learned on them.