The Unanswered Question Is the System’s Best Diagnostic

It’s 10:17 a.m. on a Tuesday. The charge nurse pulls up the shared drive folder labeled 'IV Push Protocols - Final 2021' and clicks through three subfolders before finding a PDF that says, 'See Pharmacy for current guidelines.' They close it. Walk to the med room. Five minutes later, they’re on the phone with the pharmacy tech, asking which vial to draw up for a patient on renal replacement therapy. The pharmacy tech says, 'We don’t have a written one. We just use the old one until someone says otherwise.' The charge nurse writes it down on a sticky note and tucks it into the pocket of their scrubs.

That sticky note isn’t a mistake. It’s a map. It’s the only record that exists of what actually happens when the official system fails to deliver. The question wasn’t asked in a training module. It wasn’t submitted through a feedback portal. It wasn’t even typed into the EHR. It was spoken, then written, then carried — not because someone was being rebellious, but because the patient needed it now, and the system didn’t.

Most systems treat unanswered questions as failures. They’re not. They’re instrumentation. They’re the exact point where knowledge stopped moving. The charge nurse didn’t ask because they were lazy. They asked because they had no other option. And when they couldn’t find an answer, they built one — on a sticky note. That’s not shadow documentation. That’s the system revealing its own gaps, in real time, in the language of the people who live in it.

The most valuable output of any knowledge system isn’t the number of documents uploaded. It’s the number of questions that can’t be answered. Those questions are demand-weighted. They’re not random. They’re the result of repeated, urgent, real-world need. Every time someone says, 'I don’t know where to find this,' they’re not being inefficient. They’re telling you where the system failed them — and where it needs to improve.

I’ve watched this happen in units with dozens of staff, in hospitals with full knowledge teams, in systems that claim to be 'learning organizations.' The same question gets asked again and again — by the preceptor, by the unit secretary, by the pharmacy tech — each time with slightly different phrasing, each time met with silence. No one compiles those questions. No one maps them. No one says, 'This is the same gap, asked 17 ways.'

That’s not a knowledge problem. That’s a leadership problem. It’s the belief that if something isn’t in a document, it doesn’t exist. But knowledge doesn’t live in documents. It lives in the gaps between them — in the questions that keep coming back, in the workarounds that become rituals, in the sticky notes that get passed from shift to shift.

Some will say, 'But we can’t scale sticky notes. We need standardization.' That’s real, and I won’t wave it off. If you treat every workaround as a violation instead of a signal, you’re not enforcing compliance — you’re silencing the only feedback loop that’s still alive. You’re not fixing the system. You’re punishing the people who are trying to keep it from collapsing under its own weight. The problem isn’t the sticky note. The problem is that the system didn’t give the charge nurse a better way to get the answer — and then didn’t learn from the fact that they needed one.

The solution isn’t to ban the sticky note. It’s to make sure the question that produced it gets captured, surfaced, and acted on. That’s not about better search. It’s about better listening. It’s about recognizing that the moment someone says, 'I don’t know where to find this,' is the moment the system should be triggered — not to send them to a help desk, but to ask, 'Why didn’t you already know?'

I’ve seen systems that track every click, every login, every document download — but never track the question that made someone stop clicking. They measure activity, not insight. They assume that if a document exists, it’s being used. They don’t notice when it’s being ignored — or worse, when it’s being replaced.

The charge nurse didn’t need a new policy. They needed a way to know, in the moment, what to do. And when the system couldn’t give them that, they improvised. That’s not defiance. That’s adaptation. And if you’re not watching how people adapt, you’re not managing knowledge. You’re managing paperwork.

Solution Compass exists to handle the last part: making sure the answer surfaces in the words the person used, not the words the document used. That’s the only way the system learns. That’s the only way the sticky note becomes a policy — not because someone approved it, but because enough people asked the same question in the same way.

The system doesn’t fail when it can’t answer a question. It fails when it doesn’t notice that the question was asked at all.

Look at the drawer again. The sticky notes aren’t evidence of chaos. They’re evidence of a system that’s trying to tell you something — and you’ve been too busy fixing the printer to listen.

The drawer is still full. The questions haven’t stopped. The system still doesn’t hear them. But someone, somewhere, is still writing them down — by hand, in the margins, on the back of a form — because they know, even if the system doesn’t, that the next person asking will need it more than they need to follow the rules.