Home › The Garage › The Gemba walk
Lean

The Gemba Walk

Gemba means 'the real place' — where the work actually happens. A Gemba walk is the discipline of going there to see the process with your own eyes, because the truth is on the floor, not in the report.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. What Gemba means
  2. Why go and see
  3. What to look for
  4. The rules of a good walk
  5. Common questions
The process on paperclean, linear, as designed The process on the floorworkarounds, waiting, the real thing ≠ The Gemba walk is how you find the gap — and the gap is where the improvement is.
The documented process and the real one are never identical. The Gemba walk closes the gap.

What Gemba means

Gemba (現場) is Japanese for "the real place" — the actual location where work is done and value is created: the factory floor, the service desk, the screen where the operator works. A Gemba walk is the Lean practice of leaders and improvers physically going to that place to observe the real process, talk to the people doing it, and see the work as it actually is — not as a dashboard, a policy, or a slide represents it.

Why go and see

The process you design and the process that actually runs are never the same. People invent workarounds, steps get skipped, queues form in places no diagram shows. Reports and dashboards are abstractions — useful, but one or two removes from reality, and they systematically hide the friction that frustrates the people doing the work. Genchi genbutsu — "go and see for yourself" — is the Toyota principle behind it: you cannot understand a problem you have only read about.

The map you build from a desk is a hypothesis
Any process map drawn from memory or policy is a guess until someone has watched the work. A Gemba walk is how you turn the hypothesis into the current reality — which is the first non-negotiable principle of good process mapping: map what actually happens, not what's supposed to.

What to look for

The rules of a good walk

  1. Observe, don't inspect. A Gemba walk is not an audit. The moment it feels like a performance review, people perform, and you stop seeing the truth.
  2. Go with a purpose. Walk to understand a specific process or problem, not to wander.
  3. Ask, don't tell. Your job is to learn from the people who do the work, not to fix it on the spot.
  4. Watch the process, respect the people. You're there to find faults in the system, never in the person.
  5. Don't solve it in the room. Capture what you see; design the fix afterwards, with the team, from evidence.

What you learn on the walk is the raw input for everything else — an honest process map, a root-cause analysis, a journey map. The walk is where the truth enters the system.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

Keep learning in the Garage

Short, practical lessons on Lean, process mapping and AI-ready operations — the same thinking that powers LeanBean, in two minutes or less. Follow along and build the habit.

Common questions

What is a Gemba walk?

A Lean practice of going to 'the real place' where work is done to observe the process, talk to the people doing it, and see the work as it actually is — not as a dashboard, policy or slide represents it. Gemba is Japanese for 'the real place'.

Why do a Gemba walk?

Because the process you design and the one that actually runs are never the same — people invent workarounds, steps get skipped, and queues form where no diagram shows. Reports hide that friction. 'Go and see for yourself' (genchi genbutsu) is the only way to understand the real problem.

What do you look for on a Gemba walk?

Waiting and queues, workarounds, handoffs between people or systems, rework, and above all what the frontline people tell you. The eight wastes (TIMWOODS) make a good observation checklist.

What are the rules of a good Gemba walk?

Observe, don't inspect — it's not an audit. Go with a specific purpose, ask rather than tell, watch the process while respecting the people, and don't try to solve the problem in the room. Capture what you see and design the fix afterwards with the team.

Related guides: The 8 wastes (TIMWOODS) · Root cause analysis · How to map a business process