Going to the Gemba: Beyond Boards and Status Updates
Going to the gemba means visiting the actual place where work happens to observe and learn with the people doing it. A gemba board can help you discuss performance and problems, but reviewing that board is not the same as understanding the work. The distinction matters when a busy schedule turns a visit into a quick status report.
In the Lean methodology, one of the most well-known–and most misunderstood–practices is the “Gemba walk.”
Here's the short video version of this argument, if you'd rather watch than read.
The word Gemba means “the actual place.” It's where the actual work happens. In healthcare, that might be a hospital unit or a laboratory. In manufacturing, the assembly line. In tech, the developer's room. Wherever your value is created, that's your Gemba.
The purpose of going to the Gemba is to learn. To understand. To support. But far too often, Gemba walks become something else entirely: a tightly scheduled tour of metrics, boards, and scripted conversations.
When that happens, we risk missing the very thing we came to see.
What a Gemba Board Can and Cannot Tell You
In many organizations, Gemba walks have become synonymous with reviewing visual boards:
- KPI charts,
- huddle metrics,
- kaizen improvement tracking, or
- A3 updates.
And to be clear, these boards can be helpful–when they're alive, evolving, and connected to real improvement conversations.
But when a leader's visit becomes only about what's on the board, we've lost the thread.
I once shadowed a leader on a Gemba walk who spent a full minute reviewing whether today's numbers were green or red. He listened to status updates. He nodded, asked if the board was up to date (it was), thanked the team, and moved on. The walk was “on schedule.”
I did not hear a problem explored or see the conversation move from the numbers to the work behind them. The board was up to date, but the visit gave the team little opportunity to discuss what help they needed.
Gemba Isn't a Performance
Here's the irony: the more we treat the Gemba as a quick audit or status update, the more our teams feel pressure to make things look good rather than be real.
If leaders are in a rush, people learn to rehearse their lines. They present polished boards. They give safe answers. They protect their time–and their credibility–by keeping things surface-level.
That's not a high degree of Psychological Safety. That's compliance.
Leaders sometimes say they want a culture of continuous improvement, but the behavior we model in our Gemba visits tells a different story. If we're performing a Lean ritual instead of having a Lean mindset, our people notice.
The Schedule Problem: No Slack, No Space, No Substance
Another issue is time. I've seen Gemba walk agendas where leaders are scheduled to visit five or six departments in an hour. Each stop is slotted for 10 minutes. The route is mapped, the teams are prepared, the clock is ticking.
What if something important comes up?
What if a nurse says, “Actually, we've been really struggling with the new handoff process…” and it's minute nine?
What if someone hints at a patient safety issue, but the next huddle is starting in two minutes?
We often preach the value of slack in systems–that overburdened people can't do quality work.
But do we allow slack in our leadership systems? Or are we so focused on efficiency that we forget effectiveness?
Real conversations require space. The messy stuff–the valuable stuff–doesn't follow a script. If we're too tightly scheduled to stay and dig deeper, we're not leading. We're scanning.
You might not want to get caught looking at your watch:
What Effective Gemba Looks Like
So what does a meaningful Gemba walk look like?
It starts with mindsets:
- Curiosity over confirmation
- Listening over judging
- Presence over performance
It continues with time:
- Leave slack in your schedule. Don't put yourself in a position to constantly feel rushed.
- Build in “stay time.” If a conversation is rich, stay with it. Let people know they're worth your time.
And it thrives with better questions:
- “What's one small frustration you've been dealing with this week?”
- “What's something we keep putting a Band-Aid on instead of fixing?”
- “Where are we getting in our own way?”
- “How safe do you feel bringing up problems here?”
Questions are only a start. People also notice what happens after they answer: whether you listen, act on a concern, or explain why you cannot. Asking about psychological safety once is not enough to establish it.
Going to the Gemba: Follow Through After the Visit
Use the board to identify a question worth exploring, then ask someone to show you the relevant work. What makes the task difficult? Where does it wait? What workaround has become routine? Observe with permission and avoid interrupting work that needs someone's full attention.
Before leaving, agree on who will follow up and when. If you cannot resolve a concern during the visit, say what you will do next. Returning with an answer, even an explanation of a constraint, helps people judge whether raising the issue was worthwhile.
An audit can have a legitimate purpose: checking whether requirements are met. Be clear when that is what you are doing. A learning visit asks how the work functions and what support people need; treating every visit as a compliance check can make those conversations harder.
Related reading: visual management examples and the response behind the display, gemba vs. genba and the meaning of the term, and subtle reasons people stop speaking up.
Read a sample before deciding
Healthcare Kaizen offers examples of engaging people in everyday improvement. Read a sample to consider how the approach could support your team.
Related Post:
Thank you so much for this article. It is very timely reinforcement of some of the positive intention, time, and humility our leaders are displaying. It’s not easy to keep doing though, which is why I really appreciate hearing the importance of these concepts from a trusted voice in the field. Thanks especially for using healthcare examples in the article! It makes it more relevant and meaningful for our leaders.
Thanks for reading and for sharing your thoughts, Caitlin!