White Belt · 12 min
Go and see: what a walk gives you that a report cannot
After this you can
- explain what visual management is for and give an example that would work in my area.
- prepare for a Gemba walk by listing what I will observe and what I will ask.
Assumes you have done Mapping the gaps, not the boxes.
The problem
A manager spent two weeks analysing pick errors from the warehouse system and arrived with a proposal for a new scanning workflow. On the floor, a picker showed her the tote she was holding: the label had been reprinted by hand because the printer in aisle 7 had jammed again, and hand-written totes bypass the scan entirely. That workaround had been running for nine months. It appears in no system, because a workaround that keeps the work moving is invisible to every report the work produces.
The idea
Gemba is the place where the work actually happens. A Gemba walk is going there and watching, and it exists because of a specific limitation of data: a report can only contain what somebody decided to record. Workarounds, informal handoffs, the second spreadsheet everyone keeps, the exception path that carries a third of the volume — none of them are in the system, and all of them are visible in ten minutes on the floor.
Why it needs a plan
Every failure mode of a Gemba walk is a failure of intent, and intent is decided before you arrive.
Arriving to check rather than to learn. The moment the people doing the work believe they are being audited, you stop being told anything. This is not recoverable within the visit, and often not within the year. An audit is a legitimate activity; it is a different activity, and it should be called what it is.
Arriving with the answer. A walk conducted to confirm a solution will confirm it. You will see the things that support it and not notice the things that do not.
Fixing things on the spot. Deeply satisfying, and it destroys the evidence. Straighten the jammed printer and you will never learn that it jams four times a shift.
Going once. A process at 10am on a Tuesday is not the same process as at 3am on a Sunday — different staffing, different volume, different workarounds. Whichever you watched, say which one it was.
What a plan contains
What you will watch. Observable things. Not "whether they understand the standard" — you cannot see understanding — but "what they do when the part does not fit". The workaround is the answer to almost every good observation.
What you will count. Something simple, repeated: how many times a person leaves the bench, how many items are waiting at ten-minute intervals, how often the exception path is taken. Without a count the walk produces impressions, and impressions lose every argument against a spreadsheet — including a wrong one.
What you will ask. Open questions. "Walk me through what you do when…", "show me the last time this went wrong". A closed question ends the conversation at the point it should start; a leading one produces agreement, and agreement is not information.
Visual management: the same idea, standing still
Visual management is making the state of the work visible without anyone having to ask. A board showing what is due today, a marked floor space that is empty when it should be full, a red bin that fills with rejects where everyone can see it.
The test is simple: could a person walk in and tell within thirty seconds whether things are normal? If the answer needs a login, a report, or a conversation, it is not visual management.
The connection to the walk is direct. Good visual management is a Gemba walk you do not have to be present for — it makes abnormality obvious at the moment it occurs, to the people who can do something about it, rather than in a monthly report to people who cannot. And the first thing a walk usually reveals is that the only genuinely visual signal on the floor is one somebody made themselves out of a whiteboard and tape.
Worked example
Here is a real-shaped first draft, written in good faith by a manager who has read about Gemba walks:
| Field | As written |
|---|---|
| Process | Audit of picking compliance in the next-day area |
| Where | Aisles 4 to 9 |
| When | (blank) |
| Watch | Whether pickers understand the new layout |
| Watch | Check that they follow the pick standard |
| Count | (nothing) |
| Ask | Is the standard being followed? |
| Ask | Wouldn't it be quicker with a second bench? |
Eight problems, and every one of them decides how the visit will go before it starts.
"Audit of picking compliance" is the whole visit in three words. It has told everyone on the floor what this is, and they will behave accordingly — correctly and unusually, for exactly as long as the manager is standing there.
"Whether pickers understand the new layout" cannot be watched. Understanding is a state of mind; you will end up inferring it from behaviour and calling the inference an observation. Replace it with what you would see: what a picker does when the location is empty.
"Check that they follow the pick standard" makes the people the object of the check. The useful version asks what the standard requires that the work does not allow — which is the same visit conducted so that somebody will tell you something.
Only two things to watch. Two is not a plan, it is a hypothesis with a clipboard. Fewer than three usually means somebody has already decided what the walk will find.
No time or shift. The layout problem, if it exists, will look completely different on nights.
Nothing to count. The walk will produce a page of impressions and lose to the system report in the first meeting.
"Is the standard being followed?" can be answered yes. It will be.
"Wouldn't it be quicker with a second bench?" has the answer in it. The picker will agree, because agreeing is easier and because you are their manager.
The same visit, replanned:
| Field | Rewritten |
|---|---|
| Process | Picking and packing for next-day orders |
| Where | Aisles 4 to 9, and the pack bench |
| When | Tuesday 06:00 early shift, and Thursday 22:00 nights |
| Watch | What a picker does when the location is empty |
| Watch | What happens to an item that fails the scan |
| Watch | Where totes queue between picking and packing |
| Count | How many times a picker leaves the aisle |
| Count | Totes waiting at the pack bench, every 10 minutes |
| Ask | Walk me through what you do when the location is empty |
| Ask | Show me the last item that came back from packing |
| Ask | What slows you down most on a normal shift? |
Nothing here is harder to do than the first version. It is the same hour on the floor. The difference is that the second one can return something the manager did not already believe — and "what happens to an item that fails the scan" is the observation that finds the hand-written totes.
Dataset: ds-gemba-plan-draft — the same data loads in the tool below, so you can reproduce every figure here yourself.
Your turn
The planner opens with the audit-framed draft.
- Read the seven findings. Note how many are about wording — that is not pedantry. Wording is where intent shows up, and intent is the only thing that decides whether the visit is worth an hour. Seven of the eight problems above are here. The missing one is "Check that they follow the pick standard" — and the tool does recognise that phrasing; it stops after the first framing problem it finds, and "Audit" in the process name gets there first. One finding of a kind is enough to make the point, which is a reasonable design and a thing worth knowing when you are counting.
- Rename the process to remove "audit" and watch the framing finding move rather than clear — it re-fires on "compliance", the next word in the name that says the same thing. That is worth more than a finding that disappears: the framing was never in one word.
- Rewrite both observations as things you could see happen, and add a third.
- Add two things to count. This is the entry people skip, and it is the one that makes the walk survive contact with a meeting.
- Rewrite the two questions as open ones. "Is the standard being followed?" becomes "walk me through what you do when…". Watch both findings clear.
- One thing no plan can contain, and the tool says it once the plan is clean: while you are there, do not fix anything. Write it down and come back.
Gemba Walk Planner
practiceOne process, named. Otherwise the walk becomes a tour.
The physical place the work happens.
A process at 3am is not the same process.
What you will watch2
Things you could see happen. Not what you would conclude about anyone.
- Whether pickers understand the new layout
- Check that they follow the pick standard
What you will count0
Something simple and repeatable, so the walk produces data and not only impressions.
What you will ask2
Open, not leading. "Walk me through…", "show me the last time…".
- Is the standard being followed?
- Wouldn't it be quicker with a second bench?
no time or shiftNo time or shift stated. A process at 10am on a Tuesday is not the same process as at 3am on a Sunday — different staffing, different volume, different workarounds. Whichever you watch, say which one it was.
audit framing"Audit" frames the visit as an inspection. The moment the people doing the work believe they are being audited, you stop being told anything — and that does not recover within the visit. Go to learn how the work actually happens, including the workarounds, which are the most useful thing anyone can show you.
observation is a judgement"Whether pickers understand the new layout" — "understand" is a state of mind, which cannot be watched. Replace it with what you would actually see happen. Not "whether they understand the standard" but "what they do when the part does not fit".
too few observations2 things to watch. Fewer than 3 usually means you have decided what you expect to find, and a walk conducted to confirm something confirms it.
nothing to countNothing to count. Without a count the walk produces impressions, and impressions lose every argument against a spreadsheet — including the wrong spreadsheet. Count something simple: how many times a person walks away from the bench, how many items are waiting, how often the exception path is taken.
closed question"Is the standard being followed?" can be answered yes or no, which ends the conversation at the point it should start. Open it: "what happens when…", "walk me through…", "show me the last time…".
leading question"Wouldn't it be quicker with a second bench?" — "Wouldn't it" tells the person what answer you are hoping for. You will get agreement, and agreement is not information.
How this is calculated
No statistics and no score. Every check is about wording, because wording is where intent shows up and intent is the only thing that decides whether a walk is worth doing.
- A named process, a place, and a time including the shift.
- No audit language — a visit read as an inspection stops being told things.
- Observations you could watch, not verdicts you would reach.
- At least one thing to count.
- Questions that are open rather than yes/no, and not leading.
Source: Imai, M. (1997), Gemba Kaizen, Ch. 2 — the five golden rules of gemba management; Rother, M. (2009), Toyota Kata, on coaching questions rather than inspection.
Check yourself
No hints. Wrong answers are explained, not softened.
During a walk you notice a jammed label printer and the picker hand-writing labels. What do you do?
Which of these belongs in the 'what I will watch' column of a Gemba plan?
A team installs a dashboard in the office showing yesterday's production figures, updated overnight. Is this visual management?
Worth remembering
Why does a Gemba walk find things a report cannot?
A report contains only what somebody decided to record. Workarounds, informal handoffs and exception paths are invisible to every system the work produces, and visible in ten minutes on the floor.
Why should you not fix things during a Gemba walk?
Fixing destroys the evidence. Straighten the jammed printer and you will never learn that it jams four times a shift, or what people do when it does.
What is the test for visual management?
Could a person walk in and tell within thirty seconds whether things are normal? If it needs a login, a report or a conversation, it is reporting rather than visual management.
Can you do this now?
Rate yourself honestly. We compare your rating with how you actually answered — the gap is more useful than either number alone.
I can explain what visual management is for and give an example that would work in my area.
I can prepare for a Gemba walk by listing what I will observe and what I will ask.
Your rating is recorded alongside your drill results. Neither alone marks the competency as met.