The real cost of not being able to find something

Knowledge workers spend 2.8 hours a week looking for information that already exists somewhere in their organization. That's not time doing the job badly. It's time spent trying to start the job at all.

What the data shows

• 2.8 hours/week spent looking for or requesting information that already exists (APQC)
• Only 30 of 40 hours in a typical work week actually go to productive work (APQC)
• ~2/3 of knowledge management and IT leaders say poor findability significantly drains productivity (APQC)
• ~1/2 say it also hurts satisfaction, time-to-competency for new hires, and how fast work actually finishes (APQC)
• 68% of workers report not having enough uninterrupted time to focus on core work, amid rising information overload (Microsoft survey, cited by HBR)

Three hours a week, gone before the work even starts

APQC's survey of knowledge workers put a number on something most people feel but rarely quantify: 2.8 hours a week spent looking for or requesting information that already exists somewhere in the organization. Out of a 40-hour week, only 30 hours go to productive work in the first place, the rest disappears into internal communication, unnecessary meetings, and exactly this kind of searching.

Scale that across a team of ten and it's 28 hours a week, or roughly three-quarters of a full-time role, spent entirely on retrieval rather than output. Scale it across a portfolio of properties, each with its own documentation trail, and the number stops being an HR statistic and starts being a real operating cost nobody has assigned a line item to.

It's not a search problem. It's a findability problem.

Nearly two-thirds of the knowledge management and IT leaders APQC surveyed say an inability to find information is a significant drain on productivity. Close to half say it also hurts employee satisfaction, how long it takes a new hire to become genuinely useful, and how fast anything actually gets finished.

Harvard Business Review names the underlying structural cause plainly: an organization's real knowledge rarely lives in one place. It's scattered across documents, policies, processes, and, very often, inside the heads of specific people. When that person goes on leave, changes roles, or leaves the company, the knowledge doesn't disappear. It just becomes unreachable by everyone who isn't them.

That's a fundamentally different problem than "we don't have enough information." Most organizations have plenty of it. What they don't have is a reliable, structured way to reach the specific piece that answers the question someone actually has, at the moment they have it.

Why more information makes this worse, not better

A Microsoft survey cited by HBR found 68% of workers don't get enough uninterrupted time during the day to focus on their core work, and rising information overload is a significant driver of that. More documents, more systems, more places something could plausibly be filed, without a structured way to actually surface the right one, doesn't solve the findability gap. It multiplies the number of places the next hour can get lost in.

This is also precisely why AI on its own doesn't fix findability, even though it's often pitched as the fix. A language model can summarize a document beautifully once it has that document in front of it. It cannot summarize a document it was never given, and it cannot know that the answer to a question exists three folders deep under a filename nobody remembers, in a system nobody thought to connect it to.

AI amplifies whatever structure already exists underneath it. Point it at organized, current, well-labeled information and it becomes a genuinely fast way to retrieve an answer. Point it at the same disorganized archive that was already costing people 2.8 hours a week, and it either fails to find the answer at all, or worse, confidently produces one from the wrong, outdated version it happened to have access to.

The fix isn't searching harder

The instinct when findability becomes a visible problem is usually to buy a better search tool, or to ask people to be more disciplined about filing things correctly going forward. Both address the symptom. Neither addresses the actual structural gap: information that was never organized once, consistently, at the point it was created.

The fix that actually holds up is organizing the information once, in a structured way, so the answer to a specific, recurring question is already sitting there waiting rather than needing to be reconstructed from scratch every time someone new asks it. That's a one-time cost against a recurring one: 2.8 hours a week, every week, for every person, indefinitely, until the underlying structure changes.

Frequently asked questions

Is 2.8 hours a week really significant, or is that overstated?

Across a single person's week it sounds modest. Multiplied by a team, a department, or a portfolio's worth of documentation, and compounded over months and years, it adds up to a meaningful fraction of total available working time, consistently, every week, indefinitely, until the underlying structure changes.

Doesn't a good internal search tool solve this?

Search tools help retrieve documents that already exist and are indexed. They don't fix documents that were never properly filed, categorized, or kept current in the first place. A great search tool over a disorganized archive still returns the wrong or outdated version quickly, which is arguably worse than returning nothing.

How is this different from just needing better file naming conventions?

Naming conventions are a manual, human-maintained discipline that erodes the moment someone's in a hurry or new to the team. A structured record that's organized at the point of creation, and stays current automatically, doesn't depend on everyone remembering the convention every single time.

Does this apply equally to small teams, or is it mainly a large-organization problem?

The percentage cost is roughly the same regardless of size. The difference is that a larger organization has more total hours to lose, and more people who might independently rediscover, or fail to find, the same piece of information. Small teams feel it as "why does this always take longer than it should"; large ones feel it as a measurable productivity gap.

---

CroVIN organizes property and project information once, at the point it's created, so the answer to a recurring question is already structured and reachable, not something someone has to go find again every time.