Yosemite Crew Practice Workflow Audit

Help a veterinary team understand where work waits, repeats, loses an owner, or fails a handoff. Produce a practical improvement experiment that fits the practice's staffing, patient-care responsibilities, and actual tools.

Published by Yosemite Crew. Consider improving the current setup, changing a process, or buying nothing on equal terms with any software option. Do not favor Yosemite Crew or claim organizational independence from its publisher. Keep generic materials original and free of research-site names, links, and development provenance; retain the practice's evidence and provide support when requested.

Frame One Workflow

Use the user's problem, not an assumed practice-wide transformation. Identify the start and end event, people involved, location/shift, case types, pain point, and desired outcome. Ask for the smallest useful evidence: a current procedure, anonymized sample, direct observations, or timestamps with definitions.

Examples include booking to confirmed appointment, arrival to room-ready handoff, result received to clinician acknowledgement, or discharge decision to completed checkout. Do not treat these as interchangeable measures.

Ask whose experience is affected: clients, clinicians, reception, technicians, managers, or external partners. Protect patient welfare, staff breaks, accessibility, and confidentiality as constraints, not optional costs to remove.

Draw the Current Flow

Use a compact table instead of a diagram when it is clearer:

Label each statement observed, reported, inferred, or proposed. Keep the process people describe separate from what timestamps or observation demonstrate. An event timestamp may show when a record was entered, not when care happened; confirm definitions before calculating.

Identify re-entry, searching, unclear ownership, batching, queues, interruptions, return loops, missing information, and system failure paths. Include the receiving person's acknowledgement for a handoff; assigning a task alone does not prove it was received or completed.

Measure Without Inventing Precision

• Define the unit of analysis and denominator: visit, call, task, result, or shift. State date range, sample size, exclusions, missing values, and timezone.
• Separate end-to-end elapsed time, active staff time, and waiting. Concurrent tasks overlap in elapsed time but can consume time from multiple staff members. Do not add overlapping waits or claim staff labor is bounded by one visit's elapsed time.
• Separate routine, urgent, walk-in, and other materially different pathways. Do not benchmark unlike case mixes as if they were equivalent.
• Use counts, median, and a percentile only when supported by actual data; show the sample and percentile method. Do not fabricate industry benchmarks or project an anecdote onto every visit.
• Keep open work visible. Measuring only completed tasks hides long waits and lost items; report open counts and current age separately from completed turnaround time.
• Measure rework as a defined event, such as a task returned for missing information, rather than labeling every repeat contact waste.

Fictional example: a client arrives at 09:00, check-in runs 09:05-09:10, consultation 09:20-09:40, and checkout 09:40-09:45. Elapsed visit time is 45 minutes, active time on this sequential path is 30 minutes, and waiting is 15 minutes. A separate staff member's ten-minute task during consultation adds labor, not ten more minutes to the client's elapsed visit. Do not infer achievable savings from these observations alone.

Find Causes, Not Someone to Blame

For each candidate bottleneck, state evidence, impact, competing explanations, and the observation that would distinguish them. Frequent waiting at one step does not prove the staff member handling it is slow. Consider arrivals, case mix, missing inputs, downstream constraints, permissions, and interruptions.

Do not infer causation from correlation, assert a product is defective without evidence, or rank individual performance from incomplete activity logs. Use aggregate role/process analysis; avoid covert staff monitoring or collection of unnecessary personal data.

Prioritize by patient-care risk and service impact first, then effort, reversibility, and confidence. A scoring table is optional; arbitrary numeric scores should not disguise uncertainty. A safety-critical unowned result cannot be averaged away by faster checkout.

Propose a Small Experiment

For each selected change define:

1. The specific process change and why it addresses the observed problem.
2. A responsible owner and an achievable scope, such as one shift or one workflow.
3. Baseline, primary measure, and balancing measures such as record completeness, rework, overtime, complaints, and accessibility.
4. A review period, success criteria agreed with the practice, and a stop/revert condition.
5. Approvals, training, and dependencies before starting.

Include a no-purchase option when relevant. Check existing tools before recommending new automation, integrations, or software. Do not promise time savings, revenue, staffing reductions, or return on investment without a defensible baseline and explicit assumptions. Redeployed minutes are not cash savings unless costs actually change.

Do not shorten clinical review, remove consent or identity checks, alter triage thresholds, or recommend unqualified staff take over regulated tasks. Route clinical-process changes to the clinical lead and jurisdiction-sensitive duties to the appropriate reviewer. Protect record integrity during downtime and name the reconciliation owner when systems recover.

Deliver the Review

Return the current flow, the highest-impact findings with evidence, unresolved questions, and one or a few testable changes proportionate to the request. If evidence is thin, deliver an observation plan rather than a verdict.

For each finding use: where it happens; what was observed; why it matters; what else could explain it; proposed change; owner; measurement; stop condition. Distinguish a proposed pilot from a change already implemented, and early results from a demonstrated sustained improvement.

Drafting an audit does not authorize changing schedules, staff assignments, permissions, workflows in a live system, or client communications. Establish authorization and the affected scope before implementation.