A gemba walk is going to the place where the work is actually done, watching it, and asking the people doing it how it really goes. This checklist gives the walk a purpose, a quick look at safety, organisation, flow, quality, equipment and visual management, and a place to record the conversations — which are the point of going. You can fill it in here and download a finished PDF without creating an account.
What gemba means
Gemba (often written genba) is Japanese for "the actual place" — in lean, the place where value is made: the line, the dock, the ward, the counter. The practice comes from the Toyota Production System, where managers were expected to understand problems by standing in front of them rather than reading about them.
The often-told story is of a young engineer told to stand in a chalk circle on the shop floor and simply watch, for hours, until he could see what was wrong. The point was not the circle. It was that the problems are visible if you look long enough, and invisible from an office.
A gemba walk is not a tour, an audit or an inspection of people. It is a manager going to learn.
Go and see, ask why, show respect
Three habits carry most of the method, and each one maps to a section of this form:
- Go and see — be there, at the time the work happens, following the work rather than your usual route. The walk details and purpose sections are about choosing where and why.
- Ask why — about the process, several times, until you reach something that could be changed. "Why is there a queue here?" is a better start than "why are you behind?"
- Show respect — the people doing the work know it better than you do. Ask, listen, write it down in front of them, and tell them what will happen next. Then make sure it does.
Do not fix it on the spot, and do not blame
The temptation on a walk is to solve things as you find them. Resist it. A fix made by a visiting manager takes the problem away from the people who own it, usually treats the symptom, and rarely survives the week. Note it, ask about it, and let the area work it through with your support. The one exception is safety: if someone could be hurt, stop it now.
When something is wrong, the useful question is what in the process allowed it — the missing standard, the late material, the unclear signal. Looking for who did it ends the conversation, and the next person you walk up to will already have heard about it.
Gemba walk questions that work
Open questions about the work get honest answers; questions that sound like a test get the answer people think you want. These are good starters, and the conversation section of the form repeats them as prompts:
- Can you show me what you are working on right now?
- How do you know this one is right before it moves on?
- What slowed you down today?
- What do you have to work around to get the job done?
- When something goes wrong here, what happens next — and how long does it take?
- Does the written method match how it is really done?
- If you could change one thing about this job, what would it be?
- You raised something last time — did you hear back?
Why this form scores the system, not the people
Many gemba checklists grade things like morale, or whether operators know their numbers, as pass or fail. That turns the walk into an appraisal, and people who are being appraised stop telling you what is really going on — usually by the second visit.
Here every scored item describes something the area's leaders provide: a standard at the station, a current board, a way to call for help that works. The conversations carry no score, and people are recorded by role, never by name. Speak while you walk, and the document the law or the client wants writes itself — which matters here, because standing at a distance typing is the posture that makes people stop talking.
Common questions
What is a gemba walk?
A practice from lean management in which leaders go to where the work is done to observe the process, ask the people doing it questions, and look for improvement opportunities. It is about learning how the work really runs, not checking up on individuals.
How often should you do a gemba walk?
Frontline leaders often walk daily, middle managers weekly and senior leaders less often but on a regular rhythm. Regularity matters more than frequency: a walk that happens on the same day every week becomes part of how the area works, while a rare one feels like an inspection.
How long should a gemba walk take?
Commonly thirty minutes to an hour. Long enough to watch at least one full cycle of the work you came to see and have two or three real conversations; short enough to do it again next week.
Who should go on a gemba walk?
The leader of the area, walking with whoever runs it day to day, is the core. Visitors from support functions — maintenance, quality, engineering — are useful when the walk has a question in their field. A large group reads as an inspection; two or three people is plenty.
What is the difference between a gemba walk and an audit?
An audit checks conditions against a standard and records whether they conform. A gemba walk sets out to understand how the work actually flows and what gets in the way, mostly by watching and asking. This form includes a light check of the area's systems, but the conversations and what you learn are the output.
What should happen after a gemba walk?
Every follow-up gets an owner and a date, and someone goes back to tell the person who raised it what happened — including when the answer is no. Read the notes before the next walk in the same area. If ideas vanish without an answer, people stop offering them.