Methods & Guides
How to Conduct a Gemba Walk: A Step-by-Step Guide
A practical guide for lean practitioners, operations managers, and CI professionals. Covers preparation, observation, questions that work, and the follow-up most guides skip.
A practical guide for lean practitioners, operations managers, and CI professionals. Covers preparation, observation, questions that work, and the follow-up most guides skip.
Most process problems are invisible from a desk. The data tells you something is wrong. The report confirms it. But the cause stays hidden until someone goes to look.
That is what a Gemba Walk is for.
Gemba (現場) is a Japanese term meaning "the actual place." In a Lean context, it refers to the location where value is created: the shop floor, the ward, the service counter, the warehouse. A Gemba Walk is the deliberate practice of going there, observing work as it actually happens, and asking the people who do it what is getting in their way.
It is not an inspection. It is not a tour. And it is definitely not a clipboard exercise where a manager ticks boxes and leaves. Done well, a Gemba Walk is one of the most powerful tools in continuous improvement because it replaces assumption with evidence.
This guide covers the full process: how to prepare, what to do during the walk, the questions that open people up rather than shut them down, and the follow-up step that most teams skip entirely.
A Gemba Walk is a structured visit to the place where work happens, carried out by a leader or improvement practitioner with the purpose of observing, learning, and identifying waste or problems directly.
The concept originates from the Toyota Production System, where managers were expected to spend significant time on the factory floor rather than managing from a distance. Taiichi Ohno, one of Toyota's chief architects, famously drew circles on the floor and asked engineers to stand in them and observe until they truly understood what was happening. The point was not to find fault. It was to see reality.
This distinction matters because many organisations run Gemba Walks badly by confusing them with something else.
| What it is | What it is not |
|---|---|
| Observing how work actually happens | Auditing whether rules are being followed |
| Learning from the people doing the work | Evaluating individual performance |
| Identifying systemic waste and barriers | Fixing problems on the spot |
| Building trust through regular presence | A one-off management visit |
The moment a Gemba Walk becomes an inspection, people stop telling you the truth. They tidy up, work to the standard they know you want to see, and hide the workarounds that reveal where the real problems are.
Gemba Walks are not exclusive to manufacturing. Any environment where work follows a process can benefit.
Manufacturing: production lines, assembly cells, material handling areas
Healthcare: clinical pathways, ward rounds, pharmacy dispensing, patient admissions
Financial services: back-office processing, claims handling, compliance checks
Public sector: service delivery points, case management, contact centres
The principle is the same regardless of setting: go to where the work happens and observe it directly.
A Gemba Walk without preparation is just a wander. You need a theme, a route, and a basic understanding of the current state before you set foot on the floor.
Every walk should have a single theme. Trying to observe everything at once means you observe nothing well. Common themes include:
Safety: near misses, ergonomic risks, PPE compliance, housekeeping
Quality: defect rates, rework points, inspection steps, first-pass yield
Flow: waiting times, bottlenecks, handoffs, batch sizes, material movement
Productivity: cycle time against takt time, idle time, downtime causes
People: workload balance, skill gaps, unclear instructions, workarounds
Pick the theme that connects to a live problem or a current improvement priority. If your KPIs show a rise in defects, make quality the focus. If lead time is creeping up, focus on flow.
Before the walk, look at relevant performance data for the area you are visiting. Downtime logs, quality reports, throughput figures, complaint data. The data tells you where to look. It does not tell you why. That is what the walk is for.
Do not lead with the data during the walk. Showing someone a report and asking them to explain it puts them on the defensive. Use the data to guide your observations, not to open the conversation.
A surprise walk reads as a raid. People become defensive, tidy up, and work to the version of the process they think you want to see. A planned, regular walk builds trust over time because people know it is not about catching them out.
Inform the team in advance. Explain the purpose: you are there to understand how the work is done and what gets in the way. You are not there to evaluate individuals.
A structured checklist keeps your observations consistent across walks and ensures you do not miss key areas. SimplicityHub's free Gemba Walk Checklist Template gives you a ready-made framework you can adapt to your theme and environment.
The walk itself has a structure. It is not a conversation followed by a look around. You observe first, then you ask questions.
Position yourself where you can watch a full work cycle without getting in the way. Then watch several cycles before you say anything. Most people talk too soon and see too little.
What you are looking for at this stage:
Does the work match the standard? Compare what you see to any posted standard operating procedures or visual controls.
Where does the operator wait, walk, or reach further than they should?
Where does work accumulate? Where does it stall?
What workarounds are in use? Improvised tools, sticky notes, informal queues?
Vague notes are useless. Write down specific observations. "Operator at station 4 walks to the shared tool rack approximately eight times per shift" is actionable. "Motion waste observed" is not.
Once you have observed, engage the operator. The goal is to understand their experience of the process, not to quiz them on the standard.
Questions that open people up:
"What is the most frustrating part of this task?"
"What slows you down?"
"Is there anything you need that you do not have?"
"What would make this job easier to do right the first time?"
"Where do errors tend to happen, and why do you think that is?"
Questions that shut people down:
"Why did you do it that way?"
"Is this how you are supposed to do it?"
"Do you know what the standard says?"
The difference is intent. One set of questions invites honesty. The other signals judgement. According to the American Society for Quality, effective Gemba practice depends on psychological safety: operators must believe their input will be used to improve the system, not to evaluate them personally.
This is the single most important principle of a Gemba Walk. When you see a deviation from the standard, the question is not "why did this person do this?" The question is "why does the process allow or create this condition?"
Workarounds are particularly valuable. If someone has invented a shortcut or an unofficial fix, that is a signal the formal process is not working. It is not a sign of poor discipline. It is a sign of a design problem.
A group of more than three people feels like an audit. Ideally, take one other person: an area owner, a team leader, or a colleague from a different department who can bring a fresh perspective. Two sets of eyes see different things. Five sets of eyes intimidate the people you need to talk to.
Long enough to observe the work properly. Short enough to stay focused on your theme.
| Walk type | Typical duration |
|---|---|
| Daily supervisor walk (one cell) | 15 to 20 minutes |
| Themed improvement walk (one area) | 30 to 45 minutes |
| Senior leader walk (cross-functional) | 45 to 60 minutes |
Resist the temptation to cover the whole operation in one pass. One area observed well is worth more than five areas glanced at.
This is the step most teams skip. And it is the step that determines whether a Gemba Walk programme actually works.
A walk that produces no visible action destroys trust faster than not walking at all. If people take the time to tell you what is broken and nothing changes, they will stop telling you the truth. Eventually, they will stop engaging entirely.
Within a few hours of the walk, review your notes with anyone who accompanied you. While observations are fresh:
Identify the two or three most significant findings
Separate quick fixes from systemic issues that need deeper investigation
Assign an owner and a target date for each action
Do not try to solve everything from one walk. Prioritise the issues that are blocking the work most directly.
Before you leave the area, or at the very latest the next day, go back and tell the team what you observed and what you are going to do about it. Specifically.
Not: "We identified some opportunities and will be looking into them."
But: "You mentioned the torque gun is shared across three stations. We are going to relocate one to station 4 by Thursday."
An obstacle that visibly gets fixed is what earns you honest answers on the next walk. This is the trust mechanism at the heart of the Gemba Walk practice.
Not everything you find on a Gemba Walk can be resolved with a quick action. Some issues point to deeper systemic causes that need structured investigation.
Use 5 Whys analysis to get past the symptom and find the root cause
Feed recurring themes into a Kaizen event for a focused improvement sprint
Where waste is widespread, use an 8 Wastes Assessment to map the full picture before prioritising
Keep a simple log of what was observed, what action was agreed, who owns it, and whether it was completed. Review this log at the start of each walk. It tells you whether the programme is generating real change or just generating notes.
| What to track | Why it matters |
|---|---|
| Action closure rate | Shows whether follow-through is happening |
| Repeat issue frequency | Flags areas where root causes are not being addressed |
| Lead time or waiting time | Measures whether flow is improving |
| Employee ideas implemented | Signals engagement and builds trust |
Cadence matters more than duration. A short, regular walk is more valuable than an occasional deep dive.
Frontline supervisors: daily, covering one area or cell (15 to 20 minutes)
Team leaders and department managers: weekly, with a specific theme
Senior leaders: monthly, cross-functional, focused on strategic improvement priorities
The walk becomes most powerful when it is built into leader standard work. Not a reaction to a problem. A routine.
The biggest mistake organisations make with Gemba Walks is treating them as a one-off exercise. A single walk produces observations. A programme of regular walks produces improvement.
The structure is straightforward: prepare with a theme, observe before you speak, ask questions that invite honesty, and follow up with visible action. Each step reinforces the next. Preparation makes observation focused. Focused observation makes questions sharper. Sharper questions surface better problems. And visible follow-up earns the trust that makes the next walk more honest than the last.
A Gemba Walk does not exist in isolation. The findings it generates feed directly into the broader continuous improvement system.
Use 5 Whys analysis when a walk surfaces a recurring issue and the root cause is not obvious
Use a Kaizen event when the walk identifies a process that needs a focused improvement sprint
Use the 8 Wastes Assessment when waste is widespread and you need to map it systematically before prioritising
Explore the full 10 Essential Process Improvement Tools to build out your CI toolkit beyond the walk itself
The Gemba Walk is where the evidence comes from. The tools above are how you act on it.
A structured checklist keeps your observations consistent, ensures you cover the right ground, and gives you a record you can review over time. Download SimplicityHub's free Gemba Walk Checklist Template to get a ready-made framework you can adapt to your theme, your environment, and your team.
A Gemba Walk is a structured visit to the place where work actually happens — the shop floor, ward, or service area — carried out by a leader or improvement practitioner. The purpose is to observe work directly, understand how it is performed, and identify waste or problems that are invisible from a desk or report.
It depends on the scope. A daily supervisor walk covering one cell typically takes 15 to 20 minutes. A themed improvement walk for a single area runs 30 to 45 minutes. A senior leader cross-functional walk is usually 45 to 60 minutes. Consistency and focus matter more than duration.
Frontline supervisors should walk daily, covering one area or cell. Team leaders and department managers should walk weekly with a specific theme. Senior leaders should walk monthly, focused on strategic improvement priorities. Regular cadence is more valuable than occasional deep dives.
Ask open questions that invite honesty rather than defensiveness. Effective questions include: 'What is the most frustrating part of this task?', 'What slows you down?', 'Is there anything you need that you do not have?', and 'What would make this easier to do right the first time?' Avoid questions that signal judgement, such as 'Why did you do it that way?'
A Gemba Walk is focused on learning and improvement — observing how work actually happens and understanding what gets in the way. An audit checks whether rules are being followed and evaluates compliance. When a Gemba Walk becomes an audit, people stop telling you the truth and work to the standard they think you want to see.
Yes. Gemba Walks apply to any environment where work follows a process. They are widely used in healthcare (clinical pathways, ward rounds, pharmacy), financial services (back-office processing, claims handling), public sector services, and contact centres. The principle is the same: go to where the work happens and observe it directly.
A ready-to-use checklist to structure your next walk, plus 80+ other free Lean Six Sigma templates.