The Dashboard Is Not the Ground Truth

Go and see for yourself

Taiichi Ohno, father of the Toyota Production System

Patient records were taking too long to move from our Emergency Department (ED) to the Operating Theater (OT) — yet no one had flagged it as a problem, because on paper, nothing was broken. It took a Gemba walk to surface the issue. A limitation in our Hospital Information System required a patient's ED record to be fully logged and closed before it could transfer to the OT. In an emergency department, where stabilizing a patient often takes priority over documentation, that meant care itself could occasionally be delayed by administrative rules embedded in the system.

A quick discussion with our VP of Information Technology led to a workaround within a week: simultaneous logging. Obstacle removed. Had we not been standing in that department that morning, asking open questions and observing the work firsthand, I doubt anyone would have connected the dots between "administrative burden" and "patients waiting."

That, in one story, is the value of a Gemba walk. The solution wasn't a new strategy. It was identifying a broken system that no one had examined closely enough to see.

Early in the hospital's journey, we realized that a newly opened institution accumulates small operational gaps faster than reports can capture them. Rather than wait for issues to escalate, we built a daily rhythm of observation into our leadership routine. Since January 2026, my Hospital Director and I have conducted daily Gemba walks. On a rotating schedule through the week, we spend an hour each day in a different part of the hospital: inpatient services, outpatient services, allied health, service areas such as concierge and the business office, and support functions including facilities management and environmental services.

We ask managers and frontline staff simple questions — what's getting in your way, what's taking longer than it should, what would you change if you could — then discuss potential solutions, agree on ownership, and return later to review progress.

Three lessons from this practice have mattered more than I expected.

Ground truth beats chain-of-command truth

Every reporting structure filters information — not because people are dishonest, but because they must constantly decide what's worth escalating and what can be managed locally. Over time, that creates blind spots. Middle managers, particularly those still developing confidence in their role, often absorb issues rather than raise them: sometimes trying to solve the problem themselves, sometimes assuming it isn't important enough, sometimes simply not realizing the issue extends beyond their own department. Gemba walks bypass that filter, and not just for the issues managers are sitting on — we've uncovered issues they genuinely couldn't see from within their own scope.

An ortho-neuro clinic handling large volumes of implants faces very different procurement and vendor-pricing challenges than a maternity clinic does, for instance. Each manager naturally optimizes for the realities of their own environment, so cross-departmental inconsistencies, duplicated work, and conflicting practices tend to stay invisible unless someone is deliberately connecting the dots across the organization. Those blind spots rarely appear in reports. They emerge only when leaders spend time where the work is actually happening.

Presence is what earns trust — fixing things is what keeps it

Junior staff have good reason to hesitate before raising concerns to senior leadership. The day-to-day realities of a frontline employee and the priorities of a senior executive can feel worlds apart, and even approachable leaders can seem distant simply by operating several layers removed from the work. Showing up regularly helps bridge that gap, but presence alone isn't enough — what actually builds trust is employees seeing that their concerns lead to action. The ED-to-OT fix mattered not simply because it was resolved, but because staff watched a problem they'd lived with turn into a solution within a week. Employees pay less attention to what leaders say than to what leaders consistently do, and that single fix sent a stronger signal about what leadership values than any town hall presentation could have.

Gemba is also how you evaluate the people leading beside you

A third benefit is often overlooked: Gemba walks are one of the most effective leadership assessment tools I've encountered. In a newly opened hospital, particularly one built from leaders recruited across multiple organizations, it can be difficult to accurately assess management capability through interviews, reports, or meetings alone. Walking the floor changes that — you see how managers respond when problems surface unexpectedly, how they listen, how they think through solutions, how they react when weaknesses in their own department are exposed in front of their own team. Leadership quality often stays hidden during routine operations and only becomes visible when confronted by a real problem in real time.

Over time, Gemba walks have become one of the most reliable ways for us to identify future leaders, understand coaching needs, and tell the difference between a manager building a resilient team and one merely managing day-to-day activity.

Reports tell you what happened. Gemba helps you understand why. A daily, disciplined practice as simple as walking the floor has told us more about how our hospital actually runs than any report ever has. It's a small operational habit, but it points at something larger: the systems that determine whether an institution works are rarely visible from a desk. You have to go and look.