GWL—Gemba Works Lab

kaizen in practice

Gemba Walk Checklist: What Leaders Should Actually Look For

D-KAI-09  |  First published 2026-08-12  |  Revised 2026-08-12  |  Primary sources: 3

Disclosure: Gemba Works Lab is supported by advertising. This page contains no affiliate links; if any are added in the future they will be clearly marked (per the FTC Endorsement Guides).

A gemba walk without a checklist tends to drift toward whatever problem is loudest that day — the jammed conveyor, the operator who flagged them at the door, the pile of red tags nobody has looked at. That is not useless, but it is not repeatable, and it is not something a new supervisor can pick up and run the same way twice. A written checklist fixes that: it turns an informal stroll into a standard routine that produces the same kind of information walk after walk, shift after shift, whoever is holding the clipboard.

What a gemba walk checklist actually is

Gemba (現場) simply means "the actual place" — for a manufacturer, the shop floor rather than the conference room. A gemba walk checklist is the form a team leader, supervisor, or plant manager carries on that walk: a short list of questions and inspection points used to observe the work as it is actually happening, talk to the people doing it, and record what needs follow-up. As a practical guide from Tervene, a firm that builds shop-floor management software, puts it, the checklist exists to "generate improvement opportunities and to proactively identify issues before they impact production" — safety, quality, and productivity issues alike, caught while they are still small (source: Tervene, "Gemba Walk Checklists & Questions").

Jim Womack, the researcher who helped introduce the term "lean" to Western manufacturing through MIT's International Motor Vehicle Program, has made a useful distinction about when a checklist helps and when it gets in the way. Responding to a reader question in a 2011 Lean Enterprise Institute column, Womack said a detailed checklist is most useful when you are training managers who are new to gemba walking, or when the walk has "a more technical focus." For an experienced walker doing a first, big-picture pass through an unfamiliar area, he prefers a handful of open questions — what is this process for, is it achieving that purpose, how are the people who touch it involved in improving it — over a rigid form (source: Lean Enterprise Institute, "Gemba Walk Checklist," Jim Womack, 2011). Both are legitimate uses of a gemba walk. Most small manufacturers should start with the structured version, because it is what makes the practice transferable from one supervisor to the next.

The SQDCP+5S structure

Rather than inventing categories from scratch, most working checklists borrow the same short list of buckets used on shop-floor performance boards: Safety, Quality, Delivery, Cost, People (SQDCP), plus a direct check of 5S standards (Sort, Set in Order, Shine, Standardize, Sustain). Tervene's guide describes gemba walk checklists built this way as connecting "shop-floor observations directly to strategic KPIs," structured inside a repeatable Plan-Do-Check-Act cycle rather than a free-form notes page (source: Tervene, "Gemba Walk Checklists & Questions").

The 5S check deserves its own line rather than folding into "Quality," because it is the fastest thing a walker can verify with their eyes alone: tools back in their shadow-boarded spot, aisles free of obstruction, labels current, nothing sitting where it does not belong. SafetyCulture's manufacturing-focused gemba templates treat 5S and safety compliance as a joint checkpoint for exactly this reason — both are visible in seconds and both predict bigger problems if neglected (source: SafetyCulture, "Gemba Walk Checklist for Manufacturing Safety & 5S").

Different checklists for different roles

A single generic checklist used by everyone from team leader to plant director tends to satisfy no one — too shallow for the person closest to the line, too detailed for the person who needs the ten-second version. Tervene's guide lays out role-specific question sets, and the pattern is worth copying directly:

Source: Tervene, "Gemba Walk Checklists & Questions" (role-based question examples).

Notice the shape of the escalation: a team leader's questions are almost all about right now, on this line. An owner's questions are almost all about whether the system underneath the line is sound. Both walks use the same SQDCP+5S skeleton — they just ask it at a different altitude.

Gemba walk checklist vs. kaizen event checklist

It is easy to confuse this checklist with our 5-day kaizen event checklist, since both are printable forms used on the shop floor. They solve different problems:

• The gemba walk checklist is a routine you run daily or weekly, indefinitely, as part of ordinary supervision. It is short (15–25 minutes), covers the whole area at a glance, and is meant to catch small problems before they compound.
• The kaizen event checklist runs once, for one intensive week, aimed at a single predefined target — a bottleneck, a changeover, a chronic defect. It is long, detailed, and covers two weeks of preparation plus five days of execution plus a 30-day follow-up.

A useful way to think about the relationship: gemba walks are how you notice that a kaizen event is needed, and how you check, months later, that the event's gains actually stuck. A shop that only ever runs kaizen events without routine gemba walks in between is flying blind between events; a shop that only does gemba walks without ever running a focused event tends to accumulate a backlog of problems that are individually too big for a 20-minute walk to fix.

Building your first checklist

For a shop under roughly 200 people with no dedicated continuous-improvement staff, the fastest path to a usable checklist is:

1. Start from the SQDCP+5S skeleton above and cut it down to 2–3 questions per category — no more than 12–15 questions total. Tervene's guidance is blunt on this point: the walk should complete in 15 to 25 minutes, and a longer list "can overwhelm leaders, making it challenging to identify all issues effectively" (source: Tervene, "Gemba Walk Checklists & Questions").
2. Write questions that point toward a fix, not a verdict. "Is the worker following the standard?" invites a yes/no that ends the conversation. "What's making this step harder than it needs to be today?" invites the information you actually came for.
3. Make it a shared document, not a management tool imposed from above. Both Womack and Tervene converge on this: a gemba walk is not an inspection of the workforce, it is a way of seeing the process together. A checklist built without frontline input, or used to catch people making mistakes, will get worked around within a month.
4. Put a name and a date on every finding, and bring the previous walk's open items to the next one. A checklist with no follow-up loop is a piece of paper, not a management system — this is exactly the failure mode our companion article on why kaizen gains disappear after 12 months documents at scale.

None of this requires software, though digital checklist tools do make the follow-up loop easier to enforce — a paper form is easy to lose, a digital one is easy to route to the right owner automatically. Either way, the tool matters far less than the discipline of actually walking, actually asking, and actually closing the loop on what you find.

references

1. Tervene — Gemba Walk Checklists & Questions: A Practical Guide
2. Lean Enterprise Institute — Gemba Walk Checklist (Jim Womack, 2011)
3. SafetyCulture — Gemba Walk Checklist for Manufacturing Safety & 5S

Last updated: 2026-08-12 | Primary sources referenced: 3 | Role-based question examples are adapted from cited sources; this article does not report unverified customer results.