3. What Is a Gemba Walk?
A Gemba Walk means going to the real place where work happens, observing the process directly, and identifying waste, risk, and improvement opportunities.
Why we do this
To make problems visible at the source, build shared understanding, and fix root causes before they become larger quality, safety, or delivery issues.
How to set your site up for Gemba Walks
- Divide your site into 5 distinct Gemba Zones and ensure they are setup in Org Setup (for example: "1- Factory", "2- Warehouse").
- Assign each Gemba Zone a small team, preferably of differing seniority levels.
- Assign each Gemba Zone a day of the week (Monday to Friday).
- Optionally assign a reminder time and up to 5 team members so automated reminders can be sent.
How to run one
- Pick the area, route, and objective before starting.
- Observe process flow and safety conditions; ask open questions.
- Create tasks in Momentum for findings with campaign Gemba Walk Action.
- Use owner, status, progress, due date, and photos to track closure.
5. 5S
5S improves workplace organisation and consistency: Sort, Set in Order, Shine, Standardise, Sustain.
Why we do this
To reduce wasted motion and searching time, improve safety, and make standard work easier to sustain.
In Momentum: create 5S Action tasks, set the 5S step, and track progress to completion.
6. Kaizen
Kaizen is continuous, incremental improvement led by the people doing the work.
Why we do this
To create continuous improvement habits, capture frontline ideas, and improve results through many small wins.
In Momentum: use Kaizen Blitz tasks and update Kaizen Step to show where each improvement is in the cycle.
7. Andon
Andon is a visual/audio alert system that surfaces issues immediately so teams can respond quickly.
Why we do this
To escalate abnormal conditions quickly, reduce delay to response, and protect safety, quality, and delivery in real time.
In Momentum: log Andon tasks with Andon Type and Alert Types, assign owners, and monitor response/closure times.
8. Poka Yoke
Poka Yoke is mistake-proofing through design controls and warning mechanisms.
Why we do this
To prevent mistakes before they happen, reduce rework, and design process controls that make the right action the easiest action.
In Momentum: create Poka Yoke tasks, set method, assign ownership, and track evidence through status, progress, and photos.