Gemba walk checklist: questions, form and routines

A gemba walk checklist is a short plan for going to the place where work happens, seeing the process, and asking useful questions. It covers what to prepare, what to look for, and what to do afterwards.

This guide gives a before, during and after checklist and grouped question sets. It also covers a simple gemba walk form and the mistakes that often spoil a walk. Everything is written in the text so you can copy it into your own form.

Key takeaways

A gemba walk is about learning from the work, not inspecting people.

Prepare a purpose, observe in silence first, then ask open questions.

Group your questions by flow, standard work, safety, quality, visual management and people.

Record follow-ups with an owner and due date, or the walk changes nothing.

Do not try to solve problems on the spot.

What is a gemba walk?

A gemba walk is a planned visit by a leader to the place where value is created. The aim is to observe the work and learn from the people doing it. Gemba is Japanese for the actual place.

The idea of "go and see" is tied to Taiichi Ohno, who led the development of the Toyota Production System. He is often credited with urging managers to watch the work directly. See the gemba walk method page for more.

Gemba walks often happen on a shop floor, but the same idea works in warehouses, hospitals and offices.

Why do a gemba walk? Purpose and what you can expect to see

The purpose of a gemba walk is to see how work really runs, compared with how reports and dashboards say it runs. It builds a shared picture of the process.

At the gemba you can expect to see the normal flow of work, and also the workarounds, waiting, searching and rework that reports hide. Those are the eight wastes in action.

You will also see how people respond to problems. Whether they call for help, hide a defect or fix it without telling anyone shows how the system treats problems.

The before, during and after checklist

Before the walk, pick one clear purpose, such as flow of orders or safety. Choose the area, tell the team you are coming, and review any recent data for it.

Before the walk, also agree the time and keep it short. Thirty to sixty minutes is typical, and it works better to visit one area well than five areas badly.

During the walk, start by watching without speaking. Follow the work, not the people, and note what you see in plain words.

During the walk, ask open questions and listen. Thank people for their time, and do not give instructions.

After the walk, write down your observations the same day. List the follow-ups, give each an owner and a due date, and go back to tell the team what happened.

Gemba walk questions: flow and waiting

These gemba walk questions help you spot inefficiencies in how work moves.

Flow: Where does work wait, and for how long?

Flow: What happens when the next step is not ready to take the work?

Flow: How much work is in progress here, and who decided that amount?

Flow: What do you look for or walk to get that you do not have at hand?

Flow: What is the longest delay you see in a normal day?

Gemba walk questions: standard work and safety

Standard work: Can I see the standard for this task, and does it match what you do?

Standard work: How was the standard created, and who can change it?

Standard work: What do you do when the standard does not work?

Safety: What could hurt someone in this area today?

Safety: Which tasks need extra care, and how is that made clear?

Safety: What near misses have happened recently, and what changed afterwards?

A safety gemba walk uses the safety questions as its main purpose. Keep the other questions for another visit, so the focus stays sharp. Read more on standard work.

Gemba walk questions: quality, visual management, people

Quality: How do you know the work you just did is good?

Quality: What defects or errors are most common here, and where are they caught?

Quality: What do you do when you find a problem?

Visual management: Can I tell at a glance whether things are on plan or off plan?

Visual management: Who reads the board, and how often is it updated?

People and improvement: What is one thing that makes your work harder?

People and improvement: What improvement have you made or suggested recently?

People and improvement: What help or training would make your job easier?

Boards and charts are part of visual management, which supports a daily management system.

A simple gemba walk form layout

A gemba walk form is a one-page sheet with a few labeled boxes. Keep it light, so it does not turn the walk into a survey.

At the top, put the date, the walker's name and the area visited. Beneath that, write the purpose of the walk in one line.

The middle of the form holds three boxes: observations, questions asked and what people said. Use plain words and avoid judgments.

At the bottom, add a table of follow-ups with four columns: action, owner, due date and status. Review the table at the start of the next walk.

Paper works well for this. If you want to track actions across many areas, see daily management software.

Leader routines and how often to walk

Gemba walks work well as a regular routine, not an occasional event. A weekly walk of the same area, with a different purpose each time, builds trust and shows change.

Frontline leaders often walk daily as part of their normal rounds. Senior leaders may go weekly or monthly, ideally with the area's supervisor alongside.

Put the walks in the calendar, and treat them as fixed. The routine is part of daily management and wider lean management.

Walk areas where you do not normally go, as well. Pair the walk with a 5S audit in the same area if you want a structured look at order and cleanliness.

Common gemba walk mistakes

The biggest mistake is walking to inspect or blame. If people feel judged, they show you what you want to see and hide the rest.

The second is solving problems on the spot. A leader who gives instant fixes takes the problem away from the team and misses the root cause.

A third is walking without a purpose, so the visit becomes a general tour. A fourth is not following up, which teaches people that raising problems is pointless.

Instead, record the problem, ask why it happens, and take it to a proper analysis. See root cause examples for how to go deeper.

Frequently asked questions