Watch where questions flow in any company and you will find the same pattern: they flow to whoever answers fastest. That person becomes the router for everything. What is our cancellation window? Where does the month-end pack live? Who owns the booking-confirmation flow?
They answer, because answering is quicker than pointing at a doc that may or may not be current. And so the loop closes: the more they answer, the more they are asked.
The tax is bigger than the minutes
The naive cost is time: a few minutes per question, a few dozen questions a week. Annoying, survivable.
The real cost is what those interruptions displace:
- Focus. Each question lands mid-task. The answer takes two minutes; getting back into the task takes twenty.
- Judgment. Your most experienced people spend their scarcest hours restating known facts instead of exercising judgment on new problems.
- Resilience. When knowledge lives in a person, the person is a single point of failure. Vacations, departures, and busy weeks all become outages.
None of this shows up in a metric, which is why it survives. It just shows up as your best people being permanently behind.
Why the wiki did not fix it
Most teams have tried the obvious answer: write it all down. It helps less than expected, for one reason. A wiki answers the question it was written for, phrased the way the author phrased it. Real questions arrive in someone else's words, halfway between two pages, with context the author never anticipated.
So the asker searches, skims two near-miss pages, and messages the expert anyway. The doc exists; the tax continues.
Answers should come from the work, not from memory
The fix is to let people ask in their own words and get an answer assembled from the actual sources: the doc, the tickets, the threads, the spreadsheets, each claim traced back to where it came from.
That is what Husn does. It reads across the tools you already use and answers with sources shown, read-only, without pinging a human. The expert keeps their morning. The asker gets a better answer than a half-remembered Slack reply. And the knowledge stops living in one overloaded head.