Gemba
Interview: When the Right Question on the Shop Floor Reveals More Than a
Thousand Charts Ever Could
The Question That Changed
Everything
It was a Tuesday morning in a stamping plant somewhere in Central
Europe. The quality engineer had spent three days building a Pareto
chart, a fishbone diagram, and a scatter plot trying to understand why
dimension A on part number 4732 kept drifting out of spec between 10:00
AM and noon. The data was clean. The charts were beautiful. The answer
was nowhere to be found.
Then the plant manager walked onto the line, stood next to the
operator, and asked one question: “What changes around here at ten
o’clock?”
The operator didn’t even look up. “The sunlight hits the gauge.
We can’t read it properly, so we guess.”
Three days of analysis. One question. One answer. The fix cost forty
euros — a window blind.
That’s the Gemba Interview. And if you’ve never heard of it as a
formal technique, you’re not alone. Most quality professionals stumble
into it accidentally. But the ones who practice it deliberately? They
solve problems in hours that others chase for weeks.
What Is a Gemba Interview?
A Gemba Interview is a structured — but conversational — questioning
technique performed at the actual place where work happens (gemba). It
is not an interrogation. It is not an audit. It is not a checklist
exercise. It is the deliberate art of asking open, probing questions to
the people who actually do the work, in the environment where they do
it, to uncover information that no dashboard, database, or report will
ever show you.
The concept borrows from investigative journalism, cognitive
interviewing techniques used in law enforcement, and the Toyota
tradition of asking “why” five times. But it wraps all of that into a
practical, repeatable skill that any quality professional, engineer, or
manager can learn.
Think of it this way: your SPC charts tell you what is
happening. Your Gemba Interview tells you why. And it’s the
“why” that fixes things permanently.
Why Traditional Data
Misses the Truth
Here’s an uncomfortable truth that most quality systems are built to
ignore: the most critical information in your process lives in
people’s heads, not in your databases.
Operators know things they’ve never reported. Shift leaders notice
patterns they’ve never documented. Maintenance technicians hear sounds
that tell them more than any sensor ever could. This knowledge — often
called tacit knowledge — doesn’t show up in your MES system. It doesn’t
appear in your control plan. It lives in the space between what your
system captures and what actually happens on the line.
Standard data collection has three blind spots:
1. The Reporting Gap. Not everything that happens
gets recorded. An operator who adjusts a fixture slightly because “it
works better this way” doesn’t fill out a deviation report. A shift
leader who skips a calibration check because the line is behind schedule
doesn’t log that decision. Your data is only as good as your reporting
discipline — and your reporting discipline is never as good as you
think.
2. The Context Gap. Even when data is recorded, it’s
stripped of context. A temperature reading of 42°C tells you a number.
It doesn’t tell you that the operator opened the window because the air
conditioning broke two weeks ago and nobody fixed it. Context lives in
the physical environment and in people’s stories — not in your data
historian.
3. The Normalisation Gap. When something happens
every day for six months, it stops being a problem and starts being
“normal.” Operators stop reporting it. Engineers stop investigating it.
Managers stop seeing it. But it’s still there, silently degrading your
quality, your efficiency, and your people’s faith in the system.
The Gemba Interview is designed to bridge all three gaps
simultaneously.
The Seven
Principles of an Effective Gemba Interview
Principle
1: Go to the Work, Don’t Bring the Work to You
This sounds obvious, but it’s violated constantly. You cannot conduct
a meaningful Gemba Interview in a conference room. The physical
environment triggers memories, reveals conditions, and provides context
that the human brain simply cannot reconstruct from memory in a sterile
meeting space.
When you’re standing at the workstation, you can see the clutter that
the operator works around. You can feel the temperature that affects the
material. You can hear the unusual vibration that signals bearing wear.
You can smell the coolant concentration before it becomes a quality
problem.
The environment is data. The interview location is your first data
source.
Principle 2: Observe
Before You Speak
When you arrive at the workstation, don’t start talking. Watch. For
at least five to ten minutes, observe the work without interrupting. Let
the operator continue their normal routine.
What you’re looking for: – Workarounds — things the
operator does differently from the standard –
Hesitations — moments where the operator pauses,
double-checks, or seems uncertain – Adjustments —
informal tweaks that aren’t part of the documented process –
Body language — signs of discomfort, frustration, or
excessive effort – Environmental factors — lighting,
noise, temperature, tool condition, workspace layout
Every one of these observations becomes a potential interview
question. “I noticed you checked that dimension twice — is there a
reason?” That’s infinitely more powerful than “Tell me about your
process.”
Principle
3: Ask About the Work, Not About the System
There’s a critical difference between these two questions:
- “How does your quality management system handle
nonconformances?” → The operator gives you the official answer they
think you want to hear. - “What do you actually do when you see a part that doesn’t look
right?” → The operator tells you what really happens.
People naturally default to describing the formal process when they
feel they’re being evaluated. Your job is to signal that you’re
interested in reality, not compliance. Frame every question around the
actual work, not the documented system.
Principle 4: Follow the
Threads
The most valuable information in a Gemba Interview rarely comes from
your prepared questions. It comes from the unexpected answers — the “by
the way” comments, the offhand references, the things the operator
mentions as if they’re obvious.
When an operator says, “We just smack it with a rubber mallet to get
it to fit,” that’s not a throwaway comment. That’s a thread. Pull it.
“How often does that happen? When did it start? Does it always work?
What happens when it doesn’t?”
A good Gemba Interview is like peeling an onion. Every answer reveals
a new layer. Your prepared questions get you started; your follow-up
questions get you to the truth.
Principle 5: Silence Is a
Tool
In most professional conversations, silence feels awkward. People
rush to fill it. In a Gemba Interview, silence is one of your most
powerful techniques.
When you ask a question and the operator gives you a quick,
surface-level answer, don’t immediately follow up. Wait. Look at them.
Nod slightly. Give them three to five seconds of silence.
What happens next is remarkably consistent: the operator fills the
silence with the real answer. The first response is usually the
rehearsed one — what they think you want to hear. The second response,
prompted by nothing more than patient silence, is the truth.
Principle 6: Never Judge,
Always Learn
The moment an operator senses judgment, the interview is over. They
will tell you what they think you want to hear, and you will learn
nothing useful.
This means: – Never say “That’s not how it should be done” – Never
reference the standard operating procedure as a correction – Never
express surprise or disapproval at a workaround – Never write notes that
look like you’re building a case against someone
Instead, frame everything as genuine curiosity. “That’s
interesting — can you show me how that works?” “I hadn’t thought of it
that way — what made you start doing that?” “Help me understand what
happens next.”
You are a learner, not an auditor. Every workaround exists for a
reason. Your job is to understand the reason, not to eliminate the
workaround without understanding why it’s there.
Principle 7: Close the Loop
After every Gemba Interview, share what you learned with the people
you interviewed. Tell them what you’re going to do with the information.
Follow up when actions are taken. Close the loop.
This is not courtesy — it’s strategy. The single most important asset
in Gemba Interviewing is trust. If operators see that their honesty
leads to improvements, they’ll be honest next time. If they see that
their honesty leads to criticism, blame, or worse — nothing at all —
they’ll give you the textbook answer forever.
One broken promise can destroy years of trust. One followed-through
action can build trust that lasts a career.
The Gemba
Interview Framework: A Practical Guide
Preparation (5 Minutes)
Before you step onto the floor: 1. Define your
purpose. What are you trying to understand? A specific defect?
A process variation? A chronic issue that data hasn’t solved? 2.
Review what you already know. Look at the available
data. Identify the gaps — what the data doesn’t explain. 3.
Identify who to interview. Who works the affected
process? Include operators across all shifts if possible. 4.
Prepare 3-5 seed questions. Not a script — seeds.
Open-ended questions to get the conversation started.
Opening (2-3 Minutes)
- Approach the operator at their workstation. Introduce yourself if
needed. - Explain your purpose honestly and simply: “I’m trying to
understand something about this process, and I think you can help me see
it more clearly.” - Ask for permission: “Do you mind if I watch you work for a few
minutes and ask some questions?” - Emphasise learning: “There are no wrong answers — I’m just
trying to learn how this really works.”
Observation Phase (5-10
Minutes)
Watch the work. Take mental notes. Look for the workarounds,
hesitations, and adjustments described in Principle 2. Let your
observations generate your real questions.
Interview Phase (10-20
Minutes)
Start with your seed questions, then follow the threads. Use these
proven question types:
Descriptive questions — “Walk me through what
you do from start to finish.” Specific questions —
“What exactly happens when you see that warning light?”
Comparative questions — “Is this shift different
from the last one? How?” Hypothetical questions —
“If that fixture was loose, what would you notice first?”
Experience questions — “What’s the most common
problem you see with this operation?” Improvement
questions — “If you could change one thing about this
process, what would it be?”
Closing (2-3 Minutes)
- Thank the operator sincerely.
- Summarise what you heard: “Let me make sure I understood —
you’re saying that…” - Commit to follow-up: “I’m going to look into this. Can I come
back if I have more questions?”
Documentation (5 Minutes)
Write everything down immediately after leaving the workstation.
Memory degrades fast. Capture direct quotes when possible — they’re more
valuable than your interpretations.
Real-World
Example: The Midnight Shift Mystery
A Tier 1 automotive supplier was chasing a chronic weld quality issue
that appeared exclusively on the midnight shift. The data showed higher
porosity rates between 11:00 PM and 3:00 AM. The engineering team
investigated gas flow, wire feed rates, power settings, and material
lots. Everything was identical across shifts. The charts were flat. The
problem persisted.
A quality manager who practised Gemba Interviewing spent one night on
the floor. She didn’t start with charts. She started with a question to
the midnight shift operator: “What’s different about working this
shift compared to the day shift?”
The operator’s answer: “The ventilator behind Bay 7 gets turned
off at 11 because the supervisor says it’s too noisy for the office. But
we need it for the shielding gas coverage. Without it, the cross-breeze
from the loading dock disrupts the gas flow. We mentioned it months
ago.”
Three months of engineering analysis. One conversation. The
ventilator was re-routed. The problem disappeared.
This isn’t an unusual story. It’s the normal result of asking the
right question to the right person in the right place.
Common Mistakes
That Kill the Gemba Interview
Bringing a clipboard. Nothing says “audit” like a
clipboard. Use a small notebook or your phone for notes. Better yet,
write everything after the interview, not during.
Asking leading questions. “You don’t skip the
calibration check, do you?” This is not an interview — it’s a trap.
Ask open questions and let the answer surprise you.
Interviewing in groups. Group dynamics suppress
honesty. The dominant voice sets the narrative, and everyone else
agrees. Interview one person at a time whenever possible.
Rushing. A meaningful Gemba Interview takes 20-30
minutes minimum. If you’re treating it like a five-minute checklist
exercise, you’re wasting everyone’s time.
Only going once. The first interview establishes
contact. The second builds trust. The third gets you the truth. Make
Gemba Interviews a regular practice, not a one-time event.
Talking more than listening. If you’re speaking more
than 20% of the time, you’re lecturing, not interviewing. Your mouth
should ask questions. Your ears should collect data.
When to Use the Gemba
Interview
The Gemba Interview isn’t just for problem-solving. It’s a versatile
tool with applications across the entire quality management
spectrum:
- During APQP — Interview operators from similar
processes to capture lessons learned before designing the new
process. - After a customer complaint — Go to the line where
the defect originated. Ask the operator what they saw, what they
reported, and what happened next. - During process validation — Interview operators
about what they actually do versus what the validation protocol
assumes. - Before an audit — Understand the reality of the
process before the auditor arrives, so you can address gaps
proactively. - During new product launch — Interview operators
during the first production runs to catch issues that the pilot run
missed. - Monthly quality reviews — Dedicate one interview
per month to a different process. Build a library of ground-truth
intelligence.
The Competitive
Advantage Nobody Measures
Here’s what most organisations miss: the Gemba Interview is not just
a problem-solving tool. It is a trust-building tool
that compounds over time.
Every time you show up on the shop floor, ask a genuine question,
listen to the answer, and act on what you learn, you make a deposit in
the trust account. After six months of consistent Gemba Interviews,
operators start coming to you with problems before they become crises.
After a year, they start coming to you with solutions.
That’s a competitive advantage that no competitor can copy, no system
can automate, and no consultant can install in a weekend workshop. It’s
built one conversation at a time, face to face, in the place where the
work actually happens.
Getting Started Today
You don’t need a training program, a certification, or management
approval to start. You need a question and five minutes of courage.
Tomorrow morning, walk onto your shop floor. Pick a process you think
you understand. Find the operator who runs it. Say: “I’ve been
looking at the data for this process, and I feel like I’m only seeing
part of the picture. Can you help me see what I’m missing?”
Then listen. Really listen. Not for what confirms what you already
know — but for what surprises you.
That surprise is where your next breakthrough lives.
Peter Stasko is a Quality Architect with over 25
years of hands-on experience in automotive and manufacturing quality. He
has led QMS implementations, coached hundreds of professionals, and
believes that the most powerful quality tool ever invented is a good
question asked in the right place at the right time.
