Gemba Walk Observation & Improvement Capture Card — Facilitator Template
A practical, facilitator-friendly gemba observation card and a weekly leadership roll-up. Use this card to capture focused observations, coach on-the-floor problem solving, agree on lightweight experiments, assign ownership, and ensure reliable follow-through so gemba becomes learning and improvement—not a checkbox.
Purpose
Use this single-sheet observation card during gemba walks to capture what you saw, the estimated impact, a small experiment to test, who owns the follow-up, and when to review results. Designed for quick coaching conversations, immediate actions, and reliable hand-off into daily management and weekly leadership review.
How to use this card (3-minute coaching loop)
- Ask permission: "Can I watch and ask a few questions for improvement?"
- Observe quietly and note the specific behavior, condition, or metric (one observation per card).
- Estimate the impact and urgency—use the score to help prioritize.
- Coach briefly: Ask operator what they think is happening and what would be a sensible first experiment.
- Capture the suggested experiment, assign an owner, set a short follow-up date, and agree on what success looks like.
- If an immediate safety or quality fix is required, take or authorize immediate action and record it as Immediate Action.
- Turn the card into a visible follow-up item (board, digital tracker, or weekly roll-up).
Gemba Observation & Improvement Capture Card
Observation (be specific)
Describe the observable fact. Avoid blame and opinions. Write what you saw, heard, or measured.
Example: Machine #7 stops 2–3 times per shift; operator takes ~8 minutes to clear each stop.
Location / Line / Shift / Date / Observer
Location: ________ | Line: ________ | Shift: ________ | Date: ________ | Observer: ________
Impact Estimate
Quick size of the opportunity. Select a simple score and a short rationale.
- Score (1–5) — 1 = low / local; 5 = high / recurring impact on safety, quality, throughput or cost.
- Brief rationale: e.g., "~3 stops/day = ~24 min lost/day; potential scrap risk when restart."
Suggested Experiment (small, time-boxed)
Write a clear, testable experiment you can try within a shift or a few days. Keep it small and measurable.
Format: Hypothesis → Test → Measure → Duration.
Example: If we add a 30-sec pre-start checklist for Machine #7, then stops caused by missing coolant checks will decrease. Measure: number of stops per shift for 5 shifts.
Immediate Action (if any)
Record any action taken during the walk (who did it and when). Example: Replaced loose hose (Operator J. — done now).
Owner (who will run the experiment / follow-up)
Assign a single owner. If it's the observer, note that; otherwise confirm with the owner during the gemba conversation.
Follow-up Date
Pick a near-term date (typically within 1–7 days for small experiments). Commit to reviewing the result with the operator and the observer.
Success Criteria / What to Measure
Define the simple metric you will use to decide if the experiment helped. Example: Stops reduced to ≤1/shift for 5 consecutive shifts OR average downtime reduced to ≤2 min/stop.
Photo / Sketch
Attach a photo or sketch that makes the observation clear (placement, condition, part number, label, etc.).
Follow-up Notes (short)
Record outcomes, lessons, next steps, and whether the experiment is scaled, revised, or abandoned.
Weekly Leadership Roll-Up (one-page summary)
Use this roll-up to brief leaders and keep sight of ownership and progress. Populate rows from completed cards and active experiments.
| # | Observation | Impact (1–5) | Experiment | Owner | Follow-up Date | Status | Outcome / Next Step |
|---|---|---|---|---|---|---|---|
| 1 | Machine #7 frequent stops | 4 | Pre-start checklist for 5 shifts | Line Tech – J. | 2026-09-03 | In progress | Results due / leader to review |
| 2 | Packaging misfeeds at Lane B | 3 | Adjust guide and measure scrap for 3 shifts | Supervisor – R. | 2026-09-02 | Done | Scrap reduced 60% → standardize change |
Weekly leadership prompts: Which experiments removed blockers? Which need escalation? What coaching or capability support does the owner need? Which items should become a formal improvement project?
Coaching prompts — short scripts to build capability
- "What did you expect to happen?" (surface mental model)
- "What do you think is causing that?" (invite operator diagnosis)
- "What small thing could we try now to see if that makes a difference?" (nudge toward experiments)
- "Who should own trying that? When can we check?" (make ownership explicit)
Common pitfalls & how to avoid them
- Checkbox gemba: Don't visit without a coaching conversation and an agreed follow-up owner.
- Too big experiments: Start with small, time-boxed tests to learn fast.
- No measurement: Define a simple metric so you can see whether the experiment helped.
- No visible follow-through: Put cards on a visible board or add to the weekly roll-up so leadership can support and escalate.
Example (filled card, condensed)
Observation: Operator needed to stop line to fix label jam (Lane C) — ~12 min/occurrence.
Impact: Score 3 — delays affect packout and OTD for this SKU.
Experiment: Add a guide shim + 3-shift trial; measure jams/shift.
Immediate Action: Temporary shim installed now by Tech L.
Owner: Tech L. Follow-up: 3 shifts from now.
Success: jams ≤1/shift for 3 shifts → standardize.
Suggested ways to integrate with THE capabilities
- Turn the card into an interactive form so observations are saved, searchable, and reported automatically.
- Feed weekly roll-ups into a simple dashboard to show trends by line, owner, impact score, and closure rate.
Keep the card visible, keep experiments small, and always finish the coaching loop with a follow-up. Gemba is how we learn about work — not how we check boxes.
Discussion
Comments and conversation will live here.