Practical guide · Lean leadership and employee engagement
What is a gemba walk? How to do one
Short answer
A gemba walk is a planned visit by a leader to the place where the work is done, to watch the process, ask the people doing it what gets in their way, and follow up on what they learn. Gemba is Japanese for the actual place. To do one, pick a theme, walk a set route, watch before you ask, ask open questions, write down what you saw and close the loop.
Last updated:
What is a gemba walk?
A gemba walk is a leader going to where the work happens, on a plan, to see how it really runs. Gemba (also spelled genba) is Japanese for "the actual place". In a plant that is the shop floor, but it can be a warehouse, a lab, a site or an office.
Three things make it a gemba walk and not a tour. You see the work yourself instead of reading a report. You ask why, and listen to the people who do the job. And you show respect: you are there to learn what makes the work hard, not to catch anyone out.
It is not an audit or an inspection. An audit compares an area with a standard and usually scores it. A walk is for understanding, so nobody is graded. See gemba walks vs audits for the full comparison.
Gemba and genchi genbutsu are close but not the same. Gemba is the place. Genchi genbutsu is the principle of going to that place and seeing the facts for yourself before you decide. A gemba walk is one way to practise it.
Why do it, who walks and how often
Reports show what was measured. A walk shows what they leave out: the workaround at a machine, the instruction nobody follows because it is out of date. The people doing the work usually know about these already. A walk gives them a regular chance to tell someone who can act.
| Who | Rhythm | What the walk is for |
|---|---|---|
| Team leader or supervisor | Daily, as part of the start-of-shift routine | Safety, the day's plan, problems from yesterday |
| Production or area manager | Weekly, on a fixed day | One theme per walk, such as flow or standard work |
| Plant manager and leadership team | Weekly or monthly, on a rota across areas | Seeing real conditions and checking that earlier actions closed |
Fix the rhythm in leader standard work. A short walk that always happens beats a long one that gets cancelled.
How to do a gemba walk, step by step
- 1
Prepare a theme
Choose one thing this walk is for, such as waiting between steps, how work instructions are used, or how material reaches the line. Tell the area the walk is to learn.
- 2
Walk the route
Plan the stops in the order the work flows, from material coming in to product going out. Go while the work is running, and keep it short, around half an hour.
- 3
Observe before you ask
At each stop, stand and watch several cycles of the work. Look at the people, the product, the tools and the layout. Hold back your opinion until you have seen what is actually going on.
- 4
Ask open questions
Ask what, why and "show me" questions, such as "What gets in your way here?" and "What did you do the last time this happened?". Avoid questions that can be answered yes or no, and avoid ones that carry a verdict.
- 5
Note what you saw, not what you think
Write facts: "three boxes of parts waiting at station 4", not "poor flow". Facts can be checked and acted on.
- 6
Follow up and close the loop
Give each action that needs doing an owner and a date. Tell the team what will happen. Start the next walk by checking those actions. If nothing comes back, people stop telling you things.
The post how to perform an effective gemba walk goes through each step in more depth. If part of the team is off site, digital gemba walks covers what carries over.
A gemba walk checklist: what to look at
A checklist points your attention and is not a score. Use the group that matches your theme.
| Area | What to look at | A question to ask |
|---|---|---|
| Safety | Guards, walkways, how people lift and reach, whether anyone works around a hazard | What is the most awkward or risky part of this job? |
| Quality | How defects are found, what is done with a bad part, whether the standard is visible | How do you know this part is good? |
| Flow and waste | Piles of parts waiting, walking, searching, rework, stopped machines | Where do parts wait longest, and why? |
| Standard work | Whether the written method matches what is done, and whether it is current | Show me how you do this. Is that how it is written? |
| 5S and visual management | Whether things have a place, whether a problem shows up at a glance | Could someone new tell at a glance if something is wrong? |
| People | Skills, cover for absences, whether ideas get a response | What have you suggested lately, and what happened to it? |
The free [gemba walk checklist](/templates/gemba-walk-checklist) has 30 prompts in these six groups, a walk plan and a findings table. The [gemba walk field guide](/templates/gemba-walk-field-guide) adds a pocket set of questions by area.
An example of a gemba walk
This walk is illustrative. A production manager walks a machining area on a Tuesday with the theme "where does work wait?". The walk takes 30 minutes.
| Stop | What the manager saw | A question asked |
|---|---|---|
| Bar stock rack | Material pulled for the whole week, stacked in the aisle | How do you decide how much to pull at once? |
| Lathe | A pile of finished parts waiting for drilling, and the operator checking the next job's drawing | What happens to those parts after you finish them? |
| Drilling | The operator waiting for a fixture that another cell has | Show me what you do when you need it. |
| Inspection bench | Parts queued, with no sign of which are urgent | How do you know which job to do first? |
The manager fixed nothing on the spot. The notes became three actions with owners and dates: a second fixture, a marked limit for the pile before drilling, and a way to flag urgent jobs at inspection. The next walk began at the drilling cell.
Common mistakes
- Turning it into an audit. Scoring people or areas teaches them to hide problems. Watch the process, not the person.
- Walking without a theme. Without a focus it becomes a tour and nothing comes out of it.
- Fixing things on the spot. Questions that help the team see the problem teach more than solutions. A safety hazard is the exception: deal with it at once.
- Not following up. A walk with no actions, or actions nobody checks, costs more than not walking, because people stop trusting it.
For worked walks by area and purpose, see the gemba walk examples. To keep walks and their follow-ups in one place, see audit management.
Go deeper
This page is the short version. These guides cover each part in full.
- How to Perform an Effective Gemba Walk on the Shop FloorEach step of a walk in more depth, with the questions to ask and how to follow up.
- What is Gemba in Lean Manufacturing?What gemba means, how it differs from genchi genbutsu, and why lean leaders decide at the place the work happens.
- Gemba Walks vs Audits: Key Differences Every Manufacturer Should KnowWhy a walk and an audit have different purposes, and how to run both without one spoiling the other.
- Digital Gemba Walks: Modernize Shop Floor ObservationsRecording walks on a phone or tablet, and what changes when part of the team is remote.
- Gemba Walks: From Compliance Checklists to Real ChangeHow to keep a checklist from taking over a walk, and how to turn findings into change.
All our articles on this subject are in the lean leadership and employee engagement topic.
Free templates and tools
- Gemba walk checklistA walk plan and route, 30 prompts in six groups and a findings table with owners and due dates.
- Gemba walk field guideA 20-page pocket guide: the rules, 48 questions by area with good and warning answers, a 30-day route and the follow-through loop, plus an action-log workbook.
- Leader standard work templateA team leader's daily, weekly and monthly routine with a box per day, follow-ups and a weekly review.
Doing this in LeanSuite
Audit management
Runs scheduled audits and tracks the findings to closure.
See Audit managementDaily Issue Management
Gives frontline teams one place to flag, track and resolve issues in real time, so the same fires stop coming back every week.
See Daily Issue ManagementTiered Meetings
Puts daily huddles on live, cascaded dashboards, so the shop floor and the top floor see the same numbers and act on them at every tier.
See Tiered MeetingsKaizen & Projects
Manage every improvement project in one visual hub, from a small kaizen event to a full DMAIC project, and track each one through to results.
See Kaizen & Projects
See it on your own lines
Bring the problem you are working on to a 45-minute demo. Or look around with sample data first, or pilot LeanSuite on your own lines for 90 days, with the setup done by our team.
FAQ
Questions about what is a gemba walk
A gemba walk is a planned visit by a leader to the place where the work is done. The leader watches the process, asks the people doing the work what gets in their way, and follows up on what they learn. It is for understanding the work, not for inspecting people.
Gemba is Japanese for the actual place. In lean it means the place where value is created, most often the shop floor, but it can also be a warehouse, a lab or an office. The idea is that problems are understood best by going there and seeing the work.
Pick a theme for the walk, plan a route that follows the flow of the work, watch several cycles at each stop before you ask anything, ask open questions, write down what you saw rather than what you think, and give every action an owner and a date. Check those actions on the next walk.
Ask open questions about the work itself, such as where parts wait longest, what makes the job hard, what happens when something goes wrong, and to be shown how a task is done. Questions about waiting, walking, searching and rework point to waste. Avoid questions that blame a person.
An audit checks an area against a standard and usually scores it, so findings are about conformance. A gemba walk is for learning how the work really runs, so nobody is graded. If a walk starts to feel like an audit, people hide problems and the walk stops being useful.
A regular, predictable rhythm matters more than length. A common approach is for team leaders to be on the floor every day and for managers to walk weekly on a fixed day, written into leader standard work. Keep walks short enough that they do not get cancelled.
Gemba is a place: where the work happens. Genchi genbutsu is the principle of going to that place and seeing the facts for yourself before you decide. A gemba walk is one way of practising genchi genbutsu.
Related guides and tools
More method guides
- The 6 Ms of production
- Poka-yoke
- Model area 90-day plans
- Moving from Excel to one system
- Reducing machine downtime: a worked month
- Andon and jidoka
- Cycle time vs lead time, worked through
- Root cause analysis
- How many operators a line needs
- Reducing scrap and rework: a worked month
- Unsafe acts and unsafe conditions
- Just culture
- Stop-work authority
- Material review board (MRB)
- What is an NCR?
- Problem solving methods
- Quad chart
- OEE calculation
- Quality assurance vs quality control
- SOP meaning and format
- Job hazard analysis
- Near miss reporting
- Fishbone diagram
- Pareto chart
- Histogram
- Control chart
- What is lead time
- What is operational excellence
- How to improve product quality
- Preventive vs predictive maintenance
Or browse the topics, the full library and the lean glossary.
Rather see it on your own problem?
Bring the problem you are stuck on, and we will show you on a call how LeanSuite handles it.

