The Knowledge Tax
Every 'hey, quick question' costs two people their focus. The knowledge tax is what a firm pays when answers live in people's heads instead of in a system anyone can ask.
Every “hey, quick question” costs two people their focus, and Gloria Mark’s fieldwork puts the recovery from an interruption at about 23 minutes. The knowledge tax is what your firm pays when answers live in people’s heads instead of in a system anyone can ask.
The tax never appears on a timesheet, and it falls hardest on your most experienced people.
What the Interruptions Cost
Say your most experienced person is interrupted four times a day with questions your documents already answer. At 23 minutes each, that is 92 minutes of lost focus a day, 383 hours over 250 working days, and $28,750 a year at $75 an hour (illustrative figures). That is one person, on one side of the exchange; the person who asked lost time too.
Illustrative: one knowledge worker's day. The shares show the shape of the argument; they are not a measurement.
The highlighted share is interruptions, the recovery after them, waiting for answers and hunting through documents. It shows up as “I don’t know where the day went.”
Why Search Does Not Fix It
Most firms already have Confluence, a shared drive or a wiki. Search finds pages, and the person still has to find the answer inside them.
You search 'refund policy' and get 14 results. You open 3 documents and read for 8 minutes before you find the answer in paragraph 4 of the third one. Total: 12 minutes, and you are not sure it is the latest version.
You ask 'what's our refund policy for enterprise clients?' and get: 'Enterprise clients can request a full refund within 30 days of invoice. After 30 days, a prorated refund applies. Source: Client Services Handbook, Section 4.2.'
Search gives you candidates to read. A system you can ask gives you the answer with its source, so you can open the document and check it.
The Same Question, Different Answers
Not everyone should get the same answer. A support agent who asks about profit margins should hear that they do not have access; a CFO who asks should get the figures, with sources.
The hard part, and the part that makes such a system safe to roll out, is knowing when not to answer.
When the Tax Is Highest
The tax peaks when people join and when they leave. New hires ask the most questions, each one interrupting someone senior. When an expert leaves, what they knew leaves with them, including the “we don’t do it that way because three years ago it caused an outage” that nobody wrote down.
Answers Without the Interruption
AskBase, our knowledge engine, is available now and does this. Your team asks in Slack or a web app. It answers from your firm’s own documents, names its sources, and scopes every answer to who is asking. When it finds nothing, it says what it searched instead of guessing.
Employee Asks
A question in Slack or the web app
Retrieve and Filter
The relevant documents, limited to what the asker may see
Generate Answer
An answer written from those documents, with its sources
Answer Arrives
The employee has an answer, and nobody was interrupted
The expert keeps their focus, the new hire gets an answer at once, and the knowledge stays when people leave. Start with one team’s most-asked questions and the documents that answer them. Where an answer exists only in someone’s head, write it down first: no system can retrieve what was never recorded.
How much is “hey, quick question” costing your team?
Book Free Assessment