A Gemba walk is a leader going to the place where the work actually happens, to see the process with their own eyes rather than through a report. It sounds simple, which is exactly why it is so often done badly: a walk with no purpose, no questions and no follow-up is a tour, not a management routine. Done properly it is a scheduled, 50-minute routine with a defined end time. This guide covers what a Gemba walk is, the process we teach for running one, how long it should take and how often it should happen. It also covers the questions to ask on the floor, the behavior that decides whether people tell you the truth, and how the walk differs in a hospital and in a factory.
What is a Gemba walk?
Gemba is a Japanese word meaning “the actual place”: the place where value is created. In a factory that is the production line, in a hospital the ward or the operating room, in an insurer the desk where a claim is assessed. A Gemba walk is the deliberate practice of going there to observe the process, talk to the people running it, and understand the gap between how the work is supposed to happen and how it actually happens.
In our training curriculum this is called Go-to-Gemba, and it is a habit rather than an event. It sits inside Lean as one of the routines that make Lean management real, and inside Lean Six Sigma it is one of the ways a team validates a suspected root cause against reality instead of against opinion.
What a Gemba walk is not: an audit, an inspection, or a chance to correct people. Those produce compliance and silence. A Gemba walk is meant to produce information a dashboard will never give you.
Why Gemba walks matter
Every management report is a model of the process, and every model leaves something out. A Gemba walk is how you find out what. It is the cheapest way to test whether the picture in the reporting pack matches the work. Three things in particular rarely make it onto a dashboard.
- The obstacles nobody escalated. Waiting, missing information, a tool that has been broken for a month. These rarely reach a report, because individually none of them is worth raising.
- The workarounds. Where the documented standard and the real process have quietly diverged, and why the people doing the work decided it had to.
- The gap between the measure and the reality. A metric can be green while the outcome it is supposed to represent is not, as the healthcare example at the end of this article shows.
The other payoff takes longer to show up. Leaders who turn up regularly, and who ask questions instead of correcting, earn the kind of trust that makes people raise problems early. That is worth more than any single insight a walk produces, because it changes what you get told for the rest of the year.
SPPA: how to execute a Gemba walk
We teach the walk as four elements: Schedule, Purpose, People and Action, or SPPA. They are what separate a structured management routine from a stroll around the building:
- Schedule. Plan your Gemba walks in advance. A walk that happens when the diary allows is a walk that stops happening.
- Purpose. Execute the walk with a specific goal. One topic, one area, one question you are trying to answer.
- People. Interact with and respect the people who do the value-adding work. They already know most of what you are there to learn.
- Action. Transform learnings into actions, and follow up. Without this the walk quietly teaches everyone that nothing changes.
The three phases of a Gemba walk, and how long it takes
A Gemba walk should be time-bound. The version we run in training takes about 50 minutes in total, split across three phases:
- Preparation, 10 minutes. Follow up on the actions from last week’s walk. Set the objective and the goal, and get into the right mindset. Determine the topic, the area and the goal, and define an end time before you set off.
- Go to the Gemba, 30 minutes. Go to the place, introduce yourself, build rapport and explain the purpose. Observe the process and involve the shop floor. Check the goal of the process and its performance, identify the obstacles, and work toward the root cause. Share what you have learned, and ask how you can help and what the next step is.
- Finalize, 10 minutes. Share your learnings with the other Gemba walkers. Reflect on your own behavior during the walk, as a short retrospective. Share the learnings with the people responsible, and together define the next step.
The proportions matter more than the exact numbers. Thirty of the fifty minutes are spent where the work happens. If the preparation and the debrief start eating the middle phase, the walk has turned back into a meeting.
How often should you walk the Gemba?
Frequency depends on how close you sit to the work. The closer you are, the more often you go, and the more operational your focus becomes:
- Team leader or supervisor, daily. Safety, quality, process adherence, abnormalities.
- Middle manager, two to three times a week. Performance, recurring problems, barriers the team cannot remove alone.
- Senior manager or site leader, weekly. Major KPIs, cross-functional issues, improvement priorities.
- Executive leadership, monthly. Strategic priorities, culture, systemic issues.
- Special situations, more often than usual. A new process, a safety issue, a quality problem, or a major change.
Gemba walk questions: what to ask on the floor
The quality of a walk is decided by the questions. Good ones are open, specific to the work in front of you, and safe to answer honestly. Use the two sets below as your Gemba walk checklist.
Safety questions
- Can you show me the safety procedures for this task?
- What was the last safety training you received?
- How often are safety inspections done?
- Are you informed about the results of those inspections?
- What are the biggest safety risks in your area?
- How do you report a near-miss or a safety incident?
- Is all personal protective equipment easily available?
- Have you noticed anything unsafe today?
- Is it easy to reach emergency equipment, such as fire extinguishers?
Efficiency questions
- What is the goal of this process?
- Do you get regular feedback about your actual performance?
- What was the last improvement that was implemented here?
- What is standing in your way of having a productive day?
- What tools, materials or information do you wait for most often?
- What part of this process takes the most time, and why?
- What is one thing you would change to make your job easier or faster?
The open-ended ones do most of the work. “What is standing in your way of having a productive day?” and “What is one thing you would change to make your job easier or faster?” invite the person to name the problem rather than confirm yours. Where an answer points to something deeper, that is the moment to move from observation into root cause analysis rather than to a solution.
The Gemba walk mindset: what leaders get wrong
Most Gemba walks fail on behavior, not on structure. How a leader behaves on the floor decides what people are willing to tell them, and the difference is stark:
Leaders who get nothing out of a walk arrive with a conclusion already formed. They do most of the talking, check up on people instead of listening to them, correct things on the spot, and usually leave at least one person feeling blamed.
The ones who get something out of it do the opposite. They look with their own eyes and stay with the facts. They ask questions instead of giving answers, and then actually listen to what comes back. They treat the walk as a chance to teach and to learn rather than to inspect, which takes some humility and buys a great deal of trust.
That difference explains why the same walk produces insight in one organization and silence in another. Correcting someone in front of their team is efficient once and expensive afterward, because the next abnormality gets hidden rather than shown to you.
A Gemba walk in a hospital and in a factory
The principle is identical in both: go to where value is created and see what is really happening. The way you conduct the walk is quite different.
In a factory the product is usually a physical item moving through a controlled process. The sequence is visible, and abnormalities announce themselves as stoppages, queues and rework.
In a hospital the patient is at the center of the process, and the work involves clinical judgment, uncertainty, privacy and frequent interruptions. The process is distributed across people and rooms rather than laid out along a line, which changes when and where you can usefully observe. What you are looking for is the same: where the work waits, where it is handed over, and where the people doing it have quietly built a workaround.
A healthcare example: when the walk saw what the data did not
A hospital was measuring discharge time, and the data said the target was being met. On a Gemba walk, staff explained what the report could not: patients were waiting several hours for transport home after being discharged.
The measure was recording the discharge order, not the patient’s actual departure. A metric measures what it was designed to measure, and nothing else. The hours a patient spent waiting for a ride home sat outside its definition. That gap is only visible to someone standing in the actual place, which is the whole argument for the routine.
The Lean Six Sigma Company runs in-company group training and full deployment support across the United States. If you want your leaders walking the Gemba as a routine rather than as an occasional gesture, those are the right starting points.
Frequently Asked Questions
1. What does Gemba mean?
Gemba is a Japanese word meaning “the actual place”, used in Lean to mean the place where value is created: the production line, the ward, the claims desk. A Gemba walk is the practice of going there to see the process firsthand instead of managing it from a report.
2. How long should a Gemba walk take?
About 50 minutes: roughly 10 minutes of preparation, 30 minutes at the actual place, and 10 minutes to finalize and agree next steps. Most of the time should be spent where the work happens, and the walk should have an end time set before it starts.
3. Is a Gemba walk the same as an audit?
No. An audit checks work against a standard and produces a compliance verdict. A Gemba walk is there to understand and to learn, which is why correcting people on the spot is discouraged. If the people on the floor experience the walk as an inspection, they will show you the compliant version of the process rather than the real one.
4. Is Gemba part of Lean Six Sigma?
Yes. Going to the Gemba is a Lean practice that Lean Six Sigma uses throughout a project, particularly to verify a suspected root cause against what is actually happening rather than accepting the team’s favorite explanation. It is also one of the daily routines that keeps improvements in place after a project closes.
5. Who should do a Gemba walk?
Every level of management, at a different frequency and with a different focus: team leaders daily, executives monthly. The frequency table above sets out each level and what it should be looking at.
