Gemba-walk pocket guide for execs
Five ways a gemba walk goes wrong and the questions to ask so people still talk to you next week - with the full pre-walk checklist.
Verified practitioner
A gemba walk is a leadership routine, not a plant tour. This guide exists because the walk fails in predictable ways - an executive shows up, observes for ninety seconds, issues an instruction, and from then on the floor performs for visits instead of working for customers.
The full checklist is printed on this page below, free to read and use. The download adds the pocket PDF, the five failure modes in detail and the question bank - the version you can actually carry onto the floor.
- ✓The one-page pre-walk checklist, printed and pocket-sized
- ✓Five failure modes - solution-jumping, audit mode, delegation, theme overload, no follow-through - and the counter-move for each
- ✓A question bank: process questions that open people up instead of shutting them down
- ✓The after-the-walk routine: where observations go so they turn into A3s and standards, not good intentions
- ✓An office/service variant for walks where the gemba is a workflow, not a line
Many of the people who share here still work in industry, so they publish without a name. We verify every maker and handle the payout - your support reaches them directly, without exposing who they are.
More from the library
Got a tool your teams swear by? Add it to the library.
Set your own price and get paid on every download. Publish under your name, stay anonymous, or release it under the Lean Competence banner - your call.
The checklist · in full
Read it here. The PDF is just the pocket version.
A gemba walk is a leadership routine for understanding real work before deciding about it. The checklist below is the whole method. Use it as is, today. The download adds the five failure modes in detail and a larger question bank.
1. Before the walk
Ten minutes of preparation decide whether this is a routine or a tour.
- □ Pick ONE theme: a process step, a deviation, a standard. Three themes are none.
- □ Tell the area you are coming and why. Surprise visits produce theatre, not truth.
- □ Block the slot like a customer escalation. A routine that yields to the calendar is not a routine.
- □ Read the standard for the step you will watch. You are looking for the gap between standard and reality.
- □ Decide, in advance, to fix nothing today. Write it at the top of your notes if it helps.
2. During the walk
Follow the actual work, not the org chart. Ask about the process, never about blame.
- □ Watch one full cycle of the work before saying anything.
- □ Note waits, searches, rework, workarounds, double handling: the work the product never asked for.
- □ Ask: "What should happen here, and what actually happens?"
- □ Ask: "What is stopping you from doing good work today?"
- □ Ask: "When did that last happen, and what did you do then?"
- □ When you hear a problem, ask who owns it, not who caused it.
- □ If you feel an instruction coming, write it down instead of saying it.
3. After the walk
This is where most walks die. Observations without follow-through train people to stay silent.
- □ Within a day: sort observations into "needs a standard", "needs an A3", "needs a decision".
- □ Pick at most two items and name an owner for each, in your daily management, not in a side channel.
- □ Close the loop with the people you talked to: what you took away, what happens next.
- □ Put the next walk in the calendar before you forget why.
When the checklist is not enough
Walks surface problems; they don't solve them. If observations keep piling up without an A3 routine or daily management to land in, the gap is the leadership system, and that is a mandate, not a template. Post a brief and we'll match a senior practitioner who has built that system before.
One email,
every other Friday.
What our practitioners are seeing on real shop floors, plus the latest episode and the next event. No marketing, no recycled lean LinkedIn posts.