Ivan Carillo

GEMBA WALK preparation

8 STEPS FOR A SUCCESSFUL
GEMBA WALK
Ivan Carillo

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
Ivan Carillo

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
Ivan Carillo

3. Follow the Value StreaM

Observe how the 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
Ivan Carillo

4. Blame ProcessES,
not 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:

+Use the walk to learn more, not to blame

+Communicate that the focus is on the process
+Encourage discussions about the main challenges

Don't:

-Criticize team members

-Create a blaming atmosphere
-Divert focus to individual performance
Ivan Carillo

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
Ivan Carillo

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
Ivan Carillo

7. Mix Up the SchedulE

Schedule the walks at different times to grasp any
variation in your workflow.

If you're used to going 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
Ivan Carillo

8. Follow-up with Employees

Discuss the outcomes of your walk with employees,
including any action plans.

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
Ivan Carillo

TL;DR:

1. Prepare the team

2. have a plan
3. follow the value stream
4. BLAME PROCESSES, NOT PEOPLE
5. DOCUMENT YOUR OBSERVATIONS
6. ASK QUESTIONS
7. MIX UP THE SCHEDULE
8. FOLLOW UP WITH THE EMPLOYEES
Ivan Carillo

REPOST THIS
AND FOLLOW ME FOR DAILY POSTS ABOUT LEAN,
CONTINUOUS IMPROVEMENT AND INNOVATION