Workflow Shadowing, Systems Audit, and a Scope You Can Hold Us To
Discover is where most projects quietly save their own budget. Two weeks of structured listening produces the written scope every later phase leans on.
What Happens in Discover
The phase in one sentence, then the mechanics.
We start in your operation, not in a slide deck. The team shadows front-desk workflows, watches how patients actually move from inquiry to visit, and audits the systems you already run, including the spreadsheets doing unofficial work. Baseline metrics get captured the same week: call patterns, booking conversion, no-show rate, intake completion, and staff hours on the tasks that hurt. Nothing in this phase changes your operation. Everything in this phase changes what the next four phases can honestly promise, because building on measured reality is the only way a roadmap survives contact with a live practice.
Workflow shadowing. <div> We watch the real process, including the workarounds, because those are the requirements nobody writes down.
Systems audit. <div> Every system touching patient flow is inventoried, from the EHR to the spreadsheet nobody admits owns the recall list.
Baseline metrics captured. <div> The numbers that will prove success later are recorded now, before anything changes.
Stakeholder mapping. <div> Who owns which decision at your practice gets named, which prevents the approval stalls that kill timelines.
Written scope produced. <div> The phase ends with a scope document both sides sign, and the price on it is the price you pay.
What This Phase Produces
Concrete outputs you will see, not abstract promises.
Operational Observation
Structured shadowing across front desk, clinical coordination, and billing touchpoints, documented as workflow maps.
Systems Inventory
Every platform, interface, and unofficial spreadsheet catalogued with its real role in patient flow.
Baseline Capture
Call patterns, conversion, no-shows, intake completion, and staff hours recorded as the comparison point.
Stakeholder Sessions
Short interviews with the people who will live inside the new system, so adoption starts in discovery.
Scope Document
A written scope with deliverables, exclusions, and fixed phases, signed before planning begins.
Compliance Groundwork
Data flows inventoried and compliance requirements captured, so Plan designs against reality.
The Phase Step by Step
How the weeks actually spend themselves inside this phase.
Kickoff and shadowing
Week one in your operation: workflows watched, questions asked, assumptions listed.
Systems and data audit
Platforms, interfaces, and data flows documented, including where PHI actually travels today.
Baseline metrics
Your operational numbers captured with definitions agreed, so after-numbers compare cleanly.
Scope gate
The written scope is reviewed and signed, and the roadmap moves to Plan with a fixed target.
Frequently Asked Questions
Straight answers for practice owners evaluating software discovery.
Do we need to prepare anything for discovery?
Only access and honesty. The team needs time with your staff and your systems, and the most valuable input is the unfiltered version of how work really happens.
How disruptive is shadowing?
It is observation, not interference. Sessions are scheduled around your peak hours, and most practices forget we are there by day two.
Who owns the scope document?
You do. The scope, metrics, and workflow maps are yours to keep regardless of whether the engagement proceeds, because they document your operation.
What if discovery uncovers problems outside project scope?
We document them and flag them honestly. Fixing them is your call, and sometimes the right answer is a smaller project than you originally wanted.