Problem Solving & Quality · Observe

Gemba Walk

Go to the place where the work happens, watch the real process, ask open questions and write down what you see — not what you expected.

Time1 h
FormatSmall group
StageObserve

Gemba Walk: what it is and why it works

A gemba walk means going to the place where the work is actually done (the line, the control room, the warehouse, the job site) to observe the real process with one specific question in mind. The walker goes at the time the problem occurs, watches at least one full cycle before speaking, records what is seen, heard and measured, and asks the people doing the work open questions. The walk ends with facts and follow-ups, not instructions, and the walker later reports back on what was done with the input.

Meeting-room problem solving relies on averages, reports and memories, which smooth away the details where causes hide: a workaround, a hard-to-read gauge, material staged in the wrong place. Direct observation corrects that bias and builds trust, because people see that their knowledge counts. A gemba walk is quick to start, but it is not a counting method; when numbers are needed, observations should lead to a check sheet or measurements. It is the natural way to begin an as-is flowchart, it answers the Where and How of 5W2H, and it supplies the observed facts that a fact–opinion sort then separates from assumptions. Site safety rules and PPE requirements always apply.

What you need

One specific question to explore
Knowledge of when and where the problem occurs
PPE, site access and a host from the area
A notebook or observation sheet, and a timer or simple measuring tools
Enough time to stay put, often an hour or more

What you get

Written observations with times and locations
Answers from the people doing the work, in their own words
A list of follow-ups and data needs with owners
Leads for the as-is flowchart and cause analysis
Feedback to the area on what will happen next

When to use it

When the problem is being solved from a meeting room with slides and averages.

How to do it, step by step

Pick one question to explore on the walk — not a general tour.
Go to the exact place where the problem appears, at the time it appears, with PPE and a notebook.
Watch a full cycle before speaking; note what you see, hear and measure.
Ask the people doing the work open questions: what is hard, what changed, what do you do when it goes wrong?
Leave with facts and follow-ups, never with instructions given on the spot; thank people and report back what you did with their input.

Worked example: Long changeovers on a bottling line

Illustrative scenario — figures are realistic but not from a real company.

A beverage co-packer's changeovers on a 600-bottle-per-minute PET line average 95 minutes against a 60-minute standard. Downtime reports blame 'mechanical adjustments'. The operations manager plans a gemba walk with one question: where do the extra 35 minutes go?

She scheduled the walk for the next flavor-and-format changeover on second shift, when most delays had been logged, and arrived in PPE with a stopwatch and notebook.
For the first 40 minutes she only watched and timed. Mechanical adjustments took 32 minutes, close to standard. Before they started, the crew waited 18 minutes for change parts that had not been brought from the tool crib.
She asked open questions such as 'What makes this changeover hard?' The filler operator explained that the crib closes at shift change and parts must be signed out by a day-shift technician.
She also saw operators searching a drawer for the right labeler setup sheet, which existed in several versions.
She left with three follow-ups (crib access, a pre-staged change-part cart, document control for setup sheets) and gave no instructions on the spot.

Result. Within a month, staging change parts on a cart before the line stopped, and giving second-shift leads crib access, cut the average changeover to 68 minutes. The meeting-room theory had explained only a small part of the gap. When the manager went back to show the crew the results, they offered the next idea: quick-release guides on the labeler.

Open it in the FieldKit Problem Solving app → Get the Problem Solving template pack — join the waitlist

Common pitfalls and how to avoid them

Turning the walk into a general tour.Carry one question and stay where it can be answered.
Giving instructions on the spot.Record, ask and follow up through the normal line of responsibility; on-the-spot orders undercut supervisors and stop people talking.
Walking at a convenient time rather than when the problem occurs.Go during the shift, product run or condition in which the problem shows up, including nights and weekends.
Never closing the loop.Report back to the people you talked to on what changed; otherwise the next walk will be met with polite silence.

Frequently asked questions

What is the purpose of a gemba walk?

To see how work is actually done, understand problems at their source and learn from the people closest to the process. In problem solving, a gemba walk replaces assumptions and averages with direct observation of the conditions in which the problem occurs. It is also a leadership practice that shows respect for frontline knowledge and builds the trust needed for people to raise problems.

What questions should you ask on a gemba walk?

Open, non-judgmental ones: What are you working on? What makes this job hard? What changed recently? What do you do when it goes wrong? How do you know it is right? Avoid questions that imply blame or suggest the answer you expect. Listen more than you talk, and write down what people say in their own words.

How long should a gemba walk take?

Long enough to observe at least one full cycle of the process under study and to talk with the people doing it, often 30 to 90 minutes for a focused problem-solving walk. Quick drive-by visits tend to show only what people want visitors to see. For long-cycle processes, come back several times rather than trying to see everything at once.

Origin

Gemba (“the real place”) — Japanese lean practice; popularized in the West by Masaaki Imai, Gemba Kaizen, 1997.

Used in these playbooks

One-page improvement cycle 3 weeks

Three weeks for a local problem owned by a team leader: see it on site, tell it on one A3, choose the countermeasure openly, pilot it and make it the new standard.

Related methods

More in “Observe”

Go where the problem happens and collect facts, counts and timelines — not opinions.