A gemba walk takes leaders to where work happens so they can understand the current condition with the people doing it. The purpose is not to tour the workplace collecting faults or to prescribe solutions from a brief impression. Useful questions reveal the expected result, what is actually happening and what support the work needs.
The Lean Enterprise Institute's discussion of leading with respect connects the gemba with understanding work and standards. Our lean leadership principles guide introduces the broader leadership stance. The questions below are original practical prompts, not a validated audit checklist or a quotation from either source.
Before the walk: choose a learning purpose
Select one work question, such as where an incoming team encounters uncertainty or what makes a priority difficult to execute. Explain the purpose to the relevant people and agree a suitable time and route. Follow site access, safety, privacy and operational requirements. Do not interrupt controlled work, take unauthorized photographs or ask someone to demonstrate an unsafe condition.
State what the visit is not. It is not a surprise performance appraisal or permission to alter a process during the discussion. If an immediate concern requires action, follow the approved response. A respectful learning purpose never replaces required controls or qualified supervision.
Questions about purpose and the expected result
Begin with what the work is meant to accomplish. What does the customer or receiving team need from this step? What tells you the work is ready to pass on? Which approved standard or agreement defines that? These questions help a leader understand the outcome before interpreting a visible activity as value or waste.
Ask the person to explain the work in their own terms. A leader may recognize the equipment while misunderstanding the decision the operator must make. Listen for the difference between the planned process and the conditions of today's work. Avoid supplying your preferred answer inside the question.
Questions about the actual condition
What is happening now compared with what you expected? Where does the work wait or require clarification? What information is hard to obtain? Which recurring condition makes the next step difficult? Ask for an appropriate example or approved record when useful, rather than turning one anecdote into a general diagnosis.
An observation record can separate three things: what was directly seen, what the person reported and the leader's interpretation. For example, 'An approved input had not arrived at the agreed point' is different from 'The supplying department is unresponsive.' The second statement needs evidence that a short visit may not provide.
What if two teams describe the same handoff differently?
Treat the different accounts as questions to investigate, not immediate proof that one team is wrong. Ask what each side expected to send or receive, which approved record supports the account and where the decision remained unclear. The handoff guide keeps ownership and receiving-team acceptance visible. Follow approved access, privacy and safety arrangements while gathering an appropriate example.
A fictional observation might show that the sending team counted an item as complete when it was sent, while the receiving team needed a required confirmation before acting. That difference calls for examination of the authorized agreement—not a spontaneous change to a controlled procedure. The cross-functional conflict guide helps separate facts from priority or authority disagreements. Return with the responsible owner's answer so the learning visit produces useful follow-through.
Questions about judgment, uncertainty and support
What can you decide when this situation changes? What requires an authorized decision-maker? How do you raise a concern, and what response helps you continue appropriately? Which part of the expectation remains unclear? These questions may reveal a leadership decision or unavailable support rather than a lack of effort.
Do not ask people to resolve issues outside their authority on the spot. If the decision belongs elsewhere, identify the responsible role and the approved next step. A walk is not useful if it records a problem, tells the employee to own it and leaves the necessary leadership action unnamed.
Close the conversation with understanding, not an instant solution
Summarize what you believe you learned and invite correction. Ask what question still needs investigation and who should be involved. Where appropriate, agree one next observation or review of existing evidence. Label a possible explanation as a hypothesis until it has been checked.
A fictional closing might be: 'The team knows the required output, but the next decision waits for an owner who is not available at that point. I will clarify the authorized route with the relevant leaders and return with the answer. Have I understood the difficulty correctly?' The leader owns the follow-up that requires leadership authority.
Return and review what happened
Keep a modest record of the work question, observations, unresolved issue, owner and checkpoint. Return to explain what was learned and what remains open. If a permitted improvement is tested, review it against the intended outcome and approved constraints rather than assuming a visible change is automatically better.
The five lean principles provide wider context for understanding value and flow. If walks repeatedly surface unclear priorities or unavailable authority across teams, discuss the leadership system instead of creating a longer inspection list.
About this resource: Prepared with AI-assisted drafting. Questions and examples are general learning prompts, not an approved safety, quality or operational audit. The example is fictional. Cover illustration: AI-generated.