What does gemba mean?

Gemba (現場) is a Japanese term meaning "the actual place" or "the real place", in manufacturing, the spot where the work is physically done, usually the plant floor. It entered lean practice through the Toyota Production System.

What is the purpose of a gemba walk?

To close the gap between what leaders think is happening and what is actually happening, by observing the real process and talking with the people doing it. It is a way to see reality directly instead of through filtered reports.

How is a gemba walk different from an audit?

An audit checks whether rules are being followed and often looks for violations. A gemba walk seeks to understand the process and treats the operator as the expert. Auditing looks for who is wrong; a gemba walk looks for what could be better.

How often should you do gemba walks?

Many plants do them daily at the supervisor level and weekly at the management level. Consistency matters more than frequency, walking the same route on a regular cadence lets patterns emerge over time.

What questions should you ask on a gemba walk?

Open, process-focused questions: "Walk me through this," "What gets in your way?" "How do you know when something is going wrong?" and "What would you fix first?" Avoid yes/no questions and anything that sounds like blame.

What is a gotcha walk?

A gotcha walk is a gemba walk turned into a hunt for mistakes or people to blame. It teaches operators to hide problems and tidy up before visits, which destroys the honesty the practice depends on.

Gemba Walks: How Leaders See What Reports Hide

The floor tells you things a dashboard never will, if you know how to look and what to ask.

A gemba walk is a structured visit to where the work actually happens, the plant floor, to observe the process, talk with the people doing it, and understand real conditions with your own eyes. The word gemba (現場) is Japanese for "the actual place," borrowed into lean practice from Japanese crime reporting and policing, where it meant the scene itself. The idea is simple: reports are filtered, floors are not.

The practice was popularized through the Toyota Production System and Taiichi Ohno's insistence that managers "go and see" (genchi genbutsu) rather than manage from a conference room. It sounds obvious. It is also the single most-skipped habit in plants that are drowning in dashboards.

What Is the Point of a Gemba Walk?

The point is to close the gap between what leadership believes is happening and what is actually happening. A daily report can tell you a line ran at 62% OEE. Only the floor tells you that it ran at 62% because a changeover cart is parked in the wrong aisle and the operator walks 40 feet for every roll change. You cannot see that in a number.

A gemba walk is not an inspection, and it is not a tour. An inspection looks for violations; a tour looks at nothing in particular. A gemba walk looks at one process, with a question in mind, and treats the operator as the expert.

A gemba walk follows a planned route with a specific observation focus at each stop.

How Do You Run a Gemba Walk?

A good walk is deliberate. It has a purpose, a route, and a follow-up. Here is a structure that survives contact with a busy plant:

Pick one theme. Safety, flow, quality, or a specific problem. A walk about "everything" observes nothing.
Plan the route. Follow the product's path, not the org chart. Walk the value stream in the direction the material moves.
Tell people why you are there. "I am here to understand the changeover, not to check up on you." Say it out loud.
Observe before you speak. Stand and watch one full cycle. Note what waits, what backtracks, what gets redone.
Ask open questions. "Walk me through this." "What gets in your way?" "What would you fix first?" Then be quiet.
Write down what you saw, not what you concluded. Facts first. Countermeasures come later, with the team.
Close the loop. Follow up on at least one thing the operator raised. Nothing kills future candor faster than a walk that changes nothing.

The Questions That Actually Work

The best gemba questions are open and process-focused: What does normal look like here? How do you know when something is going wrong? What do you do when it does? What slows you down that nobody upstairs sees? Notice what these have in common, none of them can be answered with a yes, and none of them put the operator on trial.

The Gotcha Walk and Other Ways to Ruin It

The fastest way to destroy a gemba program is to turn it into a hunt. If leaders walk the floor looking for people to catch, operators learn to hide problems, tidy up before the visit, and give the answers they think the boss wants. That is the opposite of the goal. Other anti-patterns: walking the same clean showcase line every time, walking without a theme, and, most common, walking, nodding, and never following up.

The conversation moves from observation to the operator's own diagnosis to a shared next step.

By the Numbers

Manufacturing runs on frontline labor: the U.S. Bureau of Labor Statistics counts roughly 12.8 million manufacturing workers as of 2026 (BLS Industries at a Glance, NAICS 31-33), and the vast majority of what happens to quality, safety, and throughput is decided at the machine, by those workers, in real time. Leadership systems that never reach the machine are managing a shadow of the plant. The gemba walk is the cheapest correction available: it costs an hour and a notebook.

Where Harmony fits: a walk shows you the floor for an hour, but the floor runs 24 hours. Harmony connects machines, systems, and paperwork into one real-time operational layer, so the conditions you go and see on a walk are also captured continuously between walks, see the platform. Pair the human habit of going to see with a system that never looks away.