The Questions Always Come First

The unit secretary calls the help desk at 7:14 a.m. on a Tuesday. She’s locked out of Epic. She didn’t get the email. She doesn’t remember the password she set last week. She’s holding a newborn’s wristband and needs to print a label. The analyst on the other end has already fielded seven of these calls this morning. They give her the reset link again. She thanks them. They hang up. The secretary doesn’t say it, but she’ll forget again next week. And the week after that. And the next time MFA rolls out.

This isn’t a failure of training. It’s not even a failure of communication. It’s the predictable consequence of deploying a new system without pre-writing the answers to the questions people will ask. The same ten questions appear in every hospital, every time: How do I reset my password? Why won’t my phone accept the code? Where’s the app? Why does it keep asking for my ID? Why can’t I log in from home? Why does it say ‘device not enrolled’? Why did I get locked out after three tries? Why is this taking so long? Why can’t I use my personal tablet? Why does it say ‘untrusted device’?

These aren’t edge cases. They’re the baseline. They’re the first thing people notice when something changes. And every rollout — MFA, SSO, device enrollment, conditional access — triggers the same wave. The help desk doesn’t get more staff. The analysts don’t get more time. The preceptors don’t get a pause. The questions arrive in a rush, and the answers are improvised on the fly. By the time someone writes them down, the spike has passed. The next rollout starts with the same blank page.

That’s not efficiency. That’s attrition.

The objection is simple: You can’t predict what people will ask. Every unit is different. Every workflow breaks in its own way. What works on the telemetry floor won’t help the ED. What the pharmacy tech needs is not what the lab tech needs. And you can’t write answers for every edge.

That’s real, and I won’t wave it off. The truth is, most of these questions aren’t about the system. They’re about the rhythm of the shift. The charge nurse isn’t asking how to authenticate — she’s asking how to log in before the 7 a.m. handoff. The registrar isn’t troubleshooting MFA — she’s trying to avoid a 15-minute delay before the first patient walks in. The pharmacy tech isn’t confused by the app — they’re running between med rooms with a cart full of antibiotics and no time to read a manual.

The real problem isn’t that people forget. It’s that we treat forgetting as a personal failure, not a system design flaw. We blame the user for not reading the email. We assume the training was inadequate. We schedule another webinar. We send another reminder. And then we’re shocked when the same call comes in again.

What if we stopped assuming they’ll remember? What if we assumed they’d forget — and built the answer into the moment they need it?

Pre-write the answers to those first ten questions. Not the polished, compliance-approved version. The version that fits in a text message. The one that says ‘Restart your phone. The button doesn’t work if the screen’s damp.’ Not ‘Enable biometric authentication per HIPAA guidelines.’ The charge nurse doesn’t care about guidelines. She cares that her thumbprint won’t scan while holding a syringe.

Write them in the voice they use. Use the words they say. ‘Click the link in the text’ is better than ‘Authenticate via the push notification protocol.’ ‘Use your work phone, not your personal one’ is better than ‘Enroll a trusted device per policy.’

Then track it.

Measure which of those pre-written answers actually get used. Not how many times they’re viewed. Not how many clicks they get. But which ones get referenced when the question comes in again. The help desk logs every call. Every ticket has a resolution note. Go back. After the first rollout, look at the next 100 tickets that say ‘MFA issue’ or ‘SSO login failed.’

Find the ones where the analyst typed: ‘See KB article 204.’

Find the ones where they typed: ‘Call the help desk, I’m not sure.’

The difference between those two is the difference between a rollout that drains morale and one that feels manageable. The first one has a living answer. The second one has a guess.

Solution Compass exists to handle that last part — the answer has to surface in the words the person used, not the words the document used. If the charge nurse searches for ‘phone won’t let me click verify,’ the system doesn’t return a PDF titled ‘Multi-Factor Authentication Policy v3.1.’ It returns the note someone wrote after the third call on Monday: ‘Try restarting your phone. The button sometimes doesn’t respond if the screen is wet.’

That’s not a feature. That’s a habit.

The next rollout won’t feel like triage if you’ve already written the answers. Not because you’re smarter. Not because you’re better prepared. Because you’ve stopped pretending the questions are surprises.

The unit secretary will still call at 7:14 a.m. She’ll still be holding the wristband. She’ll still be frustrated. But this time, the analyst won’t have to guess. They’ll just paste the note. And the secretary will say, ‘Oh, right. I forgot about that.’

And then she’ll forget again. But not because the answer wasn’t there. Because she didn’t need to remember it. It was already waiting — in the words she would use, for the moment she was in.

The drawer is still full. But now, the paper inside has a URL.