Cost Of Time Spent Searching for Information at Work
Diana has the payment run open, and the approve button is one click away. But she can’t click it. Earlier that morning, the analyst reviewing her work had asked her why the Hartwell Supply invoice always gets a manual adjustment. Although Diana had approved that adjustment every month for the past six years, she had no idea why it existed.
It’s now 2:15 pm on a Tuesday, and the payment run has to go out by the end of the day.
She opens the wiki to find the page for Hartwell was last updated nineteen months ago. It names the vendor, but has no mention of the manual adjustment. She then searches Slack and gets forty-two results. Thirty-nine are unrelated, and the rest are other colleagues asking the same question in 2023, eliciting only a thumbs-up emoji in reply. She messages the finance lead, whose calendar shows meetings until five. With the deadline inching closer, she messages Tom, who had joined the company the same year she did. He thought that it was a rounding issue, then added that she should probably confirm that with someone else. So, finally, she books a call with the finance lead for the next morning, which means the payment run will be late.
At 5:10 pm, a teammate remembers a Slack thread from the previous spring and finds it by sheer luck. The reason for the manual adjustment was a billing agreement with Hartwell that predated the current system. Reading the explanation took thirty seconds. Finding it took the entire afternoon.
Time spent searching for information at work includes looking for answers, documents, and the colleagues who hold the information, instead of doing the work those answers support. In most mid-market teams, the share of that time is large, but appears on no timesheet or project plan. Nobody Diana reached out to that afternoon was new, careless, or underperforming. The search failed because the knowledge sat somewhere a search could not reach.
What the Search Costs a Team
McKinsey research on knowledge work finds that employees spend about 20% of their working week searching for internal information or tracking down colleagues who have it. That is close to a full day per person, every week, spent on work that produces nothing new.
Panopto's research explains part of why the figure is so high: 42% of role-specific expertise is known only by the person currently doing the job. A large share of what employees search for is not stored anywhere. It lives in one person's head, which turns the search into a hunt for a person rather than a document.
The search also costs the people who get asked. UC Irvine research on interruptions finds that it takes an average of 23 minutes to regain full focus after being pulled away from a task. Every ask-around spends the asker's time and fragments the responder's. Diana's Tuesday cost at least four people part of their day.
Why the Answer Is So Hard to Find
The knowledge people search for most is implicit: the reason behind a decision, the exception to a process, the context that explains why something works the way it does. It fails to turn up for three reasons.
- It was never written down. The person who knows it has not been asked to record it, and the reasoning feels obvious to them.
- It was written down and went stale. A page that is nineteen months old forces the reader to guess whether it still applies. After a few of those experiences, readers stop trusting the whole source, which is why nobody uses your documentation even when it exists.
- It was said in a conversation that scrolled away. The explanation exists, attached to a real question, but it sits in a thread no one can locate without remembering the exact words.
The third reason is the most common and the least discussed. Your team already answers these questions in Slack. The answers just do not last.
Why Searching Harder Does Not Fix It
The usual response is better search tooling or a more disciplined wiki. Both help at the margins. Neither reaches implicit knowledge, because a search tool can only index what exists as a document. If the reasoning behind the Hartwell adjustment was never written, no improvement in search quality will surface it. A wiki nobody maintains makes the problem worse by returning confident-looking pages that are out of date.
The gap sits between where knowledge is created, which is conversation, and where search looks, which is documentation.
What Changes When the Answer Already Exists
Pravodha closes that gap by capturing knowledge at the moment it is shared. When a colleague explains the Hartwell adjustment in Slack or Teams, anyone on the team can save the thread in three clicks. The explanation is attributed to the person who gave it, validated by the colleagues who found it useful, and searchable by topic.
For Diana, the afternoon becomes a two-minute search. She types "Hartwell adjustment," finds the explanation, sees who wrote it and that two colleagues marked it as useful, and sends the payment run on time. If she has a follow-up, she knows exactly who to ask, so it takes one targeted message instead of four guesses. Finding the right person to ask becomes part of the same search.
The experts benefit as well. An answer captured once does not need to be given again, so the pings that interrupt their focus time drop.
Where to Start
Before changing any tooling, measure the problem. Ask each team to log every search for an answer over one week: what they needed, where they looked, who they asked, and how long it took. Most teams find that a small number of recurring questions account for a large share of the time, and that most of those answers are implicit knowledge held by a few people. Those recurring questions are the first knowledge worth capturing, and they show where tribal knowledge is costing the most.