Blog
The cost of scattered knowledge

Knowledge fragmentation is one of those problems that every company has and nobody budgets for. The information exists. The research was done. The decision was made and the reasoning was discussed. But the research is in someone's Google Drive, the decision was made in a Slack thread that's scrolled away, and the reasoning was shared in a meeting that wasn't recorded. The knowledge is there. Finding it is the problem.
The costs of this fragmentation have been measured across multiple studies, and the numbers are large enough to be uncomfortable.
Employees spend 21% of their work time searching for information (Bloomfire). Another 14% goes to recreating information they can't find. Communication silos cost an average of $12,506 per employee annually. For a 200-person company, that's roughly $2.5 million per year in lost productivity. Fortune 500 companies lose a combined $31.5 billion annually from failing to share knowledge across teams.
These numbers sound dramatic until you map them to the specific activities that produce them. Then they feel conservative.
Where the cost sits
Search time
Employees waste an average of 1.8 hours per day searching for scattered information. That's not searching the internet for new information. That's searching for things the organisation already has but can't find: the report from last quarter, the design brief for the current project, the email where the client confirmed the requirements.
The search fails because the information is distributed across tools that don't share context. You search Google Drive and the document is in Slack. You search Slack and the thread is in email. You search email and find it, but the context for why it matters was discussed in a meeting you didn't attend.
At an average loaded cost of $65/hour for a knowledge worker, 1.8 hours per day of search time costs roughly $585/week per person, or $30,000/year. For a 100-person company, that's $3 million annually spent on finding things.
Duplicate work
When people can't find existing work, they recreate it. The market analysis that was done three months ago gets done again because nobody knows it exists. The client proposal template gets rebuilt because the previous version is in someone's personal drive. The architectural decision gets relitigated because the original reasoning wasn't documented.
Fourteen percent of knowledge worker time goes to this kind of duplication, which is over four hours per week per person on work that's already been done. The cost isn't just the time. It's the opportunity cost of the better work those hours could have produced.
Decision delays
When the context needed for a decision is scattered across tools and people's heads, the decision blocks on gathering the context. A meeting is scheduled. The relevant people are identified and invited. The meeting spends its first twenty minutes reconstructing the background. The decision that could have been made in five minutes (if the context were documented and searchable) takes two weeks.
Onboarding friction
New hires in organisations with fragmented knowledge take two to three times longer to ramp than in organisations with consolidated, searchable knowledge. Each additional week of ramp time costs the employee's full salary while they're producing at a fraction of their capacity.
AI readiness
80% of enterprise data is unstructured "dark data" that AI tools can't access. Companies investing in AI without first consolidating their knowledge are buying tools that can't reach the information they need to be useful. The AI readiness gap is fundamentally a knowledge fragmentation gap.
What consolidation looks like
Reducing the cost of scattered knowledge doesn't require migrating everything into one tool (that rarely works and creates its own problems). It requires a connective layer that makes existing knowledge searchable across boundaries.
Connect your sources. Google Drive, Slack, GitHub, Gmail, Notion, meeting recordings, and the dozens of other tools where knowledge currently lives all feed into one searchable library.
Search by meaning. Semantic search finds information based on what it means rather than the exact words used. "The analysis we did on customer churn" finds the relevant document whether it's titled "Q3 Retention Report," "Churn Analysis," or "Customer Lifecycle Research."
Let knowledge capture itself. Self-writing documentation from Slack conversations, GitHub activity, and meeting recordings captures the knowledge that's currently shared through ephemeral channels and structures it into persistent, searchable documentation.
The investment is small relative to the cost of the problem. A company spending $2.5 million annually on fragmentation-related waste can recover a meaningful portion of that cost by making existing knowledge findable, which is a fraction of a single engineering salary.
Frequently asked questions
How do we calculate our specific cost? Estimate the average hours per week your team spends on search, duplication, and decision delays. Multiply by the average loaded hourly cost. Most companies find the number is between $10,000 and $15,000 per employee per year.
What should we connect first? Start with the tools that contain the most frequently needed knowledge. For most companies, that's the communication tool (Slack or Teams), the file storage (Google Drive or Dropbox), and email. These three sources cover the majority of everyday knowledge needs.
How quickly do we see results? Connecting sources takes hours. The search layer produces results immediately. Teams typically report noticeable reduction in "does anyone know where..." messages within the first month.
Related reading: The search tax, Information silos are the default, Duplicate work is the most expensive kind, The app sprawl problem. Related pages: Connections, One search, Find anything.
Other blog posts:

The cost of misalignment between teams

How to do a competitive analysis (and keep it current)

What is product ops (and do you need it)?

How to keep product and engineering aligned without more meetings

Your user research is worth millions. You can't find any of it.

Why your product decisions keep getting relitigated

How to build a product knowledge base that people actually use

Sales can't find what marketing makes