Gemba: observe work, ask, follow through

Gemba: observe work, ask, follow through

Visit the work to understand how the process actually functions and what makes it difficult for the people doing it. Agree the purpose, observe a real sequence and ask about the difference between expected and actual conditions. Avoid turning every answer into an immediate instruction. Clarify what support is needed, make a specific commitment and return to check what happened. The quality of the visit is shown by learning and follow-through, not distance walked or boxes checked. Respect privacy and safe observation boundaries. A worker who exposes a problem should receive help, not punishment for making it visible.

Follow the method

1. Agree purpose
2. Observe and ask
3. Agree support
4. Return and verify

Separate what was seen from what was assumed

Fictional packing area: leader Ben sees operator Asha using a handwritten note beside the approved order screen. Earlier visits criticized unofficial paper, so colleagues are reluctant to describe workarounds. Ben wants to understand the handoff before deciding whether the note is a problem.

Follow the method

1. Screen then note
2. Screen omits cut-off in this view
3. Note currency unknown
4. Support agreed

The handwritten note has a purpose

Distinguish an observed work condition from an interpretation, ask a respectful question that improves understanding and close a support commitment at the work.

Fictional packing area: leader Ben sees operator Asha using a handwritten note beside the approved order screen. Earlier visits criticized unofficial paper, so colleagues are reluctant to describe workarounds. Ben wants to understand the handoff before deciding whether the note is a problem.

Role: Leader visiting with the colleague who performs the work.

Normal condition

The approved process supplies the information needed to identify the order and complete the handoff correctly.

The gap

The note appears to supply information missing at the moment of work, but its purpose and accuracy are not yet known.

• Respect local access, privacy and operating rules; use only fictional order records in this exercise.
• Observation is not permission to bypass the current method or remove a control before understanding its function.

1. Agree a learning purpose

   Ben explains that he is learning how the next order is made ready and asks Asha to show the normal sequence without speeding up for the visit.

   Why: A clear purpose reduces the pressure to perform for inspection and reveals the work as it happens.

   Evidence: The visit question concerns information at the handoff, not a person’s compliance score.

2. Record sequence before judgment

   He records screen, note and packing in order, separating what he sees from his inference about resistance to change.

   Why: An interpretation can be tested only after the underlying observations are clear.

   Evidence: The observation sheet marks dislikes the system as unsupported.

3. Ask what the workaround accomplishes

   Ben asks what decision the cut-off supports and what would happen without it. Asha explains that the screen lacks the needed timing at this point; they check the reference with the process owner.

   Why: The note may reveal a design gap while also creating a currency risk. Understanding both is better than instant removal or blanket approval.

   Evidence: Needed information, its source and the unanswered currency question are recorded.

4. Agree support and return

   The owner agrees to verify an approved information route and a bounded trial. Ben names who will provide support and returns to observe whether the information is available and correct.

   Why: Listening without follow-through teaches the team that surfacing problems has no effect.

   Evidence: The commitment contains owner, review point and observable handoff evidence; no successful trial is invented.

The note is wrong today

The reference check finds that the handwritten cut-off differs from the current approved value.

Use the local response for affected work and establish the approved reference immediately. Continue investigating why the work depended on the note.

Respectful learning does not ignore a real error; correcting the current risk does not erase the underlying information gap.

Record affected scope, current correction and the separate process-design follow-up.

Run a practice session

Materials

• Annotated fictional packing scene
• Observation versus inference cards
• Blank support record

1. Notice without judging · 4 minutes

   What can you actually see?

2. Role-play inquiry · 7 minutes

   What purpose does the note serve?

3. Practice office transfer · 8 minutes

   What remains unknown about the spreadsheet?

4. Plan return visit · 5 minutes

   What evidence would make support complete?

Debrief

• Replace why do you ignore the system with a question about the work decision.
• Ask what the leader owes the colleague after the visit.

Write an observation and a competing interpretation in different columns before drafting the conversation.

Transfer into the work

Owner: Process owner and visiting leader with the colleague doing the work

Record: Observation/support commitment linked to the actual handoff

Review: At the agreed return observation, then through daily follow-up if unresolved

Evidence: Accurate approved information available at the work and colleague feedback

Address the design/support barrier and retain current risk controls; do not blame the person who exposed the workaround.