Complete firstClear scope
One concrete process where work happens; agree purpose, participation, and respectful boundaries in advance.
Without a boundary, data, perspectives, or flows become mixed.
Method guideOperations
Gemba Walk
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityLow
Time30-120 min
Participants2-6
FormatWorkshop
MaturityCanonical
01
Prerequisite
What needs to be finished first
Complete firstAccess to evidence
Relevant people and sources can be included.
Gaps remain visible; missing evidence must not be invented.
02
Preparation
What needs to be ready before start
Materials
Shared workspace, accessible sources, and a decision log.
People / roles
Host · observing leader · frontline staff
Pre-read
Clarify the question, timeframe, data access, roles, and known uncertainties in advance.
Time needed
30–60 minutes for one bounded walk; repetition may be needed to verify observations.
Setup
Create a shared version. Label facts, assumptions, and decisions separately.
03
Core question
The one question this method answers
What is happening where work occurs, and which process question should we investigate together?
04
Flow
Phases with goal, actions, output and pitfall
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.
Purpose, process observation, and agreed question
Fictional worked example
Learn through respectful direct observation how value-creating work actually flows and where the process needs support.
Purpose
Record why the walk is happening and which process is in scope.
Understand order handoff to reduce customer wait.
Observation
Record observed steps, waits, and tools.
3 of 8 cases lack delivery address; two systems reconciled manually.
Perspective
Capture perspectives with consent and context.
Fictional staff voice: “The address is often in the note but not the form.”
Follow-up
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.
- 1
Purpose
Clarify purpose and process boundary
Goal
Do people know why the work is being observed?
Inputs for this step
- Learning purpose, host, and area
Actions
- Explain the learning question and observation boundary; get agreement from people involved.
- Do people know why the work is being observed?
Output
Agreed observation purpose and process boundary
Agreed observation purpose and process boundary
Quality check
Do people know why the work is being observed?
Pitfall
Walk becomes personnel inspection Observe process conditions and ask with genuine curiosity.
Timing: Part of the agreed work block; research may be separate.
- 2
Observe
Observe work directly
Goal
Is the note observation rather than judgment?
Inputs for this step
- Real work item and process steps
Actions
- Follow real work; record steps, interruptions, and tools.
- Is the note observation rather than judgment?
Output
Evidence-led process observations
Evidence-led process observations
Quality check
Is the note observation rather than judgment?
Pitfall
Proposed fix biases observation Describe purpose, process, and actual work first; separate hypotheses.
Timing: Part of the agreed work block; research may be separate.
- 3
Ask
Ask respectfully
Goal
Are the people doing the work speaking for themselves?
Inputs for this step
- Open questions for people doing the work
Actions
- Ask what the work aims to achieve, where difficulty occurs, and what would help.
- Are the people doing the work speaking for themselves?
Output
Attributed frontline perspectives
Attributed frontline perspectives
Quality check
Are the people doing the work speaking for themselves?
Pitfall
Staff cannot speak candidly Be transparent about purpose and respond respectfully to observations.
Timing: Part of the agreed work block; research may be separate.
- 4
Follow-up
Reflect and agree next step
Goal
Is the observation kept separate from individual performance evaluation?
Inputs for this step
- Validated observations and support needs
Actions
- Reflect observations, validate them with the team, and agree an investigation or support.
- Is the observation kept separate from individual performance evaluation?
Output
Validated learning and support question
Validated learning and support question
Quality check
Is the observation kept separate from individual performance evaluation?
Pitfall
One walk is generalized Label the observation as a sample and plan repetition or data review.
Timing: Part of the agreed work block; research may be separate.
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Versioned result with question, evidence, open issues, next action, ownership, and review date.
Versioning / ownership
Record date, scope, sources, and changes. Preserve earlier observations.
Tool alternatives
- Whiteboard or paper
- Shared spreadsheet
- Versioned project space
gemba-walk-working-template.md
Prepare Gemba Walk with a clear question, roles, and sources.
Gemba Walk: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
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.
Preparation for this scope
Method setup
- Materials: Shared workspace, accessible sources, and a decision log.
- Roles: Host · observing leader · frontline staff
- Advance information: Clarify the question, timeframe, data access, roles, and known uncertainties in advance.
- Overall time needed: 30–60 minutes for one bounded walk; repetition may be needed to verify observations.
- Setup: Create a shared version. Label facts, assumptions, and decisions separately.
Prepare for the work steps
Purpose: Clarify purpose and process boundary
- Learning purpose, host, and area
Observe: Observe work directly
- Real work item and process steps
Ask: Ask respectfully
- Open questions for people doing the work
Follow-up: Reflect and agree next step
- Validated observations and support needs
Purpose, process observation, and agreed question
Purpose
Record why the walk is happening and which process is in scope.
...
Observation
Record observed steps, waits, and tools.
...
Perspective
Capture perspectives with consent and context.
...
Follow-up
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
Purpose: Clarify purpose and process boundary
Expected artifact: Agreed observation purpose and process boundary
Agreed observation purpose and process boundary
Entry:
...
- Do people know why the work is being observed?
Observe: Observe work directly
Expected artifact: Evidence-led process observations
Evidence-led process observations
Entry:
...
- Is the note observation rather than judgment?
Ask: Ask respectfully
Expected artifact: Attributed frontline perspectives
Attributed frontline perspectives
Entry:
...
- Are the people doing the work speaking for themselves?
Follow-up: Reflect and agree next step
Expected artifact: Validated learning and support question
Validated learning and support question
Entry:
...
- Is the observation kept separate from individual performance evaluation?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/gemba-walk/run-sheet
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
gemba-walk-beispiel.md
Concrete filled scenario, fictional example
Fictional worked example
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.
All names and values are invented for illustration. Unresolved explanations remain questions.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Clarify purpose and process boundaryWalk becomes personnel inspectionView in phase
- Observe work directlyProposed fix biases observationView in phase
- Ask respectfullyStaff cannot speak candidlyView in phase
- Reflect and agree next stepOne walk is generalizedView in phase
Trap
Clarify purpose and process boundary
Symptom
Walk becomes personnel inspection
What to do
Observe process conditions and ask with genuine curiosity.
Trap
Observe work directly
Symptom
Proposed fix biases observation
What to do
Describe purpose, process, and actual work first; separate hypotheses.
Trap
Ask respectfully
Symptom
Staff cannot speak candidly
What to do
Be transparent about purpose and respond respectfully to observations.
Trap
Reflect and agree next step
Symptom
One walk is generalized
What to do
Label the observation as a sample and plan repetition or data review.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
The question or boundary remains ambiguous: narrow it first.
Key data or participants are missing: label the gap and arrange access.
The group mixes observation and explanation: revisit the evidence.
An immediate safety or operational risk appears: stop and use the responsible procedures.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.