Peer-reviewed by Dr. Abdolghader Pakniyat

Introduction: The Chaos We Think We Know

Picture a hospital Emergency Department (ED) late at night. The scene is one of controlled chaos: triage is overwhelmed, a mother is crying in the packed waiting room, and the staff are visibly frustrated. When faced with this kind of systemic stress, our first instinct is often to demand more—more staff, more beds, more resources. The problem, we assume, is a lack of inputs. This is a classic reaction that focuses on inputs rather than the throughput of the system itself.

But what if the problem isn’t about resources at all? A recent presentation on Quality Improvement (QI) by Dr. Sabrina Berdouk, a Consultant in Emergency Medicine, offers a different, more powerful perspective. It suggests that the most effective solutions come not from adding more to a broken system, but from fixing the underlying process. The lessons from her work reveal a smarter, more effective approach to problem-solving that can be applied far beyond the hospital walls.

1. No Hunting for Data, but Start With a Real Problem.

In a world driven by metrics, the first step in any improvement project is often to open a spreadsheet. The first lesson flips this convention on its head. Effective improvement doesn’t begin by analyzing abstract data points, but by identifying a tangible, often painful, real-world problem.

This could be a catastrophic event, like a patient presenting with subtle neurological deficits that were not recognized. Because no CT was obtained in time, the patient deteriorated rapidly, suffering a catastrophic neurological injury and, ultimately, death in the ICU. Or it could be a chronic, grinding issue, such as an overwhelmed waiting room where a growing number of patients leave without being seen (LWBS). These are not just numbers on a chart; they represent significant failures in care and efficiency.

QI does NOT start with data. It starts with a PROBLEM

Starting with a human-centered problem, rather than a sterile metric, provides a powerful and unifying “why” for the entire team. It frames the mission not as hitting a target, but as preventing harm and alleviating frustration, which is a far more powerful motivator for change.

2. Your Biggest Problem Probably Isn’t Staffing—It’s Flow.

When delays mount, the most common refrain is, “We’re understaffed.” But the case study presented shows that this is often a symptom, not the root cause. Using the “Ask ‘why’ five times” technique to investigate high Door-to-Doctor Times (DTD), the team dug deeper.

The team asked, “Why is Door-to-Doctor time high?” The answer: because a high volume of low-acuity (less severe) patients were in the same queue as critical ones, meaning high-acuity patients were competing for space with simple cases. They asked again: “Why are they in the same queue?” Because they all followed the same rigid pathway from triage to the waiting room to a doctor. This disciplined questioning revealed that the root cause wasn’t a lack of doctors, but a lack of a differentiated process.

The core finding was clear: “The problem wasn’t staffing — it was flow.” The solution wasn’t to hire more doctors to manage the single, clogged pipeline, but to redesign the process itself by creating a dedicated “Fast Track” stream to handle simpler cases quickly and efficiently.

3. Test Big Changes in Small, Manageable Slices.

Redesigning a core process can feel daunting, and the idea of a massive, department-wide rollout is often met with fear and resistance. The third lesson demonstrates a more practical path forward: implement “small tests of change.”

Instead of overhauling the entire ED at once, the Fast Track concept was piloted in small, manageable experiments. The team started with a 1-day pilot and tested the workflow with just one shift, but also experimented with other variables, like placing senior staff in triage or ensuring leaders were present to provide support during peak times.

This incremental approach minimizes risk. If a test fails, the impact is small and the lessons are learned quickly. If it succeeds, it builds confidence and provides concrete evidence to win over skeptics. This strategy makes ambitious ideas achievable by breaking them down into low-risk, iterative steps, perfectly embodying the core advice from the presentation:

Don’t pilot with the whole department- pilot with one shift

4. Turn Resistance Into Ownership.

Any significant change to a workflow will inevitably encounter the human element: resistance. Staff members in the ED were understandably concerned, voicing fears like, “Fast Track will increase workload.” This step, which Dr. Berdouk calls “Navigating Resistance” in her framework, is critical—a brilliant process on paper can fail completely if the people who must execute it aren’t on board.

The key to overcoming this is engagement, not enforcement. The leadership team in the case study addressed this directly by:

• Providing hands-on support: Leaders were physically present during the initial shifts to help troubleshoot and demonstrate commitment.

• Sharing early wins: As soon as the data showed Door-to-Doctor times dropping, that positive feedback was shared widely with the team.

This approach transformed skepticism into enthusiasm. When the staff saw the new process making their work more effective—with crowding decreased in the main ED and both staff and patient satisfaction improving—their resistance naturally evolved into a sense of pride and investment. The powerful outcome was that “Resistance transformed into ownership.” By transforming resistance into ownership and formally rewarding the team for the new process’s success, leadership solidified the change and created a culture of continuous improvement.

Conclusion: From Data to Dignity

Meaningful, sustainable improvement is rarely about bigger budgets or larger teams. It’s about a fundamental shift in perspective. It’s about moving from abstract data to tangible problems, from blaming staffing to analyzing flow, and from imposing top-down mandates to empowering teams to test small, intelligent changes.

This approach doesn’t just improve efficiency; it transforms the experience for everyone involved.

When we transform data into decisions, we don’t just improve metrics. We restore dignity, speed, and safety to the patients who trust us — and to the teams who give everything for them.

What is one frustrating bottleneck in your own work that exists not because of a headcount problem, but because of a flaw in the flow?