What is a gemba walk checklist?

A gemba walk checklist is a structured prompt for preparing, observing work where it happens, asking respectful questions, recording evidence, protecting safety and assigning follow-up without turning the visit into a blame exercise.

What should you look for during a gemba walk?

Look at actual workflow, demand, standard work, handoffs, waiting, rework, defects, information, equipment condition, safety controls and barriers reported by the people doing the work.

What questions should be asked on a gemba walk?

Ask neutral questions such as what should happen, what is happening now, what makes the work difficult, how abnormalities are recognized, what support is needed and what should be checked next.

How long should a gemba walk take?

There is no universal duration. Set a bounded scope that allows meaningful observation without disrupting operations, and schedule further visits when the process cannot be understood responsibly in one walk.

Who should join a gemba walk?

Include the process owner and people with a legitimate role in learning or removing barriers, while keeping the group small enough to work safely and avoid overwhelming frontline staff.

Is a gemba walk an audit?

Not necessarily. A learning-focused gemba walk observes and asks questions, while a formal audit tests defined criteria; keep the purpose clear and follow the required audit process when assurance is intended.

Gemba Walk Checklist: Questions, Observations and Follow-Up

A gemba walk checklist helps leaders and improvement teams observe work where it happens, learn from the people doing it and convert evidence into responsible follow-up. The goal is not a ceremonial tour or a search for someone to blame. It is to understand the current process and its barriers.

Safety rules, worker rights, privacy, customer confidentiality and site authorization remain controlling. Stop or redirect the walk if observation would interfere with hazardous work or expose restricted information. Qualified operational and safety personnel decide immediate controls; visitors should not improvise instructions beyond their competence.

Define a learning purpose

Choose one process, value stream, problem or customer outcome. A broad aim such as “inspect the factory” produces scattered notes. A focused question such as “understand why changeovers exceed the planned window” guides observation without assuming the cause.

State whether the visit is for learning, coaching, improvement, assurance or incident follow-up. Do not call it a learning walk if observations will be used for undisclosed performance evaluation. Clarify how notes will be handled and who will receive follow-up.

Review recent process information, but do not let dashboards replace direct observation. A daily production meeting agenda can identify recurring constraints worth testing at the workplace.

Copy this gemba walk checklist

GEMBA WALK CHECKLIST

PREPARE
Process / area / date / shift:
Learning question:
Host / process owner / participants:
Safety induction, PPE and access confirmed:
Privacy or recording restrictions:
Known standard / demand / recent issue:

OBSERVE AND ASK
[ ] Watch a complete work cycle where feasible
[ ] Compare expected flow with actual flow
[ ] Ask operators to explain the work in their words
[ ] Note waiting, motion, handoffs, rework and interruptions
[ ] Check how abnormalities become visible
[ ] Observe material, information and tool availability
[ ] Ask what creates risk, frustration or delay
[ ] Distinguish direct observation from interpretation
[ ] Stop and escalate immediate safety concerns

RECORD
Observation / time / location:
Expected condition / source:
Evidence or example:
Operator context:
Question or hypothesis, not yet verified:
Immediate containment, if authorized:

FOLLOW-UP
Action or experiment / owner / due date:
Required specialist review:
Decision and evidence link:
Feedback to workforce / date:
Return visit / success measure:

Adapt prompts to the site and process. A checklist should support attention, not encourage visitors to complete boxes while missing what people and conditions reveal.

Prepare with the area owner

Agree on timing, route, group size and operational constraints. Complete required induction and personal protective equipment checks. Ask which tasks cannot be interrupted and where visitors may stand. Reschedule if staffing, an incident or production conditions make the walk unsafe or unfairly disruptive.

Tell the workforce why the group is visiting and what will happen with observations. Avoid surprise photography or recording. Obtain the authorization and consent required by policy, and respect areas where customer, patient, employee or proprietary information is visible.

Bring only the relevant standard, process map and recent measures. Too much preloaded interpretation can make the group search for confirmation rather than learn.

Observe the actual workflow

Follow the movement of work, material or information from trigger to completion. Where safe and practical, watch a complete cycle and note variation across more than one example. Distinguish routine work from a demonstration staged for visitors.

Observe at a pace that lets the normal process continue. A large group clustered around one station can change travel paths, communication and cycle time. If the visit itself changes the work materially, record that limitation and arrange a less intrusive observation method.

Look for waiting, queues, excess movement, handoff delays, workarounds, repeated checking, rework and interruptions. Observe whether tools, information and materials are available at the point of need. Do not label every pause as waste; some checks, rests or buffers may be deliberate controls.

Use an equipment inspection checklist when condition assessment is the actual purpose. A gemba walk can surface a concern but does not replace competent technical inspection.

Ask respectful, neutral questions

Begin with “Please show me how this work normally happens” and “What should happen next?” Ask how people recognize a normal condition, what makes work harder and what support would help. Listen before suggesting a fix.

Avoid questions that contain accusations or preferred answers. “Why did you ignore the standard?” assumes intent; “What made the documented step difficult here?” invites context. Do not pressure employees to discuss personal, disciplinary or protected matters in front of a group.

Thank people for identifying problems. If speaking up creates immediate extra work or blame, future walks will produce polished silence rather than useful evidence.

Ask follow-up questions that reveal conditions rather than testing memory. Useful prompts include: “What information do you need before starting?”, “How do you know this item is ready?”, “What happens when the expected input is missing?” and “Who can help when the process falls outside the standard?” Give people time to demonstrate. Do not complete their explanation with management’s preferred narrative.

Notice who is not represented. Temporary staff, night-shift workers, maintainers, inspectors or downstream teams may experience a different process. One conversation is evidence about one perspective, not proof of a universal condition. Schedule targeted follow-up when the learning question depends on roles or shifts absent from the walk.

Compare standard work with reality

Identify the current approved standard and confirm that it applies to the observed product, shift or condition. Ask operators whether it is accessible, understandable and feasible. A difference can indicate noncompliance, but it can also reveal an outdated standard, missing resources or an unrecognized operating condition.

Record the exact step and context rather than writing “operator error.” Ask who owns standard changes and how temporary instructions are controlled. Do not instruct a shortcut to improve the walk’s apparent result.

For changeover-specific observation, the production line changeover checklist provides a more detailed control structure.

Protect safety and stop when necessary

Follow site rules, marked routes, equipment clearances and permit requirements. Never distract someone performing a critical task. If an immediate hazard is observed, use the site’s stop-work and escalation process and defer to qualified personnel.

Separate immediate containment from root-cause analysis. Removing a loose obstruction may control today’s exposure but does not explain why it appeared. Record who authorized action and whether production can resume.

Do not photograph guards, screens, people or incidents without permission. Safety learning does not remove privacy, investigation or evidence-control obligations.

Record facts, context and hypotheses separately

Write what was directly seen or heard, including time, location and process condition. Then capture the operator’s explanation as attributed context. Put possible causes in a separate hypothesis field until evidence supports them.

For example, “three units waited at inspection for eight minutes during the observed cycle” is an observation. “Inspection staffing caused the delay” is a hypothesis unless staffing and alternative causes were checked. This discipline prevents a brief visit from creating false certainty.

When a finding needs formal action, use a corrective action report template to document containment, cause analysis, verification and closure.

Look across flow, quality and maintenance

Observe how demand is signaled, work is prioritized and completed items move. Check where defects are detected, how nonconforming output is identified and whether rework loops are visible. Ask what information operators need but often lack.

Notice equipment condition, minor stops, temporary repairs and access to tools or spare materials. Do not diagnose machinery unless qualified. Link recurring failure evidence to the machine breakdown report template or maintenance process.

Consider upstream and downstream effects. A locally efficient workstation can create a queue or quality burden elsewhere, so avoid declaring improvement from one isolated measure.

Convert observations into responsible follow-up

At the end, summarize what the group observed and ask the area team to correct misunderstandings. Separate immediate safety or quality containment, questions needing evidence, small local actions and larger improvement work.

Assign one owner and date to each accepted action. Avoid leaving workers with an unprioritized list created by visitors. Confirm authority, resources and whether a change needs engineering, quality, safety, worker representation or change-control review.

Classify follow-up by purpose. A containment action protects the current operation; an investigation tests possible causes; an experiment evaluates a change; and a standard update formalizes an approved method. Keeping these distinct prevents a temporary workaround from becoming permanent without review. Record assumptions, boundaries and the person authorized to stop an experiment if conditions worsen.

Before leaving, agree how workers can add evidence or challenge the summary. Some effects become visible only after the observed cycle or on another shift. A controlled correction route improves accuracy and shows that participation continues beyond the visit.

Define how success will be checked at the workplace. Completion of a slide or meeting is not proof that flow, safety or quality improved.

Use recording and AI responsibly

Operational discussions may expose people, customer data, proprietary methods and safety-sensitive details. Capture only with site authorization, clear notice, appropriate consent and a defined purpose. Provide a non-recorded route where policy or circumstances require it.

For an authorized gemba debrief with visible, consented capture, Kuno can help create draft observations and follow-up actions for human verification. It does not assess safety, direct workers or approve process changes. Explore Kuno

Verify terminology, owners and observations with participants. Remove unnecessary personal information and transfer approved actions into the official improvement system.

Return, verify and close the loop

Share reviewed findings with the area in an accessible format. Explain which suggestions were accepted, deferred or declined and why. Silence after asking for frontline input damages trust and weakens future observation.

Return at the agreed time to verify the action and its effect. Check for unintended consequences, workarounds or risk shifted elsewhere. Close actions only when the defined evidence is available and the responsible owner accepts the result.

The strongest gemba habit is repeated learning: observe, ask, test, verify and communicate. The checklist is complete only when the people who contributed can see what happened next.

Turn authorized workplace debriefs into clearer draft actions. Kuno supports consented capture while operational, safety and quality owners retain every judgment, instruction and approval. See Kuno