Introduction
Your last front-desk hire took the better part of two quarters before she stopped asking basic questions. You told yourself that’s just how long it takes — new job, new software, new patients, give it time. Then the next hire took just as long. And the one after that. At some point “it just takes a while” stops being an explanation and starts being a pattern you’re not questioning.
Here’s the uncomfortable possibility: it’s not taking anyone six months to learn the job. It’s taking six months for you to find out, by accident, everything they never actually understood in week one.
Watching Someone Do the Job Isn’t the Same as Confirming They Understood It
Most practices train new hires the same way: sit them next to someone experienced for a few days or weeks, let them shadow, hand them whatever notes exist, and trust that it sinks in. It feels like training. It’s actually closer to osmosis — you’re hoping proximity does the work that verification is supposed to do.
The tell that this isn’t working is usually invisible for a while, because a new hire who doesn’t fully understand something rarely says so directly. They nod along, do their best to mimic what they watched, and quietly wing it on the parts that never quite clicked. You don’t find out what they missed until it shows up live — a patient given the wrong instructions, insurance verified incorrectly, a claim submitted with the wrong code — and by then it’s not a training gap anymore, it’s a mistake with a real cost attached.
The Fix Isn’t More Time. It’s Actually Checking Understanding Before It Matters.
There’s a simple distinction that changes how fast this goes: instead of asking “does this make sense?” — which almost everyone answers yes to, whether it’s true or not — hand someone a specific scenario and ask them to walk through exactly what they’d do. Not the theory. The actual steps, in order, for a real situation you’ve picked. How they respond tells you immediately whether they’ve actually absorbed the process or are still guessing at it — far faster than waiting to see how they handle the same situation for real, weeks later.
The same logic applies to questions. A new hire who never asks anything isn’t necessarily your fastest learner — often it’s the opposite. If someone has real, specific questions partway through training, that’s usually a sign they’re actually engaging with the material closely enough to notice what they don’t know yet. Silence isn’t confidence. It’s frequently just someone who hasn’t gotten far enough into the material to know what to ask.
And for the first few times a new hire actually runs a process on their own — verifying insurance, checking in a patient, submitting a claim — being nearby to watch, quietly, isn’t hovering. It’s the only way to catch a small misunderstanding before it becomes a pattern, instead of finding out three months in that they’ve been doing one step wrong the entire time.
Try This
For your next new hire, pick three real scenarios they’re likely to hit in their first month — a patient with confusing insurance, a scheduling conflict, a claim with a common denial reason — and walk them through each one directly, asking them to explain back exactly what they’d do, before you ever let them handle it live. Then be present, quietly, the first two or three times they actually do it for real, not to hover, but to catch anything the scenario walkthrough didn’t surface.
Most of the six-month ramp time isn’t learning curve — it’s the gap between when a misunderstanding actually happened and when you found out about it. Close that gap with real scenarios and real verification up front, and you’ll usually see a new hire operating independently in weeks, not months.
