Gemba Walk
Gemba (Japanese for 'the real place') is where the actual value-creating work happens — the factory floor, the support queue, the customer's office, the engineer's IDE. A Gemba Walk is a structured leadership practice of going to the place where work happens, observing without interrupting, asking questions, and learning what the data and dashboards don't tell you. The related Toyota principle 'Genchi Genbutsu' translates as 'go and see for yourself.' Toyota executives, including the CEO, are expected to spend significant time on the shop floor every week. The whole point: every report, dashboard, and slide deck is a translation of reality. Gemba Walks bypass the translation. You see the actual queue, the actual workaround, the actual customer frustration — not the version that survived 4 layers of summarization.
The Trap
Two failure modes. (1) The 'Inspection Walk' — leaders walk the floor with clipboards looking for violations, asking gotcha questions, and assigning blame. Workers learn to hide problems and put on a show when leadership shows up. The walks become surveillance, not learning. (2) The 'Photo Op Walk' — leaders walk through, smile at workers, take a photo for LinkedIn, and leave without listening or following up on issues raised. After two of these, workers stop bringing problems forward because nothing comes of it. Real Gemba Walks are quiet, curious, and produce written follow-ups within 48 hours on every issue surfaced.
What to Do
Block 60-90 minutes weekly on your calendar labeled 'Gemba.' Pick ONE area each week (engineering pod, support queue, customer onboarding, sales discovery calls). Show up unannounced or with minimal notice. Bring a notebook. Ask three kinds of questions: (1) 'Walk me through how this works' (process), (2) 'What gets in your way?' (waste), (3) 'What would you change if you had a day to fix it?' (ideas). Take notes; do NOT promise on the spot. Within 48 hours: send a written summary to the team with what you'll personally act on and what's been escalated. Track: 90% of issues raised in Gemba walks should have a documented response within a week.
Formula
In Practice
Andy Grove, Intel's legendary CEO, was famous for unannounced visits to engineering labs and fab floors. He'd sit silently in 1:1 meetings between his managers and their reports, take notes, and afterward pepper the manager with questions about details he'd observed. His Gemba practice — combined with his 'High Output Management' framework — is widely credited as the reason Intel could spot quality issues 12-18 months earlier than competitors. Grove's rule, from his 1983 book: 'Information that travels through more than two layers of management has been laundered into uselessness. The CEO who relies on it is steering by a translated, smoothed map of reality.' His successors who abandoned the practice (1998-2010) presided over Intel's manufacturing-quality decline.
Pro Tips
- 01
Don't bring solutions on a Gemba Walk. The moment a senior leader says 'you should do X,' the local team stops learning and starts doing what the leader said. Your job is to see and to ask, not to direct. Save the directing for after you've fully understood the situation.
- 02
Toyota executives use a structured tool called the A3 — a single sheet that captures problem, current state, root cause, countermeasure, and check. Bring an A3 template to every Gemba and ask the team to fill it out together. The discipline of writing forces specificity that conversation alone won't.
- 03
Schedule your follow-up emails BEFORE the walk ends. Calendar blocks for 'Friday: send Gemba summary' eliminate the failure mode where insights die in your notebook. The team's trust in Gemba is built entirely by your follow-through, not your presence.
Myth vs Reality
Myth
“Gemba walks are just management-by-walking-around (MBWA)”
Reality
MBWA is informal and social ('how's it going?'). Gemba is structured: specific area, specific questions, written follow-up, measurable issues addressed. They look similar; they produce very different results. MBWA builds rapport; Gemba builds operational understanding.
Myth
“Gemba walks only matter for in-person factory work; remote/digital work is different”
Reality
The 'gemba' for software is the actual repo, the actual deployment pipeline, the actual customer support ticket queue. Watching a real engineer try to ship a real change end-to-end (paired observation for a half-day) is the digital Gemba. The principle is identical: go where the value is created, not where it's reported.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
You're a CEO. You want to know why customer onboarding takes 4 weeks. Which approach gives you the truest answer?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Executive Gemba Time per Week
Senior leaders in operationally-intensive industriesToyota / Operationally Excellent
5-10 hrs/wk
Healthy Practice
2-5 hrs/wk
Symbolic
0.5-2 hrs/wk
None (dashboard-only)
< 30 min/wk
Source: Lean Enterprise Institute / Toyota Way Field Book
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Toyota (Genchi Genbutsu Origin)
1950s-Present
Genchi Genbutsu ('go and see for yourself') is one of Toyota's 14 management principles. Toyota's CEO and senior executives are expected to spend significant time on the shop floor every week. When Akio Toyoda became CEO during the 2009-2010 recall crisis, he personally visited dozens of plants and dealers globally to understand the quality issues — rather than relying on engineering reports. The cultural rule: any decision made without Genchi Genbutsu is suspect. New hires (including MBAs) spend their first weeks rotating through production stations before any office work. The practice is widely credited as the foundation of Toyota's ability to identify problems at source rather than via dashboards.
Senior Exec Floor Time
Multiple hours weekly
New Hire Floor Rotation
Several weeks
Decisions Requiring Site Visit
All major operational decisions
Quality Leadership Position
Maintained 60+ years
Toyota's quality leadership is not a function of better engineering — competitors have similar engineers. It's a function of leaders who insist on seeing the actual work, every week, for decades.
Intel (Andy Grove Era)
1979-1998
Andy Grove built Intel's operational rigor partly through his fanatical commitment to direct observation. He'd show up unannounced in fab clean rooms, attend skip-level 1:1s as a silent observer, and quiz his managers on details only obtainable from the floor. His book 'High Output Management' codified the practice as core to executive work. Intel's manufacturing precision — achieving sub-micron yields while competitors struggled — is widely attributed to leadership that knew the actual operations, not just the reported KPIs. After Grove's retirement (1998), the practice eroded; Intel's manufacturing leadership eroded with it through the 2010s.
Grove's Floor Time
Multiple hours per week
Yield Leadership vs. Competitors
Sustained for 20+ years
Post-Grove Practice Decline
Correlated with quality decline
'High Output Management' Influence
Required reading at most tech firms
When the executive Gemba practice ends, operational excellence ends within a generation. Practices die when leaders die or retire — unless they're institutionalized.
Hypothetical: Series B SaaS CEO
Recent
A Series B SaaS CEO (180 employees) was frustrated that customer support escalations kept rising despite dashboards showing improving CSAT. She instituted a weekly 90-minute Gemba: alternating weeks between sitting with a support agent on real tickets and listening in on a CSM's customer call. Within 8 weeks, she'd identified 3 systemic issues invisible in dashboards: a billing edge case generating 30% of escalations, a documentation gap causing repeat questions, and a Salesforce field that was driving wrong CSM assignments. Fixed all three within a quarter; escalation rate dropped 45%. CEO time investment: ~75 hours over 6 months.
Issues Identified via Gemba
3 systemic (invisible in dashboards)
Escalation Rate
-45% in 6 months
CEO Time Invested
~75 hrs over 6 months
Estimated Annual Value
$1.2M (retention + support cost)
Gemba is one of the highest-leverage uses of an executive's time, especially in companies under 500 people where the layers between CEO and customer are still few enough to actually walk.
Decision scenario
The First Gemba Walk Reaction
You're a new CEO at a 250-person logistics company. On your first Gemba walk in the warehouse, an operator tells you: 'The picking software has been broken since March. We work around it manually.' Your COO swears the system was fixed in April per his dashboard. The operator quietly adds: 'My manager told me not to bring this up to anyone above him.'
Time on Job
3 weeks
What Dashboard Says
Software fixed April
What Operator Says
Still broken
What Manager Said
Don't escalate
Decision 1
How you handle this in the next 48 hours sets the tone for whether anyone tells you the truth ever again.
Thank the operator privately, then send a stern email to the COO demanding to know why the dashboard is wrongReveal
Thank the operator, ask for permission to share what you heard (without identifying her), schedule a 30-minute working session with the COO to look at the actual ticket queue together — not the dashboard✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Gemba Walk into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Gemba Walk into a live operating decision.
Use Gemba Walk as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.