Diagnose before prescribing.
We do not recommend a single tool, hire, or workflow change until we have observed the practice in operation and measured what is actually happening.
THE METHOD
The discipline of diagnosing a practice the way you diagnose a patient.
Most operations consulting fails for the same reason prescribing without diagnosing fails in medicine: the prescription targets a symptom, not the cause.
A practice with revenue leakage gets sold a billing platform. A practice with handoff friction gets sold a CRM. A practice with chart-closing delays gets sold an AI scribe. The tools arrive, the symptoms remain, and the practice is now paying for software it doesn't fully use.
Steady Flow borrows your clinical discipline directly, because it is the right discipline for this work. We listen, observe, measure, assess, and only then prescribe a plan. Software is introduced only after the manual process is working and proven.
S — Subjective
What people report.
Before we measure anything, we listen. The goal is to understand the practice as the people in it experience it: what they think is working, what frustrates them, where decisions get stuck, who actually makes which calls.
The deliverableAn operational narrative and a role-and-decision map covering every service line.
O — Objective
What we observe and measure.
What people report and what actually happens are rarely identical — not because anyone is misrepresenting, but because we all normalize our own routines. In this phase we shadow the practice, time the work, and capture the 'before' baseline in numbers.
The deliverableA set of process maps and a baseline metrics scorecard — the practice's operational vital signs, captured today, against which every change will be measured.
A — Assessment
What is going on, and what matters most.
We take the subjective reports and the objective data and diagnose the underlying causes — not just the symptoms. Then we prioritize ruthlessly. Of every issue identified, which twenty percent of fixes will eliminate roughly eighty percent of the daily friction, errors, or lost time?
The deliverableA diagnosis report with a prioritized issue list and a quick-wins memo.
P — Plan
Build the manual process. Prove it works.
We do not introduce technology in this phase. We design the new workflows, train the staff on them, run them in real operations, and re-measure the baseline metrics from the Objective phase. We need to see the numbers move before we recommend any tool.
The deliverableA set of one-page SOPs, trained staff, and a post-implementation metrics report showing whether the new workflows are moving the baseline in the right direction.
Three principles guide every engagement.
Manual before digital.
A process that works on paper will work better in software. A broken process automated is a broken process at scale. We design and prove the workflow with people first, then digitize what has earned the right to be digitized.
Focus on the vital few.
We use the 80/20 principle in Assessment: the twenty percent of issues that drive eighty percent of the friction, errors, or lost time. We fix those first and re-measure before adding more.
What this is not.
It is not a software sales pitch.
We are vendor-agnostic. We earn no commissions on tools we recommend.
It is not a top-down restructuring.
The people who do the work participate in designing the new process.
It is not all-or-nothing.
Each phase ends in a written deliverable you accept before the next begins. You may pause or end the engagement after any phase.
When this engagement is not the right fit.
In the spirit of honest scope-setting, we recommend deferring this engagement if any of the following are true:
- The practice is in the middle of an active EHR migration or major systems change.
- There is a known compliance audit underway or imminent.
- A leadership transition is in progress within the practice management team.
- The practice is absorbing a recent acquisition or major expansion of service lines.
Stable operating conditions are required for the diagnostic phase to be reliable. If any of the above apply, we will say so before contracting.
About
Steady Flow is led by David P. Chan. He spent his career inside founder-led companies — building revenue, fixing operations, taking responsibility for what didn't work yet. He started this firm to formalize what he has been doing inside other people's businesses for twenty years.