A Gemba walk is a structured visit to the place where value is created. The term points to “the actual place,” and the practice is immediately useful in an office, call center, clinic, warehouse, field service route, or digital workflow.
What a Gemba walk is—and is not
A Gemba walk is not a surprise inspection, a leadership tour, or a request for employees to perform a polished version of the process. It is a learning conversation. A leader goes to the work, observes the conditions, asks respectful questions, and leaves with a clearer understanding of which system constraint deserves attention.
The distinction matters. When people believe a visit is an audit, they hide problems. When they believe it is a listening exercise with follow-through, they can show leaders the workaround that has become invisible to everyone outside the process.
A good Gemba question makes the work easier to see. It does not make the person doing the work defend themselves.
Prepare the walk in 20 minutes
Preparation keeps the conversation focused without turning it into a script. Before arriving, the leader and process owner should agree on:
- The value stream. Follow one customer request, order, case, or decision from trigger to outcome.
- The customer promise. Name what “good” means in the eyes of the customer or downstream team.
- The question. For example: “Why do urgent orders wait for manual approval after the inventory check?”
- The boundaries. Respect safety, privacy, union rules, patient confidentiality, and the team’s normal work schedule.
- The next decision. Decide who can remove the likely constraint if the observation confirms it.
Bring a simple sheet for observations, not a laptop full of dashboards. Existing metrics are useful context; they should not substitute for seeing the sequence, interruptions, queues, and decisions in their natural environment.
What to look for on site
Stay curious about the gap between the standard process and the real process. Look for:
Waiting
Where does work pause for information, permission, a system, or a person?
Rework
What is corrected, re-keyed, reconciled, or explained more than once?
Handoffs
Where does ownership become ambiguous between teams, vendors, or platforms?
Workarounds
What unofficial tool or memory-based step keeps the customer promise alive?
Questions that open the process
Use open questions, then wait. The most useful information often arrives after the first answer.
- What are you trying to accomplish at this step?
- How do you know the work is ready for you?
- What usually interrupts this flow?
- When the process goes well, what makes that possible?
- If you could remove one obstacle this month, which one would you choose?
- What does the customer experience when this step goes wrong?
Avoid “Why did you do that?” when you can ask “What condition led you to choose that path?” The first assigns blame. The second exposes the design of the system.
A field example: a hospital access team
Consider an outpatient network in the Northeast that is missing its target for new-patient appointment scheduling. Leaders might begin with a technology request for a new call-center platform. A Gemba walk follows the request from the patient’s initial call through insurance verification and appointment confirmation.
The team discovers that schedulers are not primarily waiting on the phone system. They are toggling between a payer portal, a scanned referral, and an internal queue to answer one eligibility question. The immediate experiment is a standardized intake view and an escalation rule for ambiguous cases. The technology roadmap may still change, but it is now connected to a known work condition. Any patient-specific information is handled under the organization’s privacy and security controls.
Close the loop after the walk
The walk is only valuable if the organization acts on what it learned. Within 24 hours, share three things with the people who hosted the visit:
- What we saw, stated without judgment.
- What we believe is the next constraint to test.
- Who will make the decision, by when, and how the team will know whether it helped.
Choose one small action that demonstrates respect for the team’s time. It could be removing an approval, fixing a broken report, clarifying an ownership rule, or scheduling a deeper process-design session. If leadership cannot act yet, say why and give the observation a visible owner.
A repeatable monthly practice
Start with a 45-minute walk once a month in one value stream. Rotate the location and invite the process owner to choose the next question. Over time, connect observations to the organization’s improvement backlog, service-level measures, and investment decisions. Digital products deserve a Gemba practice too: follow a real user journey through analytics, logs, support tickets, and the teams who respond to them.
The habit is more important than the ceremony. Leaders who regularly see the work make better tradeoffs because they can distinguish a local symptom from a system constraint.
Try it this week: Ask one team to show you the last customer request that needed an exception. Follow it from start to finish, and listen for the rule or handoff that made the exception necessary.
