Going to the Gemba: Why Kaizen Starts Where the Work Happens

What gemba and genchi genbutsu mean, why lean leaders go and see for themselves, and how to make a gemba walk respectful and useful instead of an inspection tour.

Gidoka · Last reviewed October 24, 2026 · 6 min read

Reports, dashboards and meeting summaries are useful, but they are always a step removed from the work itself. Somewhere between what actually happens and what reaches your inbox, details get smoothed over, workarounds disappear and problems turn into averages.

Kaizen deals with that gap through a simple habit: go to where the work is done and see it for yourself. The Japanese word for that place is gemba. This guide explains what the term means, why going there matters so much in lean thinking, and how to make a visit worthwhile for you and for the people you are visiting.

What gemba means

The Lean Enterprise Institute (LEI) defines gemba as the Japanese term for "actual place," often used for the shop floor or any place where value-creating work actually occurs. You will also see it spelled genba. Lean practitioners use it to mean the place where value is created.

The gemba depends on the work. LEI's examples include the factory floor in manufacturing, the operating room in a hospital, the kitchen and dining room in hospitality, the job site in construction, and the code itself in software. For a small office, it might be the front desk, the order queue or the shared inbox where customer requests land.

Genchi genbutsu: go and see

A closely related term is genchi genbutsu. LEI describes it as the Toyota practice of thoroughly understanding a condition by confirming information or data through personal observation at the source. In Japanese, it essentially means "go and see" but translates directly as "actual place and actual thing." LEI notes that a decision maker investigating a problem goes to observe the process and talks with the people doing it, "rather than relying solely on computer data or information from others," and that the practice applies to executives as well as managers.

Toyota still treats this as basic. In the message that opens the Toyota Code of Conduct, Chairman Akio Toyoda writes that when failures or mistakes happen, "everyone must always stop, investigate the true cause by genchi-gembutsu, make kaizen and work towards preventing recurrence."

Why going and seeing matters

LEI's gemba entry gives a concrete reason: standardized work for a machine operator "cannot be written at a desk in the engineering office," but must be defined and revised at the gemba. The same is true of most work. The people doing a task know the shortcuts, the waits and the small frustrations that never show up in a process diagram.

LEI also names two main purposes for leaders spending time at the gemba: to raise awareness of the possibilities for dramatic end-to-end improvement, and to assess whether the management system can maintain stability, which is the basis for successful improvement. Because value flows across departments to the customer, LEI suggests that a productive walk often follows a single product family or customer-facing process from start to finish, across functions and even organizations.

Go see, ask why, show respect

John Shook, writing for LEI, recalls hearing Toyota's Fujio Cho put the practice in six words: "Go see, ask why, show respect." Shook describes this as the way to turn the philosophy of scientific empiricism into actual behavior.

Go see. Shook looks at every gemba in terms of purpose, process and people. What is this area trying to accomplish? Are processes designed to achieve that purpose? Are people supported by those processes? He starts with a few simple questions about purpose, then spends most of his time observing the process, and circles back to purpose at the end.

Ask why, but not first. Shook's advice is to ask what first, then why, then what if, and finally why not. You have to grasp the situation before you diagnose it. He quotes lean coach David Verble: "Ask no 'why?' before its time."

Show respect. Shook writes that lean thinking mandates respect for all the people involved, especially those who do the value-creating work. That includes looking for signs of overburden on workers, which lean thinkers call muri. His first rule of gemba walking is blunt: "Do no harm!"

Three kinds of walks

Not every walk is the same, and confusing them causes trouble. Jim Womack, who says he and Dan Jones first used the term gemba walk in the early 1990s, describes two types with different purposes in an LEI article:

The value-stream walk, which follows a product or service from beginning to end to see the possibilities for dramatic improvement.
The management-system walk, which checks whether daily management is keeping work stable, for example by following how team leaders and managers review status boards and respond to problems.

Womack also notes a third, looser use: senior leaders leaving the conference room to "get to the bottom" of a festering problem. He notes that this use of the term is often equated with "management by walking around," and he questions why it should be necessary if a robust daily management system is already surfacing problems quickly. Knowing which walk you are taking helps you decide what to look for and who should come along.

A simple first gemba walk

Here is a hypothetical example for a small team. Imagine you manage a six-person customer support group and response times have crept up. Instead of pulling another report, you try this:

Pick one purpose. For example: "Understand what happens to a customer email from arrival to first reply."
Tell the team in advance why you are coming and that you are there to learn, not to evaluate anyone.
Follow the work. Sit with one person and watch a few requests move through the queue. Note each step, each wait and each workaround.
Ask "what" questions first: What are you doing now? What happens next? What do you need that you don't have?
Save "why" questions for later, once you can describe what actually happens.
Write down what you saw, not what you assumed. Share it with the team and ask what they would try first.
Agree on one small change to test, and come back to see how it is going.

Common mistakes

Arriving with a solution. Shook warns that using a tool for the tool's sake is one of the most common reasons lean efforts fail; lean thinking is about not jumping to conclusions.
Treating the walk as an inspection. If people feel they are being graded, you will see a performance, not the real work.
Fixing problems on the spot. Shook cautions that CEOs who try to directly eliminate waste at the gemba often generate more waste than they prevent. Usually it is better to help the team see the problem and solve it.
Going once. A single visit gives you a snapshot. Regular visits, tied to a clear purpose, show you patterns.

Key takeaways

Gemba means "actual place": wherever value-creating work happens, in any industry.
Genchi genbutsu, "go and see," means confirming facts by observing at the source rather than relying only on reports.
Toyota's Fujio Cho summarized the practice as "Go see, ask why, show respect."
Ask what before why; understand the situation before diagnosing it.
Be clear whether you are walking a value stream or checking the management system, and do no harm.

Sources

Spotted something out of date? Let us know.