Why do leaders do gemba walks?
Three outcomes come from regular gemba walks, and none of them comes from a report:
- Problems are seen at the source. Waiting, searching, rework and workarounds are obvious on the shop floor and invisible in a dashboard.
- Standards stay honest. A leader who checks the standard work against the real work finds the drift early, while it is still cheap to fix.
- Trust builds on the front lines. Team members who are asked "what gets in your way?" and see something happen as a result keep raising problems.
How do you run a gemba walk?
The gemba walk process most lean organisations use runs from Toyota's genchi genbutsu to today's digital gemba walk. To conduct gemba walks that produce valuable insights rather than a tour, follow the same seven steps each time:
- Prepare. Read the area's tier board before you go: yesterday's reds, overdue actions and open escalations tell you what to look for.
- Choose a theme. One per walk: a standard, a measure that has been red, safety, or flow through one process. A theme keeps the walk focused enough to identify problems instead of skimming past them.
- Go and see. Stand at the work and watch several cycles before speaking. Compare the real work processes with the standard and note where people wait, search, walk or rework.
- Ask why. Ask open questions of the team members doing the work, then listen. "What gets in your way?" gets more than "Is everything OK?"
- Show respect. Don't solve or correct on the spot unless something is unsafe. Thank people for showing you a problem; that is how employee engagement is earned.
- Record. Capture observations, deviations and problems with an owner and a date at the place, in real time, with photos where useful. Notes written up later lose the detail.
- Follow up. Findings go on the team's tier board, repeat problems go to structured problem solving, and the next walk checks what changed.
What does a gemba walk look like on a factory floor?
On factory floors a good walk is quiet and specific. Take a plant manager's Tuesday walk on a packaging line, with changeovers as the theme. The board shows two late starts after changeovers this week. At the line, the manager watches one changeover from last good pack to first good pack without interrupting. The operator walks twice to the tool crib for a change part that isn't kept at the line, and the first three packs are rejected because the film setting on the standard work sheet is out of date.
Following the work on a route map shows waste that a walk-past would miss.
The manager asks the operator what slows changeovers down most, and the answer matches what was just seen. Two actions go on the line's Tier 1 board before the manager leaves: move the change parts to a shadow board at the line (team leader, by Friday) and correct the film setting in the standard (process engineer, by Thursday). On Thursday's walk the manager checks both. Nothing was fixed by the manager on the spot, yet two process improvement actions now have owners, and the operator has seen that raising a problem leads to a change.
A food manufacturer in regional Victoria made the production manager's walk a fixed 7:15 am routine on one line each day with a theme (changeover standard, labelling checks, 5S). Within a quarter the Tier 1 boards carried fewer repeat issues, because the problems operators had been living with were being raised and owned in the daily huddle instead of worked around.
What is on a gemba walk checklist?
A checklist keeps the walk about observing and learning rather than inspecting. A good one fits on a page and covers:
- Before: the theme, the board review (yesterday's reds, overdue actions, open escalations), the fixed time.
- Safety and conditions: anything unsafe right now; the area against its 5S standard; standard work visible and current.
- The work: three cycles watched; where the operator waits, searches, walks or reworks; equipment workarounds; how quality is checked.
- Performance and problems: does the floor agree with the board; the biggest problem today; overdue actions and their blockers; escalations without an answer.
- People: "what gets in your way?", "what would you change?", skills cover for the tasks being done.
- After: observations, deviations from standard, problems with owners and dates, items to escalate, one thing to recognise.
Download the printable version at the gemba walk checklist.
What questions should you ask on a gemba walk?
Fifteen questions, grouped the way a tier board is: Safety, Quality, Delivery, Cost and People. Safety: is anything unsafe right now; does the area match its standard; is the standard work visible? Quality: how do you know this output is good; what was the last defect and what happened to it? Delivery: are we to plan, and if not, why; where did the time go this hour? Cost: where do you wait, search or rework; what is the workaround you use most? People: what gets in your way; what would you change; who is doing a task they are not signed off for? The full list with the reason behind each question is on the gemba walk questions page.
Gemba walk vs audit vs tier meeting
| Gemba walk | Layered process audit | Tier meeting | |
|---|---|---|---|
| Purpose | Understand the work and its problems | Check compliance with a standard | Review performance and assign actions |
| Who | Leaders at every level | Leaders at set frequencies | The team and its leader |
| Where | At the work | At the work | At the board |
| Output | Observations, questions, actions | Pass/fail per item, corrective actions | Actions, escalations, decisions |
| Cadence | Daily (team leaders) to weekly (site leaders) | Per the audit schedule | Every shift or day |
They reinforce each other: the walk finds what the audit misses, the audit keeps the standard honest between walks, and the tier meeting is where both become owned actions.
How often should leaders do gemba walks?
Team leaders daily as part of their standard work, supervisors and area managers several times a week, site leaders at least weekly. The frequency is written into leader standard work and audited like any other standard. Twenty to forty-five minutes for one area and one theme is enough; longer walks cover more ground and see less.
What is a virtual or digital gemba walk?
A virtual gemba walk uses video or a live board to observe a remote site when travel is not possible. It is a useful supplement, not a replacement: the point of the gemba is physical presence. A digital gemba walk is different: the walk is physical, but the checklist, observations, photos and actions are captured on a phone at the place they are made, so nothing is lost on the way back to the office and the findings appear on the team's tier board the same day.
What makes gemba walks effective, and what goes wrong?
Effective gemba walks share a few habits, and the common mistakes are their opposites:
- Walking to be seen rather than to see. A quick lap of the shop floor teaches nothing. Stand in one place long enough to see the work.
- Solving problems on the spot, which teaches the team to wait for the leader. Coach with questions and let the team own the fix.
- No theme, so the walk becomes a tour and nothing is seen in depth.
- Inspecting people instead of processes. The aim is to identify inefficiencies in the process, not to find someone to blame. Team members who feel judged hide problems.
- Observations never recorded, so nothing changes and the team stops talking.
- No follow-up in the tier meeting, so the same finding is made next week.
- Walking only when something goes wrong. Regular gemba walks at a known time build the habit; walks that happen only after a bad week feel like an investigation.
Done well, regular walks foster a culture of continuous improvement: leaders see the real problems, the people closest to the work lead the improvement efforts, and the organisation learns to improve processes every week rather than waiting for a crisis to go and look.