Jun 23, 2026
Written By Elizabeth Cifers
Most clinics have a working definition of a “flow problem.” It usually involves something obvious: an overbooked schedule, a physician arriving 45 minutes late, or a waiting room that starts to resemble an airport during a weather delay. Those are easy issues to identify.
But not all flow problems are that obvious. Many lurk in the shadows instead of announcing themselves.
The schedule is full, but not unreasonable. The team is moving, the patients are being seen, and no one is dramatically behind. If you asked whether there is a flow issue, the answer would probably be no. Or at least, not really.
And yet, the day feels behind, more difficult, or more demanding than it should.
There are clinic days when nothing feels especially smooth. Patients move through the clinic, but there are delays along the way. Testing is backed up because the physician was on a call when the fluorescein needed to be pushed; the several workup lanes are missing occluders (where did they all go?); the betadine swabs are not in the exam room; and the portable indirect wasn’t put back on the charger to charge. You know these days. And they are challenging to say the least.
None of these moments stand out individually. These things happen. They are also disruptive.
That disruption is where flow slowly starts to erode.
What makes these disruptions so difficult to identify is that they rarely seem catastrophic in real time. No single missing item, delayed test, or interrupted workup seems large enough to explain why the clinic suddenly feels heavier by 10:30 am. Yet retina clinics are operational ecosystems built on sequencing, timing, and momentum. Once enough small interruptions accumulate, the clinic begins operating in a constant state of recovery rather than progression.
And recovery mode is exhausting.
The issue is not simply that one patient waited an extra ten minutes for imaging. Every delay creates secondary delays. The physician pauses in one room, waiting for a test, which delays the next exam, which delays the injection patient who was already prepped, which delays checkout, which delays the technician trying to room the next patient because there is nowhere to put them. Meanwhile, someone is searching for a charger for the indirect, which absolutely should have been charging two hours ago.
This is how clinics become busy without becoming productive.
Most practices evaluate flow by looking for major bottlenecks:
Those certainly matter. But in many retina clinics, operational strain is usually less from one catastrophic failure and more from what could best be described as “death by 4,000 tiny interruptions.”
The printer jams.
The OCT won’t upload the images to the repository.
The technician has to leave the room twice to find supplies.
A patient was prepped for the wrong eye.
The consent form somehow disappeared between when the patient signed and when the physician was ready to perform the injection.
The scribe, who is also an interpreter, is with another physician, and the patient’s daughter didn’t accompany them today.
None of these events, on its own, disrupts clinic flow. Together, however, they create operational friction that slowly consumes time, focus, and mental bandwidth. All. Day. Long.
And, unlike obvious delays, micro-interruptions often become normalized. Staff adapts to them, and physicians work around them. Everyone develops small compensatory behaviors to keep the clinic moving. And once adaptation becomes routine, dysfunction begins looking like normal operations.
One of the more interesting things about retina clinics is how extraordinarily resilient the staff usually is. Pivoting is what they do, and do well. Retina teams can compensate for almost anything for surprisingly long periods. In fact, many clinics continue to function reasonably well despite systems held together primarily by caffeine, institutional memory, and one technician named Heather, who apparently knows where everything is at all times.
The problem is that adaptation hides operational weaknesses.
If the clinic relies on experienced staff to constantly compensate for broken processes, the workflow is not actually stable. It is surviving on human effort. Those are not the same thing.
At that point, many practices assume they need more staff. Sometimes they do. But sometimes the clinic experiences too many operational interruptions, each stealing small amounts of time from many people at once.
This is where many operational reviews miss the real issue. The goal of flow is not to move people through the building faster, like luggage on a conveyor belt. Retina is too clinically complex for that kind of thinking.
The goal is to minimize unnecessary friction.
A smooth clinic is not necessarily a quiet or slow one. In fact, some of the highest-volume retina clinics operate remarkably smoothly because the workflow is predictable, supplies are available, communication is consistent, and interruptions are minimized before they become operational problems.
In other words, the clinic is not spending the entire day recovering from preventable disruptions.
The true cost of poor flow shows up in staff fatigue, physician frustration, operational inconsistency, and the strange phenomenon in which everyone worked nonstop all day, yet still somehow feels behind.
Which, in retina, is usually the first sign that the problem is not the people, but the friction.
A clinic can continue operating while still being operationally strained. ECC helps retina practices understand why.
Real-world education in retina documentation and coding for physicians, fellows, administrators, and billing teams.
👉 https://course.elizabethcconsulting.com/
.png)
