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.
{
"Title": "Gemba Walk Observation & Coaching",
"IntroductionHtml": " ",
"SubmitLabel": "Save observation",
"SuccessMessage": "Observation saved. You can return later to update follow-up and results.",
"DataType": "GembaObservation",
"SchemaVersion": 1,
"Fields": [
{
"Key": "observer_name",
"Label": "Observer name",
"FieldType": "text",
"Required": true,
"HelpText": "Your name. Helps assign accountability for follow-up."
},
{
"Key": "date_time",
"Label": "Date and time",
"FieldType": "text",
"Required": true,
"HelpText": "ISO-ish format helpful (e.g., 2026-08-27 09:15)."
},
{
"Key": "location",
"Label": "Location / line / cell",
"FieldType": "text",
"Required": true,
"HelpText": "Where the observation occurred (line name, cell, area, machine ID)."
},
{
"Key": "shift",
"Label": "Shift / team",
"FieldType": "text",
"HelpText": "Which shift or team was on duty."
},
{
"Key": "operator_name",
"Label": "Operator(s) observed",
"FieldType": "text",
"HelpText": "Name(s) of the operator(s) engaged in the activity."
},
{
"Key": "observation_summary",
"Label": "Observation — short summary",
"FieldType": "textarea",
"Required": true,
"HelpText": "A concise, factual statement: what you saw or measured. Avoid interpretation here."
},
{
"Key": "facts_and_evidence",
"Label": "Facts / evidence (what you measured or observed)",
"FieldType": "textarea",
"HelpText": "Numbers, times, counts, photos (reference), samples, timestamps, or direct quotes. Example: '4 consecutive rejects in 15 minutes; scrap weight 3.2 kg.'"
},
{
"Key": "related_metrics",
"Label": "Related metrics to note",
"FieldType": "textarea",
"HelpText": "OEE, cycle time, uptime, rejects, throughput, takt, etc. Not required but helpful for follow-up."
},
{
"Key": "safety_hazard",
"Label": "Is there an immediate safety or compliance hazard?",
"FieldType": "yesno",
"HelpText": "If yes, stop and secure the area before continuing. Record actions in follow-up."
},
{
"Key": "coaching_prompts_used",
"Label": "Coaching questions used (select all that applied)",
"FieldType": "checkbox",
"Options": [
{ "Value": "what_happened", "Label": "What happened?" },
{ "Value": "why_did_it_happen", "Label": "Why do you think that happened?" },
{ "Value": "what_have_you_tried", "Label": "What did you try already?" },
{ "Value": "what_would_you_try", "Label": "What would you try next?" },
{ "Value": "what_support_needed", "Label": "What support or resources do you need?" },
{ "Value": "how_will_we_check", "Label": "How will we know the experiment worked?" }
],
"HelpText": "Use these prompts to coach the operator toward a practical experiment."
},
{
"Key": "operator_reflection",
"Label": "Operator reflection / response",
"FieldType": "textarea",
"HelpText": "Capture the operator's own explanation, ideas, or concerns in their words. This builds ownership."
},
{
"Key": "improvement_idea",
"Label": "Improvement idea or proposed experiment",
"FieldType": "textarea",
"Required": true,
"HelpText": "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.'"
},
{
"Key": "experiment_description",
"Label": "Experiment details (steps)",
"FieldType": "textarea",
"HelpText": "Step-by-step actions for the experiment so someone else can reproduce it. Keep it minimal and time-boxed."
},
{
"Key": "owner",
"Label": "Owner (who will run the experiment / follow-up)",
"FieldType": "text",
"Required": true,
"HelpText": "Name of the person accountable for executing and reporting back."
},
{
"Key": "due_date",
"Label": "Due date for experiment start / first check",
"FieldType": "text",
"HelpText": "Date for the first check-in or when the experiment should begin. Use YYYY-MM-DD."
},
{
"Key": "priority",
"Label": "Priority (1 low — 5 high)",
"FieldType": "scale",
"Min": 1,
"Max": 5,
"HelpText": "Use priority to help daily huddle triage."
},
{
"Key": "follow_up_checklist",
"Label": "Follow-up checklist",
"FieldType": "checkbox",
"Options": [
{ "Value": "owner_contacted", "Label": "Owner contacted and briefed" },
{ "Value": "action_plan_created", "Label": "Action plan created" },
{ "Value": "baseline_collected", "Label": "Baseline metrics collected" },
{ "Value": "experiment_started", "Label": "Experiment started" },
{ "Value": "results_collected", "Label": "Results collected and logged" },
{ "Value": "results_reviewed", "Label": "Results reviewed in huddle" }
],
"HelpText": "Use these items to track concrete follow-through."
},
{
"Key": "metrics_to_watch",
"Label": "Metrics to watch (how we'll measure success)",
"FieldType": "textarea",
"HelpText": "Be specific: metric name, how measured, and target or acceptable range."
},
{
"Key": "follow_up_date",
"Label": "Follow-up / result date",
"FieldType": "text",
"HelpText": "Date when results were reviewed."
},
{
"Key": "follow_up_result",
"Label": "Follow-up result / outcome",
"FieldType": "textarea",
"HelpText": "Summarize outcomes and any quantitative changes. If experiment failed, note why and next step."
},
{
"Key": "lessons_learned",
"Label": "Lessons learned / next steps",
"FieldType": "textarea",
"HelpText": "What did we learn? What should change in standard work, training, maintenance, or design?"
},
{
"Key": "additional_notes",
"Label": "Additional notes or context",
"FieldType": "textarea",
"HelpText": "Anything else useful for the team or future review."
}
]
}
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.
Discussion
Comments and conversation will live here.