GembaJapanese: 現場 — "the actual place"

Gemba (現場) literally means "the actual place" in Japanese — originally used by police and journalists to refer to a crime scene or news scene, then adopted by Toyota for the workplace floor where value is actually created. In a manufacturing context it is the production floor, the dispensary, the warehouse picking aisle, the QC laboratory bench, the packaging line. Not the conference room, not the office, not the dashboard, not the management report.

The principle is that reality is most accurately seen at the gemba, by people physically present, observing the actual work in the actual conditions with the actual operators using the actual equipment. Reports are abstractions — useful but inevitably distorted; the gemba is where abstractions get falsified by reality. Masaaki Imai's 1997 book Gemba Kaizen made the term central to Western lean practice and Jim Womack's Gemba Walks made it operational for executives.

Genchi genbutsu (現地現物, "actual place, actual thing") is Toyota's principle number 12 in Liker's codification: go to the source to find facts and make correct decisions. It is the philosophical engine under the gemba practice. The principle has three teeth:

1. Decisions about work are made at the work, not from descriptions of the work. A senior leader who has not been at the line for 6 months has no useful opinion about the line.
2. Problems are understood by direct observation, not by reading reports. Reports filter, summarise, average and politicise. The gemba shows the actual conditions, including the conditions nobody bothered to write down.
3. Coaching, teaching and improvement happen at the work, in real time, with the people who do the work. Classroom training has its place but doesn't change behaviour; coaching at the gemba does.

The gemba walk is the structured practice that operationalises gemba presence: a regular, scheduled, formatted visit to the workplace by leadership, with a clear purpose. David Mann's Creating a Lean Culture and Jim Womack's Gemba Walks are the canonical operating-manual references. Common formats:

The team-leader walk is the most frequent and arguably the most important; if it isn't happening, none of the others will produce real value. The executive walk is the highest-leverage culturally because it sends the loudest signal about what leadership values.

A good gemba walk is not aimless wandering. It is a structured practice with consistent format that makes it productive every time and makes the team feel respected rather than inspected. The standard structure:

1. Pre-walk preparation (5 minutes) — review previous walk findings, area KPIs (OEE, RFT, safety), known issues; arrive informed but with mind open.
2. Observe before speaking (10-15 minutes per area) — watch the work without interrupting; note what you see; resist the urge to comment immediately. Imai's directive: "stand in the chalk circle for an hour" (Ohno's training of his apprentices) — observation before intervention.
3. Ask, don't tell — open questions: "what's working well?", "what's getting in your way?", "if you could change one thing about this process, what would it be?". Operators know the problems; leadership's job is to listen and act, not diagnose.
4. Coach the problem-solving, don't solve the problem — when an issue surfaces, walk the operator / supervisor through PDCA or 5-whys rather than supplying the answer. The point is to build capability, not deliver fixes.
5. Verify previous findings — start every area visit with "what happened with the issue we identified last week?" — if no follow-through, the walk is theatre.
6. Remove obstacles — the senior leader's job at the gemba is to remove obstacles only senior leadership can remove (cross-area conflicts, resource allocation, capital approval, policy). Operators surface them; leadership eliminates them.
7. Recognise + thank — every walk includes specific recognition of specific good practice; generic "great job" is worse than nothing.
8. Capture + commit — written commitments with owners + dates; the gemba record is auditable evidence of leadership engagement (ICH Q10, 21 CFR 820.20 management responsibility).
9. Follow-through within the committed timeframe — the walk's credibility is built or destroyed in the follow-through; unmet commitments destroy the next 10 walks of any leader.

Regulated plants must run gemba walks for both productivity and compliance reasons. Specific clauses that explicitly or implicitly require leadership presence at the work:

1. 21 CFR 820.20 — Management responsibility: "Management with executive responsibility shall review the suitability and effectiveness of the quality system at defined intervals". The management review is the formal artefact; the gemba walk is the regular practice that makes the management review based on reality rather than reports.
2. ICH Q10 §2.7 — Management commitment + management responsibility: senior management is responsible for ensuring an effective PQS. "Effective" is only verifiable by presence at the work; reports alone don't verify effectiveness.
3. EU GMP Chapter 2 — Personnel + organisation: senior management is responsible for the QMS implementation. Inspectors will ask the plant manager about specific recent gemba observations; a plant manager who cannot describe last week's floor visit signals weak engagement.
4. FDA QSIT inspection — investigators frequently include a floor walk and observe whether the leadership accompanying them knows the floor. "When did you last walk this area, Ms. Director?" is a common pre-walk question with diagnostic weight.
5. ISO 13485 §5.6 — Management review: the documented review must be based on inputs that include process performance, customer feedback, audit results — all data that should be ground-truthed by gemba presence.
6. 21 CFR 211.180(e) — Records reviewed by quality control unit at least annually: while the records review is a desk activity, supplementing it with gemba presence reveals what the records don't.
7. ISO 9001:2015 §5.1 — Leadership and commitment: "top management shall demonstrate leadership and commitment with respect to the QMS". Walking the gemba is the practical demonstration.

• Leader walk frequency — minutes per week at the gemba per leader; mature plants run 4-8 hours / week for the plant manager + functional directors; <1 hour is red.
• Walk follow-through rate — fraction of committed actions from gemba walks closed within commitment deadline; <80% means walks are theatre.
• Time-from-finding-to-resolution — median days from gemba observation to closed action; trending up means follow-through is slipping.
• Operator-reported obstacle removal — operator survey item "obstacles I raise to leadership get removed"; the headline trust metric.
• Cross-area issue resolution — how many of the issues that only leadership can resolve actually get resolved; this is the unique-value-of-leadership measure.
• Coverage — fraction of areas visited per cadence (weekly / monthly); deserts where no leader has walked in 6 months are the predictable problem spots.
• Repeat-finding rate — how often the same issue surfaces walk after walk without resolution; the leading indicator of leadership tolerating slow follow-through.

Mistake 1 — the auditing walk dressed as a coaching walk

When the senior leader's tone, body language, or questions read as evaluation rather than support, operators stop surfacing problems. Within 2-3 visits the walk produces only the safe, pre-staged version of reality. To rebuild trust takes 6-12 months of disciplined non-judgmental presence.

Mistake 2 — telling, not asking

Senior leaders walk in, see something they would do differently, and direct the change on the spot. This bypasses the area supervisor's authority, removes the team's ownership, and reliably produces a change that doesn't stick. The discipline is to ask "what do you think of X?" and let the team own the response.

Mistake 3 — no follow-through

Leadership notes issues, makes verbal commitments, returns to the office, and forgets. The next walk surfaces the same issues. Within 3 walks the operators stop bothering to surface them. Discipline: written commitments with owners + dates + auditable record + leader-accountable review at the next walk.

Mistake 4 — walk-as-photo-op

Visiting executives, board members, regulators visit the floor with the operations team carefully managing the route. The visitors see what management wants them to see; the operators see leadership only when accompanied by a director coaching them on what to say. This is anti-gemba — the actual conditions are the point.

Mistake 5 — wrong cadence

Quarterly executive walks alone don't move culture; daily team-leader walks alone don't move strategy. Mature plants have the full ladder (team leader several / shift → ops manager daily → plant manager weekly → executive monthly), each with appropriate framing.

Mistake 6 — confusing it with a tour

A tour is a one-way information transfer with the visitor as audience; a gemba walk is a two-way listening and coaching practice. Tours are fine for visitors with no operational role; gemba walks are for people who can act on what they see.

Mistake 7 — skipping the gemba in regulated plants

Some regulated plants treat the gemba as too sensitive ("the inspectors might see something"). This is exactly backwards — the gemba walk is how leadership finds the issues before the inspector does and ensures the audit walk goes well. Avoidance is the most reliable way to produce 483s.

V5 ships gemba walk infrastructure that makes the practice repeatable, auditable, and linked to the regulated quality system rather than living on whiteboards and notebooks.

• Gemba walk template — configurable per walk-type (team-leader, ops, plant, executive, quality) with cadence + duration + standard prompts; assigned to the right role with reminders.
• Area kiosk dashboard — when a leader arrives at an area, the kiosk surfaces the area's current OEE, RFT, safety incidents, open kaizen suggestions, overdue training, calibration-due, last audit findings + status — so the walk starts informed.
• Walk record capture — observations + commitments + owners + due-dates entered on mobile during the walk; auto-routes commitments to the named owners with due-date tracking.
• Follow-through tracking — each walk begins with status of commitments from the prior walk; auto-flagged regressions and overdue items; trending dashboards by leader + area.
• Operator obstacle queue — operators can post obstacles to the gemba walk queue between walks via the kiosk; leadership sees them on the next walk; this short-circuits the "raise it when the leader is here" delay.
• Coaching kata support — Toyota-kata-style improvement-kata + coaching-kata templates that structure the coaching dialogue (current condition → target condition → obstacles → experiments → reflect); the leader's role becomes coaching capability, not solving problems.
• Management review integration — ICH Q10 / 21 CFR 820.20 / ISO 13485 §5.6 management reviews auto-include the gemba walk record as an input; the management review is grounded in field reality, not abstracted reports.
• CAPA + kaizen linkage — observations from gemba walks that warrant formal CAPA or kaizen-event auto-create the shell with cross-reference; nothing surfaces and dies.
• Audit-walk vs coaching-walk separation — different templates with different framings; the coaching walk explicitly does not feed audit findings; the audit walk explicitly does. The dual-track prevents the trust-destroying mode confusion.
• Inspector-readiness export — the gemba walk log over the past 12 months exports as evidence of management responsibility for FDA / Notified Body / ISO inspections.
• Mobile-safe — entire gemba walk surface designed for iPhone (≤390 px CSS width); the leader walks the floor with the phone, not with a clipboard or tablet.

Is gemba just walking around?

No. Aimless walking around (the management-by-walking-around fashion of the 1980s) is friendlier than absence but doesn't produce the structured value of a gemba walk. The gemba walk has a structure (observe → ask → coach → commit → follow-through), a purpose, and a record. Casual walking around without these has minimal value.

How often should leaders do a gemba walk?

Team leaders: multiple times per shift. Area supervisors / ops managers: daily. Plant managers: weekly per area. Executives: monthly per site. Quality directors: weekly with a regulatory-readiness lens. The cadence ladder is what makes the system work — any one cadence alone is insufficient.

What's the difference between a gemba walk and an audit?

A gemba walk is a coaching + listening + obstacle-removal practice; an audit is an evaluation against a standard. Both belong on the schedule, with clearly different framings. Operators must know which mode the leader is in; mixing the two destroys trust in both.

Does gemba work in non-manufacturing contexts?

Yes. In healthcare the gemba is the patient room or treatment area (Virginia Mason Medical Center is the canonical example); in software it is where users actually use the software; in services it is where the customer interacts. The principle (reality is most accurate at the place of value-creation) is general.

Do FDA / EU GMP inspectors care about gemba walks?

Implicitly, yes. They evaluate management responsibility per 820.20 / ICH Q10 / ISO 13485 §5.6; the gemba walk record is the most concrete evidence that management is engaged with reality. Inspectors often ask plant leaders about specific recent floor observations; an answer that lands well requires actual recent presence.

How does V5 support gemba walks?

Configurable walk templates per leader role + area kiosk dashboard surfacing live area KPIs + walk-record capture with auto-routed commitments + follow-through tracking + operator obstacle queue + coaching-kata templates + ICH Q10 management-review integration + CAPA + kaizen linkage + audit-walk vs coaching-walk separation + 12-month inspector-readiness export + mobile-safe at iPhone width. The walk lives in the Part 11 audit trail.

What if I'm too busy for gemba walks?

Honest answer: the things keeping you too busy are usually the symptoms of not doing gemba walks. Plants where leadership has the discipline of 4-8 hours / week at the gemba have systematically fewer fires, faster issue resolution, lower CAPA backlog, and more time. The walk is the investment that creates the time.