Gemba Walk Checklist

What this tool does

CM8-262 is a working record for leader standard work — the regular, structured walk of the place where the work actually happens. Each row is one observation from one walk: what you saw, the question you asked, what the team said, and the follow-up if one is needed. The tool counts your walks against a monthly target, shows the mix of what you are noticing, tracks every follow-up to the point where the team has been told the outcome, and prints a report you can put in front of a management team.

Everything runs inside this single file. There is no account, no upload and no network request of any kind, so what you saw on the floor — and what people told you in confidence at the machine — never leaves the computer you are using.

What a gemba walk is

Gemba is the Japanese word for the real place — where value is actually created — and the habit of leaders going there to see the work first-hand comes from the Toyota tradition of genchi genbutsu: go and see for yourself. A gemba walk is a short, regular, deliberate visit to the floor to watch the actual work, ask genuine questions, and understand the gap between how the process is supposed to run and how it really runs.

It is not an inspection and not an audit, and the difference is the whole point. An audit checks the work against a standard and scores the people; it arrives with a clipboard and leaves with findings, and the floor prepares for it by hiding problems. A gemba walk checks the process and respects the people; it arrives with curiosity and leaves with questions, and the floor prepares for it — after a few months of it being done well — by saving up the things they want to show you. If your walks produce fear, tidying-up the night before, or a list of names, they have become audits, whatever you call them. The person doing the job is almost never the reason the job is hard to do right.

Observations — facts, not judgements

Write down what a camera would have recorded, not your verdict on it.

Bad: “Packing area a mess, team not following FIFO, poor discipline.” Three judgements, zero facts, and an insult in writing.

Good: “FIFO lane bypassed at packing — newest cartons shipped first; three pallets of older stock pushed to the back of the lane.” That is checkable, discussable, and it points at the process: something makes bypassing the lane the easier path, and the interesting work is finding out what.

The tool nudges you the same way: an observation of only a few words is rejected, and a concern cannot be saved without a follow-up action — a concern with no follow-up is a drive-by criticism, and the floor keeps score of those.

Asking instead of telling

The fastest way to end a floor conversation is to answer your own question. The walk is for understanding, and understanding comes from questions the team can answer honestly without defending themselves. Compare:

• “Why did you bypass the FIFO lane?” — an accusation with a question mark. The honest answer is now dangerous, so you will get a safe one.
• “What makes it faster to bypass the lane?” — an invitation. The answer (“the lane entrance is blocked every morning”) is the actual problem, handed to you for free.

Questions in the shape of what makes it easier to… / what gets in the way of… / what would have to be true for… assume the person is behaving sensibly inside a system you cannot see yet — which is nearly always the truth. This is the coaching style behind improvement kata: the leader's job on the walk is to develop people's thinking about their own process, not to dispense solutions from visiting altitude. Record the question you asked and the response you got; six months of those responses is a better map of your operation than any value-stream diagram.

The positive ratio

People repeat what gets noticed. If the only observations that ever reach paper are concerns, the walk teaches the floor that being seen is bad news, and the things you most need to see will start happening when you are elsewhere. Deliberately recording what is working — the batch check that caught the wrong reel, the fork-lift driver who stopped at the blind corner — and saying so at the machine costs nothing and changes what the next walk finds.

The tile aims you at roughly one positive in three observations. That is a guide, not a law: a ratio near zero means the walk has become fault-finding; a ratio near one means you are either running a remarkable operation or not looking very hard.

Follow-ups and closing the loop

Walks die for one reason above all others: the floor points at a problem, the leader nods and writes it down, and nothing visibly happens. After two or three rounds of that, people stop pointing — reasonably. So the follow-up discipline in this tool runs one step further than “done”:

• Open / In progress — the action is live, with an owner and a due date. Overdue items are flagged in red, because an overdue follow-up is visible to the team that raised it even if it is invisible to you.
• Done — the action is complete. Not the finish line.
• Closed & fed back to the team — someone went back to the people who raised it and told them what was done and why. This status is the whole game. The feedback-closure tile shows what fraction of your completed actions were actually fed back; if it is low, you are fixing things in secret, and getting none of the trust the fix should have bought.

Not every observation needs an action — “Noted” is the honest status for a positive or a small question answered on the spot. But every concern needs one, and the tool insists.

Cadence over depth

A twenty-minute walk every week beats a two-hour walk every quarter, and it is not close. Frequency is what makes the walk normal instead of an event: the floor stops performing for it, patterns become visible across weeks, and follow-ups get checked while they are still warm. The quarterly grand tour, by contrast, sees a prepared floor and leaves a long list nobody revisits.

The walks-per-month chart is therefore the first chart, with your target drawn across it (weekly — four a month — is the usual leader standard work commitment). Treat a falling line as the earliest warning light: the register keeps looking healthy for a month or two after the walking stops, and then it doesn't.

Rotating the themes

Walking with a theme — safety this week, flow next week, standard work the week after — stops the walk becoming a tour of the same three familiar problems. The theme is a lens, not a blindfold: if you are walking for flow and see an interlock taped over, you record it under safety and deal with it. Over a quarter, rotation gives every dimension of the operation a turn under deliberate attention, and the theme-mix chart shows what each lens is surfacing. The area chart does the same job for geography: a least-walked area on the tile is an area whose problems are currently invisible to you.

FAQ

Who should walk? Anyone who leads — supervisors daily, managers weekly, senior leaders at least monthly. This register supports several walkers; the cadence chart counts each person's walk on each date separately.

How long should a walk take? Twenty to forty-five minutes. Long enough to watch a process actually run, short enough to happen every week. Three to five good observations is a normal yield; eleven rows from three walks, as in the sample, is healthy.

Should I fix things during the walk? Fix genuine danger immediately, obviously. Everything else: resist. Solving problems on the spot trains the floor to wait for you, and it usually means solving the wrong problem quickly. Record it, ask the questions, and let the owner named on the follow-up do the fixing.

Should observations name people? Name people for positives if you like; for concerns, describe the process and the conditions. The register may be read widely, and “station 4's chart is out of date” ages better than a colleague's name next to a criticism.

Is this a 5S or layered-process audit? No. Those are checklists scored against a standard, and useful in their place. This is the open-ended senior habit that makes those tools honest.

Saving your work

Observations, settings and the report header are written to this browser's local storage as you type, and the toolbar shows the time of the last save. That storage belongs to one browser on one computer: another browser, a private window, a second machine or a clean-up tool that clears site data will not have it.

Treat Export .json as the real save — one file containing everything, which Import .json restores anywhere. Export CSV gives you the register for spreadsheet work. Reset asks twice, then erases everything this tool has stored. There is no undo. Walk records contain candid remarks made by named colleagues — treat exports accordingly.

Accuracy & disclaimer

The arithmetic here is counting and division, done faithfully: walks are distinct date-and-walker combinations, the positive ratio is positives over all observations, and feedback closure is fed-back items over all closed items. What the numbers mean depends entirely on what was recorded — a walk logged is not the same as a walk done well, and an observation is one person's view on one day.

This checklist structures attention; the value is created in the conversation at the machine and in the follow-through afterwards, neither of which a file can do for you. It is a record-keeping aid, not a safety inspection, not a compliance audit, and not a substitute for either where one is required.