The Philosophy Behind Gemba Walks

Gemba walks originate from the Japanese concept of gemba (現場), meaning “the actual place” or “the real place.” In lean management, this translates to going to where value is created—be it a factory floor, a hospital ward, a software development team, or a customer service center. The practice is central to continuous improvement (kaizen) because it grounds leadership in reality rather than reports or secondhand accounts. By observing processes firsthand, managers can identify waste, uncover inefficiencies, and engage with employees who possess the deepest knowledge of daily operations.

Effective Gemba walks are not casual strolls or inspections. They are structured, purposeful activities designed to foster a culture of respect for people and evidence-based problem solving. Leaders who embed Gemba walks into their management rhythm create a shared language of improvement that transcends hierarchical barriers.

For a deeper understanding of the origins and lean principles behind Gemba, you can refer to Lean.org’s definition.

Preparing for a Gemba Walk

Preparation separates a productive Gemba walk from a superficial one. Without clear intent, leaders risk wandering aimlessly, missing critical observations, or making employees feel scrutinized rather than supported. Follow these foundational steps before stepping into the workspace.

Define Clear Objectives

Each Gemba walk should have a specific focus. Common objectives include identifying bottlenecks, understanding employee challenges, assessing safety and compliance, or gathering ideas for incremental improvements. For example, a production line walk might aim to reduce changeover time, while a healthcare Gemba might focus on patient flow during shift changes.

Document your primary question: “What do I want to learn today?” This keeps the walk aligned with strategic priorities.

Equip Yourself with the Right Tools

Bring a notebook, a simple observation form (or a digital device), and a camera if permitted. Avoid complex checklists that limit observation—use them as prompts rather than rigid scripts. Key items to consider:

  • Observation template (e.g., with columns for process step, waste types, comments)
  • Stopwatch (for initial time studies)
  • Safety gear if required on the shop floor
  • Contact information for area supervisors

Communicate the Purpose

Inform team leaders and frontline workers about the walk beforehand. Emphasize that the goal is to learn and support, not to audit or punish. Transparency reduces anxiety and encourages honest dialogue. A brief email or meeting note explaining the objectives and schedule can set the right tone.

Conducting the Gemba Walk: Step-by-Step

The actual walk demands a mindset shift from “managing from behind a desk” to “coaching from the gemba.” Follow these best practices to maximize insight while respecting employees’ expertise.

1. Start with a Brief Huddle

Begin near the entrance of the area with the team leader. Reiterate the objective, ask for any immediate safety concerns, and confirm the walk path. This creates a collaborative atmosphere.

2. Follow the Value Stream

Trace the actual flow of materials, information, or work. Start at the point of customer demand (e.g., shipping dock or service request) and move upstream. Pause at each significant process to observe cycle times, work-in-progress, and waiting or movement.

3. Ask Open-Ended Questions

Engage operators and technicians with questions like:

  • “What is the most difficult part of this step?”
  • “How do you know if you are having a good day?”
  • “What would you change if you could improve one thing?”

Listen more than you speak. A ratio of listening 80% to talking 20% is a useful guideline. Avoid solving problems on the spot—capture the issue and address it during post-walk analysis.

4. Observe Before Intervening

Resist the urge to correct or optimize in real time unless there is an immediate safety risk. Your presence may already affect behavior (Hawthorne effect); note what happens when you step back and simply watch. Use the “Go and See” approach from Toyota Production System: observe the actual work, ask why, and show respect for the process.

5. Take Focused Notes

Record specific observations: location, time, what you saw, and the condition (e.g., “Station 3: operator waiting 45 seconds for parts between batches”). Use photos only with permission and explain how they will be used (e.g., training). Avoid photographing employees without explicit consent.

For a detailed example of effective questioning techniques, see IndustryWeek’s guide to Gemba walk questions.

Common Mistakes During the Walk

  • Walking too fast — you miss the subtle details, such as ergonomic strain or small inventory movements.
  • Focusing only on “bad” observations — overlooking best practices that could be replicated elsewhere.
  • Checking your phone — signals disinterest; stay present.
  • Skipping the gemba of high-performing areas — even well-running processes have improvement potential.
  • Assuming you already know the answers — every Gemba walk should reveal something new.

Post-Walk Actions: Turning Observations into Improvements

The Gemba walk only creates value when observations lead to action. A systematic follow-up ensures that insights are not lost and that employees see tangible results from their openness.

Immediate Debrief

Within 24 hours, hold a short debrief with the team leader and any involved manager. Review key findings, categorize them into safety, quality, delivery, cost, or morale issues. Prioritize the top two or three that are feasible to address quickly.

Use an A3 Problem-Solving Report

For complex issues discovered during the walk, an A3 report (a one-page structured problem-solving tool) can be an excellent follow-up tool. It captures the problem statement, current condition, root cause analysis (using 5 Whys or fishbone diagrams), target condition, and action plan. Share the A3 with the team to involve them in solution design.

Implement Small Changes Rapidly

Low-cost, high-impact improvements—such as relocating a tool rack or updating a standard work instruction—can be implemented within days. This builds trust and demonstrates that Gemba walks are not just talk. Track the results using simple metrics (e.g., time saved, defect reduction, ergonomic risk score).

Institutionalize the Improvement Cycle

Integrate Gemba findings into the Plan-Do-Check-Act (PDCA) cycle already used in your organization. Each walk becomes a systematic checkpoint for continuous improvement, not a one-off event. Consider creating a Gemba Walk Board in each area that lists findings, actions, and status updates visible to all employees.

Expanding Gemba to Different Environments

While Gemba walks originated in manufacturing, they are now applied across industries with tailored adaptations.

Healthcare Gemba Walks

Hospital leaders walk through patient care units, labs, or emergency departments. Observations focus on patient flow, hand hygiene compliance, nurse-to-patient communication, and supply availability. The stakes are higher, so respectful timing (e.g., not interrupting a critical procedure) is essential.

Software Development and IT

In tech environments, the gemba may be the development team’s workspace, a ticketing system queue, or the deployment pipeline. Leaders observe stand-up meetings, pair programming sessions, or release planning. The goal is to identify bottlenecks in code review, recurring bugs, or waiting time between builds.

Service and Administrative Processes

Call centers, claims processing, and accounting departments also benefit from Gemba walks. The walk follows the flow of a document or customer call, observing hand-offs and delays. Software tools like CRM logs can supplement direct observation.

For examples of Gemba in service industries, see Process Excellence Network’s article.

Digital Gemba Walks: Opportunities and Pitfalls

In remote or hybrid work environments, physical presence is not always possible. Digital Gemba walks use video calls, shared dashboards, and screen sharing to virtually observe work. While this sacrifices some sensory richness (e.g., cannot feel the heat of a furnace or smell an exhaust leak), it can still provide valuable insights into digital workflows.

Best practices for virtual Gemba walks:

  • Schedule the walk during the actual process time (not a mock demonstration).
  • Ask the employee to share their screen and explain their steps, while you silently watch.
  • Use a shared document to take notes in real time, visible to the employee.
  • Resist the temptation to multi-task — maintain the same focused attention as an in-person walk.

However, recognize that digital walks miss the physical context, such as ergonomic issues, ambient noise, or non-verbal cues. A blend of in-person and digital walks is often optimal.

Measuring the Impact of Gemba Walks

To justify the time investment, organizations should track leading and lagging indicators. Common metrics include:

  • Number of improvement suggestions generated per walk
  • Implementation rate (percentage of suggestions acted upon within 30 days)
  • Employee engagement scores (survey questions about feeling heard)
  • Operational KPIs tied to observed processes (e.g., cycle time, defect rate, first-pass yield)
  • Frequency and consistency of walks across leadership levels

Organizations that regularly audit the effectiveness of their Gemba walks find that disciplined follow-through correlates with higher morale and better problem-solving capacity.

Building a Gemba Walk Culture

Mature lean organizations treat Gemba walks as a core leadership habit, not a periodic event. To embed this culture:

  • Senior leaders model the behavior by walking regularly (weekly or biweekly).
  • Rotate the focus area: one week safety, next week quality, etc.
  • Include cross-functional participants from maintenance, engineering, HR, etc.
  • Recognize teams that act on findings (e.g., share success stories in town halls).
  • Provide brief training on lean observation techniques for new leaders.

When done right, Gemba walks evolve from a management tool into a shared ritual of continuous improvement. Employees start to expect the visits and prepare their own improvement ideas in advance.

Common Pitfalls and How to Avoid Them

Even well-intentioned Gemba walks can backfire if leaders fall into these traps:

Pitfall Consequence Remedy
Treating it as a performance review Employees become defensive or hide problems Emphasize learning and curiosity; avoid grading
Dominating conversations Workers clam up; you miss real issues Use the 80/20 listening rule
No actionable follow-up Disillusionment; future walks ignored Always complete a “next actions” section
Walking the same route every time Narrow focus; miss other areas Rotate routes and vary times
Ignoring positive observations Diminished morale; lost chance to replicate successes Record and share best practices

Integrating Gemba with Daily Management Systems

In organizations with a robust lean operational model, Gemba walks feed directly into the daily management system. Observations are reviewed at daily stand-up meetings, and countermeasures are assigned to specific owners. This creates a tight feedback loop where the gemba drives real-time improvements rather than gathering dust in reports.

Some companies link their Gemba walk observations to their Kaizen event pipeline. If a walk reveals a major waste type (e.g., high defect rate on a specific process), it might trigger a week-long Kaizen blitz focused on that area.

Case Example: Gemba in a Distribution Center

A large logistics operator noticed rising shipping errors and declining employee morale. They initiated weekly Gemba walks by the warehouse manager and a continuous improvement coach. During the first walk, they observed pickers walking an average of 200 meters per order due to poor slotting. By asking open-ended questions, they learned that high-turnover items were stored far from the packing station. The team implemented a simple slotting adjustment, reducing travel distance by 40% within two weeks. The follow-up walk showed improved productivity and fewer errors. This example illustrates how a small observation, validated on the gemba, can yield outsized results.

For additional real-world case studies, see shmula’s compilation of Gemba walk stories.

Conclusion: The Gemba Mindset

Effective Gemba walks are not merely a technique but a reflection of a leadership philosophy that values go-and-see, ask-why, and show-respect. When conducted with genuine curiosity and disciplined follow-through, they become a powerful engine for continuous improvement. They break down silos, empower frontline workers, and keep the organization focused on what truly matters: delivering value to the customer. Start small, walk regularly, and let the gemba teach you.

For a deeper dive into Toyota’s Gemba principles, read Lean.org’s Gemba Walk primer.