Gemba Walk

A gemba walk is a Lean management practice where leaders or process owners go to the place where work actually happens, observe the process directly, and ask questions to understand how value is created. Lean Enterprise Institute defines gemba as the actual place where value-creating work occurs. ¹

It is not a surprise inspection. It is a structured way to see the real workflow, learn from the people doing the work, and spot friction that reports and dashboards often hide. Toyota's related genchi genbutsu practice emphasizes going to see the actual place or process before solving the problem. ²

Processes usually look cleaner in documentation than they do in real life. The SOP may say one thing, the software may require another, the handoff may depend on a workaround, and the metric may only show the final delay.

A focused observation can reveal waiting, rework, duplicate entry, unclear ownership, missing materials, unnecessary motion, and quiet escalation paths. The observer's job is to understand the system before judging the person; if employees experience the walk as performance policing, they will hide workarounds instead of explaining them.

Choose a narrow process, go to where the work happens, observe the actual flow, ask respectful questions, capture what you learn, and follow up on improvement opportunities. A focused question—such as why invoice approvals take too long—is more useful than a broad walk through an entire department.

Ask open questions: What triggers this step? What information do you need? What slows you down? What do you do when the normal path fails? Which part is hardest to explain to a new person? Then assign ownership and tell the team what happened as a result.

The real place may be a physical floor, shared inbox, ticket queue, CRM, or video call. AHRQ's workflow-assessment toolkit similarly treats understanding current clinical and administrative workflows as a prerequisite for redesigning them well. ³

• Arriving with a solution already chosen instead of testing assumptions.
• Asking questions that sound accusatory rather than curious.
• Documenting only the ideal future state instead of the current workaround, delay, duplicate spreadsheet, or confusing handoff.
• Failing to connect observations to action, ownership, and feedback to the team.

A gemba walk keeps process documentation honest. Watching the work happen surfaces the handoffs, checks, and exceptions that static templates miss, so teams can update SOPs and training guides from evidence rather than memory.

When a workflow happens in a browser or software tool, Trails can capture it as someone performs it and turn that capture into a polished step-by-step guide or AI-narrated video. That gives teams a practical way to share the observed workflow with people who were not present during the walk.

Is a gemba walk only for manufacturing?

No. It comes from Lean manufacturing, but applies anywhere work has a real flow: a ticket queue, CRM, shared inbox, onboarding workflow, or internal system.

Who should do a gemba walk?

Managers, process owners, team leads, operations leaders, quality teams, and documentation owners can all use them. Curiosity and follow-through matter more than rank.

What should happen after a gemba walk?

Summarize and validate the observations with people doing the work, choose the next action, and communicate what will change. Update the relevant SOP, guide, checklist, or training material when there is a documentation gap.