Gemba Walk: A Practical How-To Guide
The word gemba comes from the Japanese gamba, meaning "the actual place." In Lean thinking it refers specifically to the place where value is created — the factory floor, the service counter, the operating room, the project site. A gemba walk is the practice of going there, regularly and with intention, to see work as it actually happens rather than as it is reported to happen. It sounds unremarkable until you realise how few organisations do it consistently, and how differently managers who do it regularly think about their operations.
The gemba walk is not a new idea. Taiichi Ohno at Toyota insisted that managers spend time on the floor watching actual work. He believed — correctly, as it turned out — that the most important information about a production system is never visible in a report. Reports are summaries of what people chose to measure and chose to tell you. The gemba shows you what is actually happening, including the things no one thought to measure and the problems people have learned to work around rather than fix.
What a gemba walk is not
Before describing how to do a gemba walk, it is worth being clear about what it is not, because the most common failures come from misunderstanding its purpose.
It is not an inspection. An inspection looks for deviations from a standard in order to assign accountability. A gemba walk looks for opportunities to understand and improve. The difference matters enormously to the people being observed.
It is not a performance review. You are not there to evaluate individuals. You are there to understand the system they work within.
It is not a problem-solving session. When you see a problem during a gemba walk, you note it. You do not fix it on the spot, because the fix you invent in thirty seconds is almost certainly wrong, and the act of fixing it immediately tells the team that their job is to manage your reactions rather than to surface problems.
It is not a tour for visitors. If the walk exists to impress an external audience, it will generate impressive-looking work rather than honest observation.
How to prepare
A productive gemba walk requires more preparation than most managers expect. You do not simply show up and wander. Three things matter before you go.
Choose a theme. A gemba walk without a focus produces scattered observations that are hard to act on. Before each walk, decide what you are trying to understand. Flow? Handoffs? Safety? Customer wait time? The theme shapes what you pay attention to without blinding you to everything else.
Inform the team. This is not a surprise audit. Tell the team you are coming, when you will arrive, roughly how long you will stay, and what you are interested in observing. A team that knows why you are coming will be more willing to show you real problems rather than hiding them. Surprise inspections produce tidy workstations and silent workers — neither of which helps you.
Bring a notepad, not a checklist. A checklist tells you what you expected to find. A notepad lets you record what you actually see. Write down observations, questions, things that surprise you, and things you do not understand. You are not scoring the operation; you are trying to understand it.
How to conduct the walk
Arrive on time, alone or with one other observer at most. More people create a delegation, and delegations change behaviour. Position yourself where you can see a process from beginning to end without obstructing flow. Watch quietly for several minutes before asking anything. You are looking for how work actually flows: where does it pause? Where does it speed up? Where do people improvise?
When you ask questions, ask them with genuine curiosity rather than judgment. The best gemba questions follow a consistent pattern: "Can you show me how this step works?" "What happens when...?" "Why is this done this way?" "What makes this difficult?" These are open questions that invite the worker to teach you. Workers know their jobs far better than you do, and the gemba walk is your opportunity to learn from them, not to demonstrate that you know better.
Respect the worker's expertise explicitly. When someone explains something to you, thank them. When you observe something you do not understand, say so. The posture of a learner — genuinely curious, willing to be surprised, quick to acknowledge what you do not know — is what makes a gemba walk produce real information rather than performed competence.
If you observe a problem — a safety hazard, a quality defect, a process that is clearly broken — note it. Do not fix it on the spot unless it poses an immediate physical danger. The practice of fixing problems during a gemba walk trains the team to hide problems before you arrive, because they have learned that your presence triggers intervention rather than support.
Debrief and follow-up
The walk itself is only half the value. After the walk, within twenty-four hours, review your notes and extract two categories: questions you still have (problems you observed but do not yet understand well enough to act on) and commitments you want to make (process changes, investigations, resources you will provide). Share both with the team you observed. The questions signal that you are still learning. The commitments signal that what you saw mattered.
A gemba walk that produces no visible follow-up becomes, over time, a ritual that people wait out rather than a conversation they engage with. The team notices whether anything changes as a result of your presence. If nothing changes, they will eventually stop showing you real problems.
How regular gemba walks change leadership
Managers who do gemba walks regularly — not as a programme initiative but as a standing habit, weekly or more often — report a consistent shift in how they understand their operations. Problems they once learned about six weeks after they started surfacing become visible within days. Improvement ideas that would never have made it into a report come forward naturally. And their teams, sensing that direct observation is valued, begin to pay more attention to what they actually see rather than to what the metrics say they should be seeing.
The deeper change is subtler. A manager who spends regular time in the gemba develops a felt sense of how the operation works — not a summary, not a dashboard, but a direct, embodied understanding of pace, rhythm, pressure, and variation. That understanding makes every other management decision better, because it is grounded in reality rather than in the version of reality that reports produce.
If your leadership team is ready to build the habits and disciplines that connect strategy to the work that actually creates value, XNM's strategic advisory can help you design a gemba programme that fits your organisation's context and culture.