What Is a Gemba Walk? A Practical Guide for Plant Managers

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

What is a gemba walk? A plain guide for plant managers: the meaning, how a walk works in manufacturing, a worked example and the mistakes that spoil it.

A gemba walk is a routine in which a leader goes to the place where the work happens, watches the process and asks the people who do the work questions. This guide is for plant managers who want to start gemba walks, or who want to fix walks that have turned into inspections. You will learn what the term means, how a walk works in manufacturing, what to do on the floor and what to avoid. A worked example shows the idea with simple numbers.

Key points

• A gemba walk is a routine in which a leader goes to the place where the work happens, watches the process and asks the people who do the work questions.
• Gemba is Japanese for actual place. In a plant it is the shop floor, the line, the warehouse dock or any spot where value is created.
• A walk is not an inspection or an audit. Its purpose is to understand current conditions and to support the people who do the work.
• Follow one product from start to finish, ask what, why and what if, and write down facts instead of opinions.
• A walk only pays off when you act on it. Pick one small fix per walk and report back to the team.

What is a gemba walk? The meaning explained

Gemba (also written genba) is Japanese for "actual place". The Lean Enterprise Institute defines it as the place where value-creating work happens, and in manufacturing that is usually the shop floor. A gemba walk is the visit itself. The Lean Enterprise Institute's lean lexicon entry on gemba describes the walk as a practice in which leaders use first-hand observation and questioning to understand current conditions before they act.

That gives you the gemba walk meaning in one sentence: you go to the real place, you watch the real work and you ask real questions. You do not sit in a meeting room and read a report about the work. The method belongs to lean management and lean manufacturing, but the idea travels. The same lexicon entry names an operating room in a hospital, a job site in construction and software code in software development as examples of other places where value is created.

Do not confuse the walk with management by walking around, a related management habit. A later article in this series compares the two. A related term is genchi genbutsu, which roughly means "go and see for yourself". Lean authors use the two terms almost interchangeably. Michael Ballé points out a difference in emphasis: gemba names a place, while genchi genbutsu names an act. You can read his view in Gemba, workplace, genchi genbutsu, go-and-see: what is the difference?. For a plant manager the practical point is the same: facts come from the floor.

Walk, tour or audit: what is the difference?

Three activities look alike from a distance, because in all three someone walks through the plant. They have different goals.

• A plant tour shows the site to visitors. The host talks, the visitors watch, and nobody expects an action afterwards.
• An audit checks the plant against a standard, such as a quality or safety procedure. The auditor looks for gaps and records findings.
• A gemba walk is a learning routine for leaders. The leader watches the process, asks questions and leaves with a better picture of current conditions.

The difference matters for how people behave. In a check they defend their work. On a good walk they explain it. Operators and team leaders are the experts on their own station. They know which tool is worn, which supplier delivers late and which step needs a third hand. A manager who asks and listens gets this knowledge. A manager who checks and corrects does not.

Who should walk? Plant managers are the obvious group, but department heads, planners, maintenance leads and quality leads gain just as much. Planners in particular rarely see how their schedule plays out at the machine. A planner who has stood at a work centre for an hour plans differently afterwards. If you bring a colleague, agree on a role in advance: one person asks, the other takes notes.

Benefits: why plant managers walk the floor

Reports are always late and always summarised. A weekly output figure tells you that a line missed its target. It does not tell you that the operator waits four minutes for a pallet every hour. You only see that when you stand there.

A walk has several benefits:

• You see problems and opportunities for improvement first-hand. You find small, repeated delays and other inefficiency that never reach a report.
• You hear the reasons. The people at the machine usually know why a step is slow. You only learn it if you ask.
• You show that the work matters. Frontline staff notice when a manager comes to the line with a real question and listens to the answer. Over time this helps to build trust.
• You identify bottlenecks. Direct observation shows where work piles up and where people wait, which is the first step towards removing the constraint and raising productivity.

The last point links to Toyota's well-known guidance for leaders. The Lean Enterprise Institute attributes the phrase "go see, ask why, show respect" to Toyota chairman Fujio Cho. Its article How to go to the gemba adds that respect includes setting demanding expectations, not only being polite.

Regular gemba walks also build a culture of continuous improvement, the habit of improving a process in small steps over time. A walk gives you facts, and facts give a team something concrete to work on. Many walks lead to a small kaizen, a step in continuous improvement and a practical change made close to the work by the people who run the process.

How a gemba walk works in manufacturing

A gemba walk in manufacturing follows a simple pattern. The steps below suit a first walk. A separate article in this series covers the full plan and agenda, and another offers a gemba walk checklist with questions.

1. Choose one focus. Pick one product family, one line or one question, such as "Why do we wait for material at final assembly?" The Lean Enterprise Institute suggests following a single product family or customer-facing process from start to finish across departments.
2. Tell people you are coming. Say what you will do and why. Say clearly that you are not there to check on individuals.
3. Walk the flow. Start where the material enters and move with it, or start near the customer and work backwards. Stay at each step long enough to see several cycles.
4. Ask open questions. Start with what is happening. Then ask why. Later ask what would happen if something changed. Ask people about the process, not about themselves, and ask for their improvement ideas.
5. Write down facts. Note times, counts, distances and what you saw. Leave out opinions and names.
6. Close the loop. Thank the team, choose one opportunity for improvement, agree one small action and tell them when you will report back.

Keep each gemba walk short and regular. A repeated 30-minute gemba walk teaches you more than a long visit once a year, because you start to notice change. You also build trust, because people learn that a walk leads to a fix and not to blame.

Example: one hour at a packing station

This is an illustrative example with made-up numbers, not a measured case. A plant manager walks to a packing station that is often late. She has one question: "What stops the packers from working?"

She stands at the station for one hour and writes down what she sees:

• The packer leaves the station to fetch cartons from a store 40 metres away. This happens 6 times in the hour.
• Each trip takes 3 minutes there and back.
• During a trip the station does not pack anything.

The arithmetic is short:

• Time lost per hour: 6 trips × 3 minutes = 18 minutes.
• Share of the hour: 18 ÷ 60 = 30 percent.
• Over a 7.5-hour shift: 30 percent of 450 minutes = 135 minutes.

She asks the packer why cartons run out. The answer: the store hands out one pallet at a time and the station holds only one carton stack. She does not issue an order. She asks the packer and the team leader what would work. They suggest a small carton buffer next to the station, refilled once per hour by a material handler.

Nobody was blamed, and nobody needed a new machine. The fix is a layout and routine change, and it is small enough to test the next day. The change can streamline the packer's day. That is the typical outcome of a good walk: one clear observation, one number and one small action.

Common mistakes

• Treating the gemba walk as an inspection. If people expect to be checked, they hide problems. Say the purpose out loud and keep to it.
• Walking without a question. A tour with no focus produces general impressions and no action.
• Giving orders on the spot. Orders from a manager who has watched for five minutes miss the context. Ask questions and let the team propose the fix.
• Looking only for waste. The Lean Enterprise Institute warns against spotting waste without understanding its causes. Ask why it happens.
• Never reporting back. If nothing visible happens after a walk, people stop sharing what they know.
• Going only when something is wrong. Walks in good times show you what normal looks like, which makes the next problem easier to read.

How software can help

Software cannot replace the walk, but data can help you choose where to walk. KPI dashboards, schedule data and a model of the plant can show where flow breaks down, so your hour on the floor goes to the right place. iFAKT is a Stuttgart-based consulting company and software specialist for Industry 4.0, founded in 2001. It develops Polaris, a production software that combines ERP data with a digital twin of manufacturing to reveal bottlenecks. Whatever tool you use, the walk still gives you what data cannot: why people work the way they do.

Next step

Plan your first gemba walk for this week: pick one line and one question, and block 30 minutes in your calendar. Afterwards, tell the team what you saw and which small change you will try, so the next gemba walk starts with their trust.