Gemba Walk
A Gemba Walk is a lean management practice of going to the place where the work is actually done, to understand the current situation through direct observation and questions before deciding anything. Gemba is Japanese for the actual place. In the group form recommended by James Womack of the Lean Enterprise Institute, everyone who touches a process walks it together from start to finish and asks about its purpose, how it really runs and how the people in it are involved.
Facilitation script
- 1
Brief the group before entering the work area: the process being walked, the purpose of the walk, the three themes of purpose, process and people, and the ground rule of observing and asking without fixing or judging.
10 min - 2
Start where the work starts. Ask the person at the first step to show how a real case is handled. Let the group watch a full cycle before anyone asks a question.
10 min - 3
Continue along the flow step by step. At each stop, have one or two people ask about purpose, process and people while the others take notes on what they see, including waiting, rework and workarounds.
30 min - 4
At the last step, ask how the output reaches the customer and what comes back as complaints or questions. Thank each team before you leave their area.
5 min - 5
Debrief in a separate room. Each person shares their most important observation first, facts before interpretations. Collect surprises and open questions on a flip chart.
15 min - 6
Agree two or three follow-ups with owners, and decide who goes back to the teams you visited to tell them what the group learned and what will happen next.
10 min
Tips
Ask the person doing the work to show you, then ask what gets in their way; you learn more from watching one real case go through than from a description of the standard process.
Keep the group small enough that it does not crowd a workstation or intimidate one operator.
Always close the loop with the teams you visited, because a walk that produces no feedback is remembered as an inspection.
Common pitfalls
Fixing things on the spot: a senior person's passing remark becomes an instruction, and people stop showing how the work really runs
Walking in department order or by the office layout instead of following the flow of work, so the handovers where most problems sit are never seen
Bringing a group so large that the work stops and people perform the official process for the visitors
Skipping the debrief, which leaves ten private impressions and no shared picture or follow-up
Never reporting back to the teams visited, so the next walk is met with guarded answers
Variations
For knowledge work with no shop floor, walk the process by following one real item, such as a ticket, an order or a claim, from desk to desk or screen to screen. A remote version has each person share their screen and work through a live case while the group observes. Used as preparation for a workshop, the walk comes first and the notes feed a process or value stream map the group then draws together. Genchi genbutsu, usually translated as go and see, is the wider principle behind the practice.
Where it fits
When to use it
A team is about to redesign a process that most of the people in the room have only seen on a slide
Departments disagree about where a delay or defect comes from, and each knows only its own part of the flow
Managers are making decisions about frontline work from reports and dashboards alone
You are preparing a mapping or improvement workshop and want the group to start from shared first-hand observation
An improvement was introduced some weeks ago and you want to see whether it is used as intended
When not to use it
The purpose is to check compliance or performance. That is an audit, and labelling it a Gemba Walk damages trust in later walks
The people doing the work have not been told why the group is coming. Brief them first or postpone
You want to understand individual customers' needs and behaviour outside your own operation. Use Simple Ethnography, Shadowing or a Service Safari
The problem is already well understood and what is missing is a decision or a root-cause analysis. Go straight to The 5 Whys or A3 Problem Solving
The site cannot safely host visitors at the moment, for example during a critical production run or an incident
Related methods
Frequently asked questions
What is a Gemba Walk?▾
A Gemba Walk is a lean practice in which managers and team members go to the place where the work happens, observe it directly and ask questions before taking any action. Gemba means the actual place in Japanese. The aim is to understand the current situation first-hand instead of relying on reports.
What questions do you ask on a Gemba Walk?▾
The Lean Enterprise Institute groups them under three headings: purpose, process and people. In practice that means asking what customer problem the step helps solve, how the work actually gets done, and how the people doing it take part in sustaining and improving it. Open questions such as asking someone to show you a case work better than why-questions that sound like an accusation.
Who should take part in a Gemba Walk?▾
For a group walk, bring the people who touch the process across departments, so that each sees the steps before and after their own. Three to ten people is a workable size in most workplaces. A leader can also walk alone or with one colleague as a regular routine.
How is a Gemba Walk different from an audit?▾
An audit checks whether work conforms to a standard and produces findings. A Gemba Walk is for learning how the work really runs and why. Nobody is scored, and problems that come up are treated as information about the process, not about the person.
Can you do a Gemba Walk for office or remote work?▾
Yes. Follow one real work item through every step it passes, sitting with each person or watching their shared screen as they handle it. The same rules apply: follow the flow, watch a real case, ask about purpose, process and people, and debrief afterwards.
Plan your next workshop with AI
Workshop Weaver helps you combine methods like Gemba Walk into a complete, timed agenda in minutes.
Try it freeMethod descriptions on Workshop Weaver are original content written by our team, based on established facilitation practices. This method was inspired by work from Lean Enterprise Institute (James P. Womack).