Gemba Walk Template: What to Record and How to Follow Up

Disclosure: M365.FM host Mirko Peters works at iFAKT GmbH. This page describes the company factually; paid partnerships and links are labelled as advertising.

By Mirko Peters · 2026-11-11

A gemba walk template needs few fields: focus, facts, actions, owners and dates. See what to record, how to write notes and how to track follow-up actions.

A gemba walk template is a one-page form that records what you saw on a walk and what will happen next. It needs only a few fields: the focus, the facts you observed, and an action log with owners and due dates. This article is for continuous improvement managers who want to capture notes in a clear structure and make sure the follow-up actually happens. Gemba is Japanese for "actual place", the place where the work is done.

Key points

• A good gemba walk template has three parts: a header with the focus, a list of observations written as facts, and an action log with owner, due date and status.
• Write observations as facts with numbers, such as counts and times. Leave out opinions and personal names, because notes that blame people stop people from speaking.
• Every problem you decide to fix becomes one action with one owner and one due date. Actions without an owner and a date are wishes.
• Review the open actions at the start of every walk. This is the follow-up that makes people believe a walk leads to change.
• Track a few numbers for the action list, such as closure rate and age of open actions, so you can see whether walks produce results.

What a gemba walk template is, and what it is not

A template does two jobs. First, it helps you capture observations while the gemba walk is fresh, so you do not rely on memory. Second, it turns observations into actions that somebody owns. If a form does only the first job, it becomes an archive nobody reads.

A template is not an inspection form. It does not score people or areas, and it should not feel like an audit. The Lean Enterprise Institute's lexicon entry on gemba describes the walk as a way for leaders to understand current conditions before they act. Its article How to go to the gemba warns against prescribing from a distance and against using tools for their own sake.

There is also a lesson in how to build the form. Jim Womack writes in Gemba walk checklist that if you need a checklist you should develop one, and that its development should be a shared task. The same applies here. Start with the fields below, try them on two walks and ask the team what to change.

What to record on every walk

Keep the form to one page. These fields are enough for most plants.

Header

• Date, area or line, and the people on the walk
• The focus question, for example "Why does final assembly wait for material?"
• Start and end time

Observations

• Station or process step
• What you saw, as a fact with a number (count, time, distance)
• What you heard, in the words of the team, without names
• The open-ended questions you asked, so you can see which ones worked

Issue type

• A simple tag such as flow, quality, safety, people or equipment. Tags let you count patterns across walks.

Action log

• What will be done, in one sentence
• Owner, who agrees to it
• Due date
• Status: open, done or dropped
• Result: checked on the next walk

What went well

• One line. Recording good practice builds engagement and gives you something to copy elsewhere.

Resist the urge to add more fields. A long form pushes people to tick boxes instead of watching the work.

How to write good gemba walk notes

Good gemba walk notes are specific and neutral. They describe what happened and leave the judgement to the team discussion afterwards.

Compare these pairs:

• Weak: "Operators are slow at the packing station." Better: "Packing station 3 made 41 packs in 30 minutes. The packer left the station twice to fetch cartons."
• Weak: "Poor housekeeping." Better: "Three tools were missing from the shadow board at the drilling cell."
• Weak: "Supervisor ignores the problem." Better: "The same jam was reported on Monday and Wednesday. No action was on the board."

The better notes can be checked. Another person can count the packs or look at the shadow board. That makes follow-up fair, because the team argues about facts and not about opinions.

Two more habits help. Capture observations during the walk, not hours later, because details fade. A small notebook or a printed template on a clipboard works well. And protect people. Womack describes in his introduction to Gemba Walks that he kept promises of confidentiality to the organisations that hosted him. Treat your notes the same way: write about the process, and share names only where a person has agreed to own an action.

Adapting the form to your focus

Keep one core form and change only the focus line. For a flow walk on the shop floor, add a field for waiting time at each station. For a walk on quality and safety, add the standard you are checking, and record where the production floor differs from it. For a walk linked to 5S, a method for organising the workplace, note whether tools and material have a defined place.

Using the same header and the same action log on every walk lets you standardize your records across areas. This structured approach has a practical benefit: you can compare walks, see where problems repeat and spot opportunities for improvement that no single walk would show. Ask team leaders and other frontline staff to help fill in the form from time to time. It builds employee engagement, and they notice things that visitors miss.

Many actions will be small, close to the work and quick to test. Lean practice calls such a change a kaizen, a small improvement made by the people who run the process. Small changes add up to higher productivity, as long as somebody tracks them.

How to follow up: from observation to action tracking

Follow-up is where most walk programmes fail. The walk is interesting, the notes are tidy, and then nothing happens. A simple routine prevents this.

1. Agree actions at the end of the walk. Sit down for 10 minutes with the area leader. Pick the observations worth acting on. Not every observation needs an action.
2. Write each action as a task. One sentence, one owner, one due date. Use a verb: "Test a carton buffer at station 3 for one week."
3. Share the list within a day. Send it to the people who own actions and post it on the area board.
4. Review open items at the start of the next walk. Before you look at anything new, check the old actions. Ask what was tried and what was learned.
5. Close or drop actions on purpose. Mark an action done only after you see the result on the floor. Drop an action openly when circumstances change, and note why.
6. Look for patterns. After a month, count the issue types. If five of ten issues are about material flow, that is your improvement theme.

Assigning an owner is the step people skip most. Choose an owner who can influence the cause, often a team leader or a supervisor, and ask whether they accept the task. The owner may ask the team for help, and that is the point: the people close to the work solve the problem.

Example: one month of action tracking

This is an illustrative example with made-up numbers. A continuous improvement manager runs one walk a week for a month and keeps one action log.

• Walks: 4
• Actions raised over the month: 12
• Actions closed (result checked on the floor): 9
• Actions still open: 3, with ages of 10, 17 and 24 days

She calculates two simple numbers:

• Closure rate: 9 closed ÷ 12 raised = 75 percent.
• Average age of open actions: (10 + 17 + 24) ÷ 3 = 51 ÷ 3 = 17 days.

She also tags the 12 actions by issue type: 6 flow, 3 quality, 2 safety and 1 equipment. Half of the actions deal with flow. At the review she suggests that the next walks focus on material flow, and she asks the owner of the 24-day action what is blocking it. The owner needs a decision about a storage area, so she takes that to the plant manager.

The numbers are not a target to hit. They are a prompt for conversation: why is one action 24 days old, and what would help?

Common mistakes

• Making the form too long. More fields mean more ticking and less looking.
• Writing opinions instead of facts. "Messy" or "slow" cannot be checked and invites argument.
• Naming and blaming. Notes with names stop people from talking openly.
• Leaving actions without an owner or a date. They will not be done.
• Following up only with the manager. Share the list with the team, or they will think nothing happened.
• Counting actions as success. Twenty actions closed on paper mean little if the floor looks the same. Check the result.

How software can help

A shared spreadsheet or task board is enough for the action log. Software becomes useful when you want to see whether a change moved the numbers. iFAKT's Polaris Analyzer is a module of the Polaris production software with KPI dashboards across all modules that compare planned and actual values in production. Used next to your action log, such a dashboard can show whether the line behaves differently after a fix. The walk and the conversation stay the main source of insight.

Next step

Build your gemba walk template on one page this week: a header, a list of facts and an action log with owner, date and status. Use it on your next walk, and log each result as part of your continuous improvement routine.