HOW TO MAKE

A SUCCESSFUL
GEMBA WALK
IN 8 STEPS

KAIZEN MADE EASY

1️⃣Prepare the Team
Inform the team beforehand about the
Gemba Walk

Do
+Give earlier notice to reduce anxiety
+Explain the purpose of the Gemba Walk
+Create an open environment for everyone

Don’t
-Include ops team only
-Make it a fault-finding mission
-Evaluate team performance during the walk

KAIZEN MADE EASY

2️⃣Have a Plan
Have a defined plan for the walk tied
to specific goals.
If you want to talk about how equipment
downtime is affecting your productivity, do a
walk focusing on maintenance processes.

Do
+Identify critical areas
+Laser focus on your goals
+Create a list of concerns to address

Don’t
-Overlook the activity schedule
-Waste time on irrelevant matters
-Underuse data collection and recording

KAIZEN MADE EASY

3️⃣Stream
Follow the Value

Observe how process works, from start to

finish.
If you want to find gaps in your inbound activities, go for
a walk covering all the processes from unloading to
stow.

Do
+Track waste habits
+Observe your workflow
+Pay attention to task transitions

Don’t
-Ignore some types of waste
-Overlook transitions from one step to the next
-Focus on critical areas only, while ignoring the
whole process

KAIZEN MADE EASY

4️⃣notBlame the Process,
People
Understand the process flow. Don’t judge
people performance.
If you’re improving a data entry process, scout for
software improvements rather than find employee
faults.

Do
+Track waste habits
+Observe your workflow
+Pay attention to task transitions

Don’t
-Ignore some types of waste
-Overlook transitions from one step to the next
-Focus on critical areas only, while ignoring the
whole process

KAIZEN MADE EASY

5️⃣Document Your
Observations

Take notes during the Gemba walk.

You can point the issues out, and solve them at the root
cause later on.

Do
+Document ideas
+Keep on taking notes
+Use visuals (photos, sketches) to capture
details

Don’t
-Ignore feedback
-Rely on your memory
-Overlook important details

KAIZEN MADE EASY

6️⃣Ask Questions
Ask specific questions to understand why
the work is being done in a particular way.

Do
+Use 5W + 1H framework
+Inquire about workflow obstacles
+Prepare a list of open-ended questions

Don’t
-Ask leading questions
-Overlook feedback from workers
-Assume processes are working as documented

KAIZEN MADE EASY

7️⃣Mix Up the Schedule
Schedule the walks at different times to
grasp any variation in your workflow.
If you're used to go for Gemba walks in the morning, set
one in the afternoon too.

Do
+Plan Gemba walks at different times
+Track walk outcomes to detect patterns
+Monitor the effects of time variables on
workflow

Don’t
-Strictly adhere to a set schedule
-Assume all processes work the same way
-Neglect the impact of time on your operations

KAIZEN MADE EASY

8️⃣Follow-up with Employees
Discuss the outcomes of your walk with
employees, including any action plans.

For example, you might schedule a meeting after the

walk to discuss identified issues and potential solutions.

Do
+Acknowledge all contributions
+Share the outcome with the team
+Discuss potential action plans with key
stakeholders

Don’t
-Ignore employee contributions
-Make decisions without open discussions
-Tailor action plans without involving your team

KAIZEN MADE EASY

P.S. If you enjoyed this, repost it for your network
and follow Kaizen Made Easy for more

KAIZEN MADE EASY Learn • Collaborate • Improve