Gemba Walking Shows You What Really Happens in the Process

Check the process where decisions, errors, and waste actually happen. Learn what gemba walking is, how to run it without making people feel inspected, which questions to ask your team, and how to connect shop floor observation with production data. If you are responsible for results, quality, or efficiency, a gemba walk helps you get to the source of a problem faster.

A report shows the number. A gemba walk helps you understand where that number came from.

A gemba walk means going to the place where the work is actually done. In manufacturing, that may be a production line, an operator workstation, a warehouse, quality control, maintenance, or packing. In services, it may be customer service, a lab, logistics, or an office where an order moves through the process.

“Gemba” means the real place. In Lean, decisions should be based on facts from the process, not only on reports, emails, and statements.

A good gemba walk follows three rules:

The last rule shapes the quality of the conversation. If the team feels inspected, they will show you a version of the process prepared for the visit. If they feel that you want to remove obstacles, they will say more about what really blocks the work.

In Lean, it makes sense to look at the process through specific types of waste: waiting, rework, unnecessary motion, excess inventory, errors, overload, and unclear decisions.

A report usually shows the effect:

On site, you can check the cause. An operator may be waiting for a component. A team lead may be looking for information. A machine may be stopped, but the downtime code may be too general. Quality control may reject a batch because the error started two steps earlier.

If an operator waits 6 minutes for material, and this happens 80 times per week, you lose 480 minutes. That is 8 hours of work per week. Over a month, it adds up to more than 32 hours that may disappear in a report under a general label such as “work organization” or “missing material.”

Gemba walking helps name the waste clearly enough to fix it.

A gemba walk makes the most sense when you want to check one specific thing.

Do it when:

Do not go only to look at production. Go to check why setup takes 42 minutes instead of 25, why micro-stops are entered in bulk, or where rework starts after the first quality check. The narrower the question, the better the findings.

A gemba walk should not look like a manager walking through the area with a notebook and a list of mistakes. That can shut people down. Instead of facts, you will get careful answers. That is why it helps to plan the walk using the steps below.

Example topics:

One walk means one problem. Save the rest for later.

Choose up to three numbers:

The data should point your observation in the right direction. It should not replace talking to people.

A short sentence is enough: you want to see what makes the work harder in this process so that some waste can be removed. That message can change the atmosphere because the team knows you are not looking for someone to blame. You are looking for facts.

For a few minutes, watch the process without interrupting. Write down what you see:

Look for a repeated pattern and do not stop at the first observation.

Good questions during a gemba walk:

Avoid blame and questions such as “Why are you doing this wrong?” It is better to ask what makes it hard to follow the standard.

A kaizen gemba walk connects observation with a quick test of a small fix, such as one specific obstacle that can be checked with data.

At one workstation, the operator walks 12 meters to get labels during every cycle. The process has 60 cycles per shift.

12 m × 60 cycles = 720 m per shift.

With two shifts and 20 working days, that equals 28.8 km per month spent walking just for labels.

Changing where the labels are stored can reduce motion, lower fatigue, and limit mistakes. It is a small decision, but it is based on observation and a simple number.

After a gemba walk, agree right away on:

With that plan, the walk can become the start of a better process.

Gemba walk in Lean management works best when you connect two things: observation on site and process data. Observation tells you what is happening, and data shows the scale of the problem.

Example: During a gemba walk, you see that operators enter downtime reasons too generally. In the system, many stops go into one category, such as “other.” On the shop floor, it turns out that this one word covers three different situations: missing component, waiting for the team lead’s decision, and machine adjustment.

After changing the downtime codes, you can check which problem costs the most time and base the decision on hard data.

Gemba walk helps you see the problem, but data shows its scale: downtime, stop frequency, impact on OEE, and differences between shifts. If you want to move from observation to number-based decisions, check how to monitor OEE, downtime, and production data in real time.

You lose the most value when a gemba walk turns into checking people.

Avoid these mistakes:

“We are checking production” is too much. “We are checking the causes of downtime on line A” works better.

First understand the working conditions. Decide later.

The team lead sees part of the process. The operator sees details that often decide where waste starts.

If the team reports a problem and hears nothing about what happens next, the next walk will be treated as a formality.

A gemba walk should end with a small test, a change in the standard, or a decision about what is still missing before a conclusion can be made.

The first gemba walk does not have to be long. What matters is that it leads to a result.

After 7 days, go back to the same place and check whether the change worked and whether the numbers confirm it.

Choose one process that costs time today, creates defects, or blocks the team. Check the data, go to the place where the work happens, ask a few good questions, and write down one thing to test.

A good gemba walk should end with one decision, one test, and one number that shows whether the process is really working better.

If, after your first walk, you see many problems but do not have reliable data on their scale, the next step may be real-time OEE and downtime monitoring.

A gemba walk means going to the place where the work is done, observing the process, and talking with the team. The goal is to understand the facts before making a decision.

No. Gemba can be a shop floor, warehouse, lab, service area, customer service office, or administrative process. What matters is the place where value is created for the customer.

An audit checks compliance with requirements. Lean gemba walk helps you see how the process works in daily work, where waste appears, and what blocks the team.

For a stable process, a fixed rhythm can work well, for example once a week. For a quality issue, downtime problem, or major change, shorter walks over several days may work better.

After the walk, choose one change and assign a measure to it: downtime, setup time, number of defects, OEE, or stop reason. That way, you can see whether the observation actually led to a process improvement.