checklist

Gemba Walk Checklist & Leader Script

An interactive, practical checklist and leader script for focused, respectful Gemba walks. Includes pre-walk checks, observable prompts for safety/quality/flow/morale, starter coaching phrases, a quick-capture issue form (owner, priority, immediate containment, follow-up), and a follow-up cadence template for reliable closure.

Interactive Tool

Gemba Walk Checklist & Leader Script

Purpose

Use this checklist to make Gemba walks structured, respectful, and action-focused. Observe facts, coach with curiosity, capture any immediate issues, and assign clear ownership and a follow-up cadence so improvements stick.

Leader script (short)

Opening: 'Hi — we’re doing a quick walk to understand how the process is working today. I’m here to learn and to help remove obstacles. Can you show me how this step is done?'

While observing (use coaching phrases):

  • Ask a question: 'Can you walk me through what you're seeing here?'
  • Praise what works: 'I noticed X working well — tell me more about that.'
  • Probe for data: 'What did you expect to happen? What actually happened?'
  • Offer support: 'What would help you do this easier or safer?'

Closing: 'Thank you. I’ll capture what we saw and follow up on the immediate items we agreed on.'

How to use this form

Complete the pre-walk readiness checks, score quick tone checks for safety/quality/flow/morale, record observable facts (not opinions), and if you identify an issue, use the quick-capture fields to assign owner, priority, immediate containment, and follow-up date.

Confirm you have a clear purpose, permission to observe, and a 15–30 minute time budget.
Where will you walk (e.g., Packaging Line 2).
Use a clear format (e.g., 2026-08-28 09:15).
Names and roles (brief).
Primary theme for this walk.
Quick tone-check on safety observed during the walk.
1.0 10.0
Quick tone-check on quality observed during the walk.
1.0 10.0
Observe flow, handoffs, and any bottlenecks.
1.0 10.0
Note team tone, engagement, and signs of stress.
1.0 10.0
Record observable facts. Avoid interpretation or blame. Example: 'Machine X stopped 2 times in 30 min; operator performed workaround Y.'
Which approach did you use to engage the team?
If yes, complete the quick-capture fields below. If multiple issues exist, submit separate entries or list them clearly in the description.
One short sentence describing the problem (observable fact).
Who will own follow-up?
Choose the priority for follow-up.
What was done now to make the situation safe or stop the immediate impact?
e.g., same day, 48 hours, next weekly huddle. Use a date if you prefer.
Who will verify the issue is closed?
How frequently should progress be reviewed?
What will you (the leader) commit to do, and when will you check back?
One-sentence reflection: what was learned or the next step?
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Sign In to Save Create an Account
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.