Gemba Walks: Observe the Work, Then Choose a Useful Next Step

Gemba is a place, not an acronym

The Lean Enterprise Institute translates gemba as the actual place where value-creating work happens. That can be a production line, a dispatch desk or the team handling customer requests. Gemba is also written genba. An English-friendly pronunciation is “gem-buh”, with a hard g.

The walk is a way to understand current work before deciding what to change. Kaizen concerns improvement; the walk can help a team find and understand a problem to improve. A Six Sigma investigation can use the same direct observation alongside its measurements. These are related practices, not competing names for one compulsory sequence.

Observe the work with its operators. An unexplained queue may be waiting for a drawing, an authorized decision or a replenishment signal. Looking at the queue without asking can send the team after the wrong problem.

Plan the visit around one question

Seven-step guides are useful teaching aids, but there is no required seven-step duration for every Gemba walk. Choose a period long enough to see the part of the workflow you need, and arrange follow-up when important conditions are absent. A short visit cannot establish what happens across every shift.

For this fictional example, the question is why a ready maintenance-support request waits before approval. The boundary begins when the request is accepted and ends with a usable decision. The observer follows one request with the requester and reviewer; the purpose is learning, not ranking people.

1. Agree the purpose

   Tell the team which customer problem you are examining and what is outside the visit.

2. Follow actual work

   Watch one job and its information cross the relevant handoffs.

3. Ask about the difference

   Compare what was expected with what happened, without prescribing a cause.

4. Keep a checkable record

   Separate timestamps and quotations from your interpretation.

5. Agree the follow-up

   Name who will check the missing evidence and when the team will review it.

An observation sheet needs room for uncertainty

Use one record per observation. Include the job or case, step, time, expected condition, observed condition, the operator’s explanation, evidence still needed and follow-up owner. Avoid collecting personal details the investigation does not need.

In the fictional record below, the approval screen alone would miss a conversation about a missing drawing. The timestamps locate the delay. They do not prove why the drawing was absent or why the next review slot was late.

Ask a question someone can answer from the work

“Why is this process inefficient?” asks for a judgment. “What information do you need before you can start this review?” asks for something the person can show. Follow with “Where does that information come from?” or “What happens when it is missing?”

Give people room to disagree with the map. A necessary recovery step can look like waste when its purpose is invisible. Ask permission before recording, taking photographs or quoting a person, and follow the site’s access and safety rules. The walk does not authorize entering a restricted area or interrupting a hazardous task.

Turn one finding into a follow-up, not ten promises

Suppose the visit suggests that acceptance does not check drawing revision. The next step could be to inspect several request packets and compare what was available when each was accepted. That is an investigation, not proof that a new form will solve the delay.

If the evidence supports a trial, agree the smallest safe change and its fallback. A PDCA cycle helps connect the prediction and result. A value-stream map keeps the local change connected to the complete journey.

Return to the work after the visit

Tell the team what you learned, what remains uncertain and what happened to its questions. Quietly filing the notes teaches people that the next walk will also lead nowhere.

Check the proposed change under ordinary conditions, including absences, different request types and unresolved cases. The continuous-improvement guide covers that wider loop. The downloadable record here provides prompts; it is not an employee assessment or an approved site audit.