Gemba Walk Mistakes: 9 Ways a Walk Turns Into an Inspection

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

Nine gemba walk mistakes that turn a learning walk into an inspection, and how to fix each one with respect for people, better questions and coaching.

A gemba walk turns into an inspection when the leader goes to check people instead of learning how the work flows. Most of the damage comes from nine habits, and all of them can be changed. This article is for lean managers who run walks or coach other leaders to run them. It groups the gemba walk mistakes by when they happen: before, during and after the walk. Gemba is Japanese for "actual place", the place where work is done.

Key points

• A gemba walk turns into an inspection when the leader checks people instead of learning how the process works and what gets in the way of the team.
• Nine common mistakes fall into three groups: how you prepare, how you behave on the floor and what you do after the walk.
• Respect for people is a practice, not a mood. It means observing the work, listening, coaching and clearing obstacles, as the Lean Enterprise Institute describes it.
• Ask more than you tell. Counting your questions against your statements during a walk gives you a simple, honest measure of your behaviour.
• Follow up on the one or two problems the team chose, so that people see a walk lead to change and not to blame.

Gemba walk mistakes before you leave the office

Why do walks drift into inspections? Mostly because managers are used to checking results. Checking feels productive, since you can count findings. Learning is slower and less visible, so without a deliberate change of habit the check wins. Naming the mistakes helps, because you can pick one and practise it.

Three mistakes happen before you take the first step.

1. Going without a purpose. A walk with no question produces general impressions. The Lean Enterprise Institute suggests looking at each gemba through three lenses: purpose, process and people. Decide which one you are looking at today and write one question. You can find the idea in its article How to go to the gemba.

2. Not telling the team why you are coming. People who are surprised by a manager with a notebook assume they are being checked. Tell the team leader the day before what you will look at, and say that the walk is not about judging individuals.

3. Going only when something is wrong. If your visits come with bad news, the team learns to link your presence with trouble. Walk in good weeks too. You will learn what normal looks like, and the team will see that you come to understand, not only to react.

Mistakes on the floor

Four mistakes show up in your behaviour at the station.

4. Looking for who, not why. Michael Ballé of the Lean Enterprise Institute calls seeing reality "without blaming the guys doing the work" a foundational skill. You can read his view in Gemba, workplace, genchi genbutsu, go-and-see: what is the difference?. If your first question is "who did this?", you have started an inspection. Ask "what happened?" and "what made it hard?" instead.

5. Solving on the spot. A quick order from a leader who has watched for a few minutes often misses the cause. The Lean Enterprise Institute warns against issuing prescriptions from a distance and against leaders acting as the only source of answers. Diagnose and decide close to the work, with the people doing it. There is one exception: if you see a safety hazard, act on it at once and explain why.

6. Talking more than listening. If you explain, teach and correct for most of the walk, you learn little. Active listening is one of the seven practices of leading with respect described by Mike Orzen in the Lean Enterprise Institute article How to lead with respect. Try to ask open questions, such as "What happens when this part is missing?", and then wait.

7. Hunting for waste without asking why it exists. Spotting waste is easy. Understanding its cause is the real work. The Lean Enterprise Institute notes that treating waste elimination as the goal, without finding causes, is a trap. A pile of parts is a symptom. Ask what made the pile.

Mistakes after the walk

Two mistakes happen when you are back at your desk.

8. No follow-up. If nothing visible changes after a walk, people stop sharing what they know. Agree one or two actions with an owner and a date, tell the team the plan and review it at the start of the next walk.

9. Finding problems but not developing people. A leader who solves everything creates a team that waits. Orzen lists teaching and coaching among the seven practices, where leaders build people's problem-solving skills through hands-on learning. After a walk, ask the team leader what they would test, then support the test.

What a good walk looks like instead

In lean management, leaders go to the gemba to see how work really happens and to find improvement opportunities with the people who do it. The aim is to improve processes through continuous improvement, and that needs trust. Frontline staff only share what they know if they expect to be heard. This is why the tone of a walk matters as much as its content, in lean manufacturing as in any other setting.

A good walk is not a softer inspection. It is a different activity with a different goal. Orzen's article calls the gemba walk the basis of showing respect and of achieving real understanding. It quotes Jim Womack saying that problem-solving, done with people, is "actually the highest form of respect". Respect here is not politeness. Orzen says that leading with respect is not a soft skill. In the other article's words, it includes setting demanding expectations.

In practice, coaching on the floor follows a short pattern:

1. Ask what the problem is. Let the team leader describe it in their own words.
2. Ask what they have tried. You learn what they know and what they lack.
3. Ask what they would test next. Agree a small experiment, which lean practice calls a kaizen, a practical improvement made close to the work.
4. Ask what help they need. Then do your part and clear the obstacle.

These gemba walk best practices are simple, but they only work if you use them every time. The same questions on each walk make people comfortable, because they know what to expect. Use the same four questions in everyday talks with team leaders, not only on formal walks, so that coaching becomes part of normal work.

Example: a talk-time and question check

This is an illustrative example with made-up numbers. A lean manager wants to know whether her walks feel like inspections. A colleague joins her on two walks of 30 minutes each and tallies what she says: questions and statements.

• Walk A: 28 things said, of which 6 were questions and 22 were statements or instructions. Questions: 6 ÷ 28 = 21 percent.
• Walk B, after she prepares three open questions in advance: 30 things said, of which 17 were questions and 13 were statements. Questions: 17 ÷ 30 = 57 percent.

The change is not a target. There is no published ideal ratio, and the numbers say nothing about quality. They give her a simple signal that she is listening more. She also asks the team leader on Walk B what they noticed. The answer: "You let us finish this time." That feedback tells her more than the percentage does. She repeats the tally once a month to check that the habit holds.

Common mistakes

These are the mistakes leaders make when they try to fix the nine above.

• Using the list as a scorecard against managers. Share it as a self-check, not as a judgement.
• Trying to change everything at once. Pick one mistake per month and practise it.
• Dropping walks after one bad one. A clumsy walk is a chance to learn. Say so to the team, and go again.
• Blaming the team for hiding problems. People behave the way they are treated, as Orzen puts it. If problems stay hidden, look at how past problems were received.
• Copying a checklist from another plant. Without the purpose, the questions turn into a form to tick.

How software can help

Software cannot teach respect, but data can help you walk with a clear question and spend less time guessing where to look. iFAKT is a Stuttgart-based consulting company and software specialist for Industry 4.0, founded in 2001. It develops the Polaris production software, which combines ERP data with a digital twin of manufacturing and AI to optimize production schedules, reveal bottlenecks and improve on-time delivery. With such a view you can prepare your question before the walk. On the floor, the conversation with the team still does the work.

Next step

Pick one of the nine gemba walk mistakes that you recognise in your own walks, and practise fixing it on your next walk. After the walk, ask the team what you did differently and what they would like you to keep.