Gemba Walk Checklist: What to Look For, and What to Ask Instead of Tick

A gemba walk is when a manager goes to where the work actually happens — the gemba, Japanese for "the real place" — to observe the process, ask the people doing it how it works, and look for waste. It comes from the Toyota Production System and it's built on three habits: go and see, ask why, and show respect.

The trap is in the title of this page. A gemba walk is observation, not inspection, and the moment you carry a checklist of boxes to tick, most people quietly turn it into an audit. So this checklist is mostly questions. That's deliberate, and the rest of the page explains why it's the only version that works.

A gemba walk is not an inspection

This distinction is the whole point, and it's the one that gets lost first.

An inspection asks is this right? A gemba walk asks why is it like this? Both are useful. They're not the same thing, and doing an inspection while calling it a gemba walk trains the people on the floor to perform for you — which destroys the only thing a gemba walk can give you, which is seeing the work as it really is.

If what you need is compliance checking, use a proper inspection — a 5S audit, a GMP audit or a workplace inspection. They're good tools. They're just not this one.

The three habits

1. Go and see — genchi genbutsu

The core idea is that you cannot understand a process from a report about it. Data summarises; it doesn't show you the operator walking twelve metres to fetch a tool, or the part waiting on a bench because the next station is busy, or the workaround everybody uses because the standard method doesn't work on Thursdays.

The most famous illustration is attributed to Taiichi Ohno, the architect of the Toyota Production System: he is said to have drawn a chalk circle on the factory floor and had a manager stand in it — for hours — simply observing, until they could see what he saw. You don't need to do it for hours. The point stands: stand still and watch before you say anything.

2. Ask why

Not "why did you do that?" — which is an accusation — but "why does it work this way?", asked of the process rather than the person. The repeated-why technique comes from the same tradition: keep asking until the answer stops being about a person and starts being about a system.

3. Show respect

The people doing the work know more about it than you do. A gemba walk that treats them as the subject of inspection rather than the source of knowledge gets polite answers and learns nothing. Respect in practice means: tell people why you're there, ask rather than assume, and never use what you learned on a gemba walk against the person who told you.

Before you go

Five questions, answered before you set foot on the floor:

• What's the purpose of this walk? A theme, a problem, a value stream — not "just to have a look". Walks without a focus become tours.
• Which process, specifically? Follow one value stream end to end rather than drifting around the whole site.
• Have you told the area? Unannounced walks read as inspections. Say when, and say why.
• Who's coming? Small is better. A procession of managers is a performance, not an observation.
• What happened to the last walk's actions? If nothing, fix that before generating more.

On the floor: what to watch for

The eight wastes

The traditional lens is the wastes of lean — seven identified in the original Toyota system, with an eighth, unused talent, added later. The mnemonic is TIMWOODS:

The two that are easiest to see and most often missed are inventory and waiting. A pile of work in progress between two stations is a visible sign that the flow is broken, and it's sitting there in plain sight. A person standing idle waiting on a machine is the same signal, and it's easy to misread as the person being idle rather than the process making them wait.

Standard work

• Is there a standard way to do this task, and is it written down or shown?
• Is the work actually being done that way?
• If not, is the standard wrong, or is the work wrong? This is the important one. When people deviate from a standard, it's very often because the standard doesn't work — and they've found something better that nobody has written down.

Visual management

• Can you tell, at a glance and without asking, whether this area is on target today?
• Is it obvious what's normal and what's abnormal?
• Where's the problem visible — or does it only show up in a report tomorrow?

Flow

• Follow one part or one order from start to finish. Where does it stop?
• Where does it go backwards?
• Where does it wait?

Safety

• Where would somebody get hurt doing this job the way it's actually done — not the way the procedure says?
• What workaround exists because the safe way is slower?

That last question overlaps with a behaviour-based safety observation, and it's the same principle: when the unsafe way is the easy way, the finding is the system, not the person.

The questions to carry

This is the checklist that matters. Not boxes — questions. Open ones, asked of the people doing the work.

To understand the work:

• Can you walk me through what you're doing right now?
• How do you know this is done correctly?
• What happens right before this reaches you — and right after it leaves?

To find the problems:

• What slows you down?
• What do you have to work around?
• What goes wrong here most often?
• If you could change one thing about this job, what would it be?

To find the standard gap:

• Is there a written way to do this? Does it match how you actually do it?
• What would a new starter get wrong on their first day?

To show you'll act:

• What happened to the last thing somebody suggested?

Questions to avoid: anything starting "why didn't you…", anything with the answer built in ("don't you think it would be better if…"), and anything about individual performance. Those turn an observation into an interrogation, and the answers you get stop being true.

After the walk

This is where most gemba programmes quietly die, and it's the part the published checklists leave out.

• Write it down the same day. Observations fade fast, and the specific detail — which station, which step, what the operator actually said — goes first.
• Separate observation from action. Record what you saw, then decide what to try. Not everything seen needs fixing, and not everything needs fixing by you.
• Close the loop visibly. Go back and tell the people who told you things what happened to their input. This single habit decides whether the next walk gets honest answers.
• Fix processes, not people. If an action item has someone's name as the problem rather than as the owner, rewrite it.
• Track what changed. A gemba walk that produces observations and no experiments is a tour.

The mistakes that kill it

Turning it into an audit. Carrying a tick-box sheet and marking areas down. People learn within two walks that you're inspecting them, and from then on you see the performance, not the work.

Fixing things on the spot. A manager spots a problem and solves it in front of everyone. It feels like leadership. It teaches the team that problems are solved by managers, and it skips understanding why the problem exists — so it comes back.

Walking everywhere and seeing nothing. A broad tour of the whole site covers a lot of ground and learns very little. Follow one process deeply.

Treating it as a ritual. A weekly walk at the same time, the same route, the same questions, with no follow-up. It becomes something the floor prepares for, which is the opposite of the point.

Using what you learn against people. Once. It only takes once, and the practice is over.

How often, and for how long

There's no single rule, but patterns that hold up in practice:

• Frontline supervisors: daily, short — fifteen to thirty minutes.
• Area and department managers: a few times a week.
• Senior leaders: weekly or fortnightly, focused on one value stream at a time.

Regularity matters more than length. A short walk that happens reliably and closes its loops does more than a long one that happens when someone remembers.

Capturing it without breaking the method

Here's the practical tension a gemba walk creates: the method depends on watching and listening, and a clipboard or a phone held up to type on is exactly the thing that makes you look like an inspector and makes people perform.

So observations usually get written up afterwards, from memory — and that's where the quote the operator gave you becomes a paraphrase, and the specific station becomes "the line".

Speak while you walk, and the document the law or the client wants writes itself. A quiet voice note between stations — "station 4, operator walks to the rack for the 10mm driver maybe eight times an hour, says it used to live on the bench before the reorganisation" — keeps the exact detail without holding a device up at anyone. It's the difference between an observation you can act on and one you remember the gist of.

Related

• 5S audit checklist — Sort, Set in Order, Shine, Standardise, Sustain, scored separately
• GMP audit checklist — good manufacturing practice, walked
• Behaviour based safety observation — observing a task, with the same "fix the system" principle
• General workplace inspection — for when you genuinely do need an inspection

Frequently asked questions

What is a gemba walk? A practice from lean manufacturing where managers go to where the work happens — the gemba, "the real place" — to observe the process, talk to the people doing it, and look for waste and improvement. It comes from the Toyota Production System and rests on three habits: go and see, ask why, and show respect.

What is the difference between a gemba walk and an audit? An audit checks conditions against a standard and produces findings. A gemba walk observes the process to understand it and produces questions and experiments. An audit asks "is this right?"; a gemba walk asks "why does it work this way?" Mixing them up — carrying an audit checklist on a gemba walk — makes people perform instead of showing you the real work.

What does gemba mean? Gemba is Japanese for "the actual place" or "the real place" — in lean, the place where value is created, usually the shop floor. The related principle genchi genbutsu means "go and see for yourself".

What should you look for on a gemba walk? The eight wastes (TIMWOODS: transport, inventory, motion, waiting, overproduction, overprocessing, defects, unused skills), whether standard work matches actual work, whether problems are visible at a glance, and where the flow stops or goes backwards.

How long should a gemba walk take? Fifteen to thirty minutes for a frontline supervisor's daily walk; longer for a focused walk following one value stream. Consistency matters more than duration.

Is a gemba walk the same as management by walking around? Related but different. Management by walking around is general visibility and presence. A gemba walk has a specific purpose, follows a specific process, focuses on the work rather than the people, and is expected to produce follow-up. It's more disciplined, and the follow-up is what distinguishes it.