Operations Operating practice
Shows through respectful direct observation how value-creating work flows and where the process needs support.
Gemba Walk uses respectful observation at the place of work to show how work actually flows and where the process needs support. Conversations with the people involved help interpret observations and investigate suitable improvements.
What is happening where work occurs, and which process question should we investigate together?
Phases may be revisited; their order supports the work but does not replace domain judgment.
Purpose
Explain the learning question and observation boundary; get agreement from people involved.
Observe
Follow real work; record steps, interruptions, and tools.
Ask
Ask what the work aims to achieve, where difficulty occurs, and what would help.
Follow-up
Reflect observations, validate them with the team, and agree an investigation or support.
Review the result and open assumptions at the next suitable checkpoint. Record changes, ownership, and new evidence.
Use when: One concrete process where work happens; agree purpose, participation, and respectful boundaries in advance.
Learning question and observation boundary with agreement from the people involved.
Statements about the work goal, difficulties, and helpful support.
The review records observations checked with the team and an agreed investigation or form of support.
Fictional worked example
Learn through respectful direct observation how value-creating work actually flows and where the process needs support.
Record why the walk is happening and which process is in scope.
Understand order handoff to reduce customer wait.
Record observed steps, waits, and tools.
3 of 8 cases lack delivery address; two systems reconciled manually.
Capture perspectives with consent and context.
Fictional staff voice: “The address is often in the note but not the form.”
Agree what the team will investigate or what obstacle to remove.
Inspect data origin with the team; infer no cause or blame from one observation.
Fictional walk in digital order processing: three of eight sampled cases wait for a missing delivery address; staff reconcile it across two systems. Observation: duplicate entry. No cause is claimed yet; team will inspect where address data originates.
Start with a bounded question, clarify access and participants, and collect available evidence. Learn through respectful direct observation how value-creating work actually flows and where the process needs support.
When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.
On site, the flow of work is checked against open questions and targeted observation. Deviations, wait times, and local workarounds show where the process really breaks. The insights gained sharpen priorities for improvement without unnecessarily disrupting daily work.
A Gemba Walk brings leadership and analysis back to where work actually happens. It becomes solid through calm observation, precise questions, and respect for local knowledge rather than a quick search for solutions. A control round turns into learning once deviations, workarounds, and wait times are read as clues about system design.
Agree in advance on the observation focus, the conversational frame, and respectful conduct toward ongoing work at the site. The walk becomes especially fruitful when perceiving and asking come first, before immediate judgment or redesign. The end should include a few concrete observations checked for practical relevance with the people on site.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Your feedback helps shape the next improvements to methodatlas.
Prepare Gemba Walk with a clear question, roles, and sources.
To be confirmed
To be confirmed
Plan the full method Time: Set according to scope and available evidence
Complete this worksheet on paper or in your own document during the work.
Record why the walk is happening and which process is in scope.
...
Record observed steps, waits, and tools.
...
Capture perspectives with consent and context.
...
Agree what the team will investigate or what obstacle to remove.
...
Blank worksheet: start with a bounded question. Enter observed facts only, mark assumptions, and record open questions and sources.
How to Go to the Gemba · Lean Enterprise Institute
Expected artifact: Agreed observation purpose and process boundary
Agreed observation purpose and process boundary
Entry:
...
Expected artifact: Evidence-led process observations
Evidence-led process observations
Entry:
...
Expected artifact: Attributed frontline perspectives
Attributed frontline perspectives
Entry:
...
Expected artifact: Validated learning and support question
Validated learning and support question
Entry:
...
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/gemba-walk/run-sheet
Fitting alternatives with decision guidance, followed by other related methods.
Instead of Gemba Walk, when you want to measure an end-to-end flow with wait times and waste.
Visualizes workflows with roles and handoffs so problems, media breaks, and improvement opportunities become visible.
Sorts possible causes into categories and creates a shared picture for investigation and next tests.
Identifies waste along a process, prioritizes impact, and derives improvements.
Bundles observation, waste analysis, and experiments into a compact improvement process with a new standard.
Compares work as actually performed with the standard and reveals deviations that improve the process in a targeted way.
