Gemba Walk
The structured observation that turns floor time into improvement fuel. Gemba is Japanese for "the actual place," where value is created. This skill gives observation walks a structured lens, a written output, and a clear handoff to the next improvement tool.
What a Gemba Walk Is (and Isn't)
You are there to understand, not to fix.
A gemba walk is an observation. It is not a management tour, not a problem-solving session on the floor, and not a spot audit. The purpose is to see the actual work, understand how it flows (or doesn't), and collect observations that can be analyzed away from the point of production.
The failure mode of most gemba walks is a lack of output: a manager walks the floor, talks to a few people, sees a few things, and returns to the office with nothing written down. Two weeks later, nothing has changed. The skill exists to close that gap.
Do not make changes on the floor during the walk. If you see an immediate safety hazard, address it, but note everything else and bring it back. Fixing things in the moment skips the analysis step, builds the habit of spot-fixing over systematic improvement, and signals to operators that gemba = criticism.
The 5 Observation Lenses
A structured lens for every walk.
Each lens directs attention to a different dimension of the work. The skill prompts for observations under each one rather than letting the walk drift toward whatever is most visible or most familiar.
Questions at the Gemba
What to ask vs. what not to ask
Questions at the gemba should open up the process, not put the operator on the spot. The goal is to understand how the work works, not to evaluate the person doing it.
- "Can you walk me through what you do first?"
- "What makes this step hard to do consistently?"
- "What happens when [this condition] occurs?"
- "Where do you go when you need [this material/information]?"
- "What's the one thing that would make this easier?"
- "How do you know when this step is done correctly?"
- "Why did you do it that way?" aimed at the person sounds like a challenge. Ask why about the process instead: "What makes this step hard?"
- "Shouldn't you be following the procedure?" leads to shutdown
- "How long does this take you?" creates performance anxiety
- Leading questions that imply what you already think is wrong
- Questions about other people or shifts, since this isn't the place
- Any question that can be answered "yes" or "no" and nothing more
What the Skill Produces
A prioritized observation list, not a wall of notes.
Every observation is structured: what was seen, the lens it falls under, a severity rating, and the recommended next tool. The output is designed to feed directly into an improvement queue or a kaizen event scoping session.
Three observations from a 45-minute walk. Severity: H = address this week, M = next event, L = monitor.
| Observation | Lens | Sev | Next Tool |
|---|---|---|---|
| Operators walking to far end of cell for torque wrench, avg 4 trips/hour observed | Standard Work | H | Standard Work / 5S |
| WIP pile of ~80 units between Form and Pierce, no FIFO lane visible | Flow | M | VSM Calculator |
| Operator on 2nd shift using different torque sequence than standard, not aware of update | Quality / Engagement | H | TWI Job Breakdown Sheet |
Common Gemba Mistakes
Three ways a gemba walk produces nothing
Examples
Works on the plant floor and in the clinic
A 45-minute walk through a five-station assembly cell with a focus on flow and walking waste. The skill structured the debrief from verbal notes into a prioritized observation list: 7 observations across the five lenses, 2 rated high severity, with recommended next tools for each.
"We walked the cell for about 45 minutes. I noticed [description]. The line leader mentioned [description]. On the way out I saw [description]." Three paragraphs of notes, unstructured. The skill sorted, categorized, and rated them.
A patient flow observation in an emergency department, from triage through disposition. The skill uses clinical vocabulary throughout: "patient," "provider," "boarding," "throughput." The engagement lens surfaces observations about whether nursing staff know the department's current wait-time target and whether they have a channel for raising process concerns.
Safety observations in a clinical gemba walk are flagged for immediate escalation to the charge nurse. The skill does not queue them with everything else. Patient safety issues are not held for the next improvement event.
What you get
A real run on the sample data
Unedited output. The sample message at the top went to Claude Sonnet 4.6 (an earlier-generation model, so a newer one may word things differently) with this skill pasted in, the same way the steps below show, on September 29, 2026. Scroll inside the frame to read the whole reply.
Installation
Describe what you saw. Get the structured output.
resources/examples folder.Related Skills