In one minute
Follow real work end to end and ask operators what the process actually makes possible.
Go to the place where value is created, observe one real flow, ask about purpose, process and people, and record gaps between standard and reality without blaming workers.
The problem it addresses
Leaders optimise a process from dashboards while hidden handoffs and workarounds remain invisible.
A theme-park operator reports perfect control checks, yet night staff repeatedly bypass a failing alert to keep visitor flow moving.
When to use it
- Use Gemba Walk when leaders optimise a process from dashboards while hidden handoffs and workarounds remain invisible.
- The team can examine: A defined flow, permission to observe, frontline participation, baseline measures and a non-punitive charter.
- A relevant situation is: A theme-park operator reports perfect control checks, yet night staff repeatedly bypass a failing alert to keep visitor flow moving.
When not to use it
Do not use it to replace evidence, accountable judgement or affected people's participation.
Turning the walk into an inspection of people or treating a single visit as representative evidence.
Inputs required
A defined flow, permission to observe, frontline participation, baseline measures and a non-punitive charter.
Step-by-step process
1. Bound the decision and name its owner.
Write the scope, decision owner and people who can veto or revise the result before starting the workshop.
2. Collect the necessary evidence and affected perspectives.
Collect and date the necessary evidence: A defined flow, permission to observe, frontline participation, baseline measures and a non-punitive charter.
3. Choose one customer-facing flow and a question, not a verdict.
Record the evidence and decision criterion for: Choose one customer-facing flow and a question, not a verdict.
4. Obtain consent and follow the work across roles and handoffs.
Record the evidence and decision criterion for: Obtain consent and follow the work across roles and handoffs.
5. Ask operators where delays, workarounds and unsafe conditions occur.
Record the evidence and decision criterion for: Ask operators where delays, workarounds and unsafe conditions occur.
6. Compare observation with the written process and relevant data.
Record the evidence and decision criterion for: Compare observation with the written process and relevant data.
7. Agree one improvement test with those doing the work and revisit it.
Record the evidence and decision criterion for: Agree one improvement test with those doing the work and revisit it.
8. Record the output, next test and review trigger.
Store the artifact with its evidence links, owner, bounded next test and date or trigger for review.
AI automation lens
AI may sort authorised notes and expose missing evidence. It must not invent observations, silently decide for affected people or present a generated map as validated.
Visual model
Text alternative: Choose one customer-facing flow and a question, not a verdict; Obtain consent and follow the work across roles and handoffs; Ask operators where delays, workarounds and unsafe conditions occur; Compare observation with the written process and relevant data; Agree one improvement test with those doing the work and revisit it.
Interactive example
Scenario: A theme-park operator reports perfect control checks, yet night staff repeatedly bypass a failing alert to keep visitor flow moving.
Worked answer: Follow an actual shift, document the alert workaround and its cause with staff, then correct the system and review the safety signal.
Facilitation notes
Record disagreements before synthesising; ask whose evidence is missing; state who may revise the result.
Expected output
- An inspectable decision artifact, its assumptions and evidence, a responsible owner, a bounded next test and a review date.
- Agree one improvement test with those doing the work and revisit it.
- A named owner, test and review date.
Common mistakes
Turning the walk into an inspection of people or treating a single visit as representative evidence.
Quality checklist
- The decision and system boundary are explicit.
- Affected people and alternative accounts are included.
- Each important claim has a source or is marked as an assumption.
- An owner, safeguard and disconfirming signal are named.
Template
Knowledge check
Question: What mistake would undermine this method in the scenario?
Answer: Turning the walk into an inspection of people or treating a single visit as representative evidence.
Related tools
References
- Gemba Walk — method source (opens in a new tab). Accessed 2026-10-09.
- Further practice reference (opens in a new tab). Accessed 2026-10-09.
Method profile
The method structures a discussion and a test; it does not establish causal proof or guarantee success.