How often should leaders do Gemba walks?

Weekly is the sweet spot for project leaders; monthly for executive sponsors. Less than monthly and the walks become disconnected from daily reality; more than weekly and they consume more of the team's time than they create value.

Is a Gemba walk the same as 'management by walking around'?

No. MBWA is informal and unscoped. A Gemba walk is structured: a theme, a route, a format for engagement, and a debrief. The discipline is what separates a Gemba walk from a stroll.

Can you do a Gemba walk on a remote team?

Yes — by sitting with one team member for two hours via screen-share and watching them work a real ticket. The principle (go to where the work happens) is identical; the venue is the developer's environment, not a factory floor.

What if I see something unsafe on a walk?

Safety is the one exception to the 'don't intervene' rule. Stop the work, ensure safety, but step back from the corrective action — that still flows through the supervisor and the normal process. Don't escalate beyond the immediate hazard.

Should we record metrics on Gemba walks?

Light counting is fine — frequency of hand-offs, queue depth, near-misses — but heavy data collection turns the walk into an audit. If you need detailed metrics, send an observer separately; protect the walk's character.

How do I get the team to trust the walks?

Never criticise individuals on the walk, never override the supervisor, always close the loop on issues raised, and never use what you saw against people in performance discussions. Trust takes 8–12 walks to build and one bad walk to destroy.

What's the right group size?

One or two people. Senior leader plus one apprentice is ideal because it builds the next generation of observers. Anything beyond three becomes a parade and the team stops talking.

How is a Gemba walk different from a site inspection?

An inspection is to verify compliance against a standard; a Gemba walk is to learn what the work is really like. Inspections produce reports and corrective actions; Gemba walks produce insight and questions. Both have a place; conflating them ruins both.

Which calculators on PMMilestone.org apply to Gemba Walk?

For Gemba Walk, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Gemba Walk?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Gemba Walk?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Gemba Walk?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Gemba Walk is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Gemba Walk defined on PMMilestone Research & Insights?

A lean management practice of going to the actual place where work is performed — site, factory floor, or team room — to observe, ask questions, and learn directly rather than rely on reports. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Lean · Letter G

Gemba Walk

A lean management practice of going to the actual place where work is performed — site, factory floor, or team room — to observe, ask questions, and learn directly rather than rely on reports.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-23

Definition

A Gemba walk is a structured visit by managers and leaders to the place where value is actually created — the construction site, the manufacturing line, the developer's screen, the call-centre floor — to observe work first-hand, talk to the people doing it, and learn what reports cannot tell them. Gemba (現場) is Japanese for "the real place." The discipline came out of Toyota Production System and has been adopted by lean construction, lean software, and modern operations leadership worldwide.

What It Is — and Is Not

A Gemba walk is not an inspection, an audit, or a management-by-walking-around photo opportunity. It is not a chance to fix things on the spot or to lecture. It is a learning practice: leaders go to see, ask, and listen. The default verbs are watch, ask why, and write down. Decisions and corrective actions happen later, with the team, after reflection. A walk that ends in five spot-corrections has failed.

Real-World Construction Example

On a hospital fit-out, the project director ran a weekly 45-minute Gemba walk through one trade area at a time. The format was strict: foreman walks first and explains, director listens, no instructions given on the walk. Over 14 weeks the walks surfaced eleven systemic issues that the daily reports had missed — material staging conflicts, an unclear hand-over protocol between MEP and finishes, a tool-room queue that cost two hours per crew per day. Closing those issues lifted weekly productivity by 18% and cut RFIs in half.

Real-World IT / Agile Example

The IT equivalent is a leader sitting with a developer or support engineer for two hours and watching them work. On a SaaS platform team, the VP of engineering did monthly Gemba sessions — one engineer, one full ticket, screen shared, no interruptions. The walks exposed a deployment pipeline that took 40 minutes for a one-line change, a flaky test suite developers had given up reporting, and an internal documentation site no one trusted. None of these were in the dashboards; all of them were costing the team a day a week.

Standard Format

Prepare: pick a theme (safety, flow, quality, hand-offs), brief the team, agree the route.
Observe: watch one process end-to-end. Don't interrupt.
Engage: ask open questions. "Walk me through this." "What's hardest about this step?" "What did you try before?"
Show respect: never criticise individuals on the walk, never override the supervisor in front of the team.
Reflect: debrief with the supervisor after the walk; agree what you learned, not what you'll change.
Follow up: changes flow through the team's normal improvement cycle, not as a manager edict.

Project Controls Perspective

Controls teams that run weekly Gemba walks build a richer cost and schedule narrative than those that rely on system data alone. The reconciliation between what the cost report says and what the site looks like is often the first signal of a productivity slip — typically two to four weeks earlier than the CPI/SPI numbers move. Many of the best schedulers I know spend at least half a day a week on the work face for exactly this reason.

Common Mistakes

Turning it into an inspection. Once the team thinks they're being judged, you'll see what they want you to see.
Fixing things on the walk. Undermines the supervisor and trains the team to wait for the next walk.
Walking the same route every week. Familiar paths produce familiar observations.
Bringing an entourage. A leader with six people behind them is a parade, not a Gemba walk.
Skipping the debrief. Observations without reflection are just exercise.
No follow-through. Teams stop engaging when issues raised on walks vanish into the void.

Expert Tips

Pick a theme each week. "Hand-offs," "first-time quality," "safety near-misses" — themes focus the eye.
Ask five whys, not five whats. The discipline is causal, not informational.
Carry a notebook, not a clipboard. Clipboards signal audit; notebooks signal learning.
Go alone or in pairs. Senior plus a junior protégé is the best format I know.
Close the loop publicly. When an issue raised on a walk is resolved, name it in the next stand-up or town hall.

Key Takeaways

Gemba means the place where value is created — go there, regularly, and learn.
It is a learning practice, not an inspection. Observe, ask, listen, leave.
The walks surface systemic issues that reports miss — typically weeks before the metrics move.
Walks without follow-through erode trust faster than no walks at all.
The construction site, the developer's screen, the support agent's queue — Gemba is universal.

Related Encyclopedia Entries

Last Planner System — companion entry on a directly related concept.
Lessons Learned — companion entry on a directly related concept.
Quality Management — companion entry on a directly related concept.
Daily Stand-up — companion entry on a directly related concept.
Value Engineering — companion entry on a directly related concept.
Takt Time Planning — companion entry on a directly related concept.

Frequently Asked Questions

How often should leaders do Gemba walks?
Weekly is the sweet spot for project leaders; monthly for executive sponsors. Less than monthly and the walks become disconnected from daily reality; more than weekly and they consume more of the team's time than they create value.
Is a Gemba walk the same as 'management by walking around'?
No. MBWA is informal and unscoped. A Gemba walk is structured: a theme, a route, a format for engagement, and a debrief. The discipline is what separates a Gemba walk from a stroll.
Can you do a Gemba walk on a remote team?
Yes — by sitting with one team member for two hours via screen-share and watching them work a real ticket. The principle (go to where the work happens) is identical; the venue is the developer's environment, not a factory floor.
What if I see something unsafe on a walk?
Safety is the one exception to the 'don't intervene' rule. Stop the work, ensure safety, but step back from the corrective action — that still flows through the supervisor and the normal process. Don't escalate beyond the immediate hazard.
Should we record metrics on Gemba walks?
Light counting is fine — frequency of hand-offs, queue depth, near-misses — but heavy data collection turns the walk into an audit. If you need detailed metrics, send an observer separately; protect the walk's character.
How do I get the team to trust the walks?
Never criticise individuals on the walk, never override the supervisor, always close the loop on issues raised, and never use what you saw against people in performance discussions. Trust takes 8–12 walks to build and one bad walk to destroy.
What's the right group size?
One or two people. Senior leader plus one apprentice is ideal because it builds the next generation of observers. Anything beyond three becomes a parade and the team stops talking.
How is a Gemba walk different from a site inspection?
An inspection is to verify compliance against a standard; a Gemba walk is to learn what the work is really like. Inspections produce reports and corrective actions; Gemba walks produce insight and questions. Both have a place; conflating them ruins both.
Which calculators on PMMilestone.org apply to Gemba Walk?
For Gemba Walk, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Gemba Walk?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.
Which related encyclopedia entries should I read alongside Gemba Walk?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Gemba Walk?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Gemba Walk is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Gemba Walk defined on PMMilestone Research & Insights?
A lean management practice of going to the actual place where work is performed — site, factory floor, or team room — to observe, ask questions, and learn directly rather than rely on reports. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for Gemba Walk →