Template

Gemba walk observation & coaching template

Facilitator-friendly interactive template to record gemba observations, use coaching prompts, capture experiments, assign owners and due dates, and track follow-up metrics.

Interactive Tool

Gemba Walk Observation & Coaching

Gemba walk observation & coaching

Use this form during a gemba walk to capture clear facts, coach for operator reflection, propose lightweight experiments, assign owners, and track follow-up so observations turn into owned improvements.

Keep entries short and evidence-based. Use the coaching prompts to help the operator reflect and propose a practical next-step experiment whenever possible.

Your name. Helps assign accountability for follow-up.
ISO-ish format helpful (e.g., 2026-08-27 09:15).
Where the observation occurred (line name, cell, area, machine ID).
Which shift or team was on duty.
Name(s) of the operator(s) engaged in the activity.
A concise, factual statement: what you saw or measured. Avoid interpretation here.
Numbers, times, counts, photos (reference), samples, timestamps, or direct quotes. Example: '4 consecutive rejects in 15 minutes; scrap weight 3.2 kg.'
OEE, cycle time, uptime, rejects, throughput, takt, etc. Not required but helpful for follow-up.
If yes, stop and secure the area before continuing. Record actions in follow-up.
Use these prompts to coach the operator toward a practical experiment.
Capture the operator's own explanation, ideas, or concerns in their words. This builds ownership.
A short, testable experiment: who will do what, what will change, how long the test runs, and what metric will indicate success. Example: 'Try a 15-min buffer change for batch start; measure rejects next 4 runs.'
Step-by-step actions for the experiment so someone else can reproduce it. Keep it minimal and time-boxed.
Name of the person accountable for executing and reporting back.
Date for the first check-in or when the experiment should begin. Use YYYY-MM-DD.
Use priority to help daily huddle triage.
1.0 10.0
Use these items to track concrete follow-through.
Be specific: metric name, how measured, and target or acceptable range.
Date when results were reviewed.
Summarize outcomes and any quantitative changes. If experiment failed, note why and next step.
What did we learn? What should change in standard work, training, maintenance, or design?
Anything else useful for the team or future review.
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.