Free Bookkeeping Evaluation. Free Classes Every Friday. Free Compliance Checks. Free SEO Audits
All Ops Tools
LEAN Tool

Gemba Walk

Also known as: Go And See

Leaders go to where the work happens, observe, ask, and learn before they decide. The single highest-leverage habit in LEAN leadership.

What It Is

Gemba (現場) is Japanese for "the real place," the place where value is being created. A Gemba Walk is when a leader goes to that place, watches the work as it actually happens, asks the people doing it open-ended questions, and learns.

It's not an inspection. It's not a status meeting. It's not management-by-walking-around. It's structured observation with a specific posture: respect for people, curiosity for the work, and humility about what you don't yet know.

When To Use It

Run a Gemba Walk before any process change, when a Scorecard metric goes red and stays red, when a team keeps surfacing the same issue at L10, or whenever a decision feels detached from how the work actually flows.

For leaders, weekly Gemba is a habit worth building. A 30-minute walk one day a week, on a different process or team each time, is enough to keep your decisions grounded.

How Launch Uses It

For new operations clients, we run a Gemba in week one before recommending anything. The recommendations land more accurately because we've seen the work, not just the org chart.

For ongoing clients, we coach owners and leaders to do their own Gemba Walks. We do them together the first few times so the leader learns the questions to ask, the things to look for, and (often hardest) the discipline of not fixing things on the walk.

Tips

  • Tell the team you're coming. Surprise visits are inspections; Gemba isn't.
  • Ask open questions: 'Walk me through what you just did.' 'What slows you down here?' 'What would you change?'
  • Bring a notebook. Don't bring a laptop or phone. Your attention is the point.
  • Find one improvement the team has already suggested but couldn't get traction on. Champion it.

Pitfalls To Avoid

  • Fixing things on the walk. The walk is for observing; decisions go through the team's normal cadence.
  • Asking 'why is this slow?' (a blame question). Ask 'what makes this hard?' instead.
  • Skipping the wrap-up note to the team. They should know what you saw and what you're taking back.
  • Only walking when something is going wrong. Walk when things are going well, too.

Template

Gemba Walk: Worksheet

Area / Process

 

Date

 

Walker

 

Duration

 

Purpose of THIS Walk

 

What I Observed (Watch, Don't Judge)

 

Questions I Asked + Answers I Heard

 

What Surprised Me

 

Ideas the Team Surfaced

 

What I'll Take Back (to L10 / Issues List)

 

Need help running this with your team?

Operations consulting from Launch Industries can lead, facilitate, or co-pilot any of these tools alongside your team.

Book a call