A manager walks through a workplace, spots a delay and immediately tells someone to work faster. That may look like close attention to operations, but it has skipped the most useful question: what in the process is creating the delay?
The Lean Enterprise Institute’s guide to visiting the gemba emphasises observing actual work and respecting the people doing it. The purpose is to understand the process where value is created, not to collect impressions from a hurried tour.
Choose one process to understand
For an illustrative office visit, follow a request from arrival to completion. Note where information is checked, where the request waits and where someone needs clarification. Do not interpret every pause as wasted effort; the pause may be a necessary control or a response to missing information.
Tell the team what you are trying to learn. Ask when observation would interfere least, and respect privacy, safety and customer obligations. Watching real work is not permission to record confidential screens or conversations.
Write observations in neutral language
“The request waited for a missing reference number” describes an event. “The team is careless” assigns a broad judgement that the observation does not establish. Keep the event, your question and any proposed explanation in separate notes.
Ask before proposing a fix
Useful questions include “What makes this step difficult?” and “When does this work smoothly?” Give the person doing the work room to correct your understanding. A workaround that looks untidy may be compensating for a limitation elsewhere.
Close the visit with a commitment
Agree which question needs follow-up, who will investigate it and when the team will hear back. Avoid promising a solution before the problem is understood.
A worthwhile gemba walk leaves more than a manager’s list of impressions. It produces a clearer account of how work flows, where the evidence is incomplete and what will be examined next with the people closest to it.

