Gemba Walk: Go See Where the Work Happens

The mental model

"Gemba" is Japanese for "the actual place." A Gemba Walk is about leaving the conference room and going to the place where work happens and value is created, like a factory floor or a sales desk. It's a tool for leaders to ground their understanding in reality, not in summaries, reports, or dashboards. The philosophy is simple: to truly understand a process, you must see it in action.

How it works

A leader decides on a process to observe, like customer onboarding or bug triage. They go to the physical or digital "gemba"—the sales floor, the assembly line, or even a shared screen in a video call. The key is to observe without interrupting, ask open-ended questions like "Can you show me how you do that?", and listen. It is not about providing solutions on the spot, but about gathering information and showing respect for the people doing the work. The insights are then used later for strategic process improvement.

When to use it

Use a Gemba Walk when you suspect a disconnect between reports and reality. It's valuable when kicking off a process improvement initiative, when metrics look strange, or when you simply want to understand the daily challenges your team faces. For example, a product manager might do a Gemba Walk with the support team to understand the most common user complaints firsthand, rather than just reading ticket summaries.

When not to use it

Do not use a Gemba Walk as a surprise inspection or a performance review. It's not the time to point out individual mistakes, assign blame, or implement immediate changes without team consultation. If the team feels judged, they will stop being transparent, and the walk becomes useless. It is a tool for learning, not for policing.

One canonical example

A plant manager sees reports of increased defects in a specific assembly step. Instead of emailing the line supervisor, she goes to the factory floor (the gemba). She observes the process for an hour, noticing that a parts bin is placed awkwardly, forcing workers to twist and reach, sometimes grabbing the wrong component. This direct observation reveals a problem that a data report never could.