Why Is Information So Hard to Find at Work? 8 Knowledge Problem Signs

Have you ever spent 20+ minutes looking for information you know exists somewhere?

You remember someone discussing it in a meeting. There’s probably a document. Maybe it was shared in Slack. Or Google Drive. Or the CRM. Or in that project management tool everyone swore would become the single source of truth.

You search a few folders. Try a couple keywords. Ask a coworker.

Twenty minutes later, you’re still looking.

When information becomes difficult to find at work, the obvious reaction is to blame search, documentation, or the number of tools your company uses. Sometimes those are part of the problem.

But often, something bigger is happening: your organization is struggling to preserve and use what it knows.

At media junction, we’ve spent nearly 30 years helping organizations connect technology, processes, customer data, and the people who depend on them.

As AI has become part of everyday work, we’ve seen the same problem become even harder to ignore: companies have accumulated enormous amounts of useful knowledge, but much of it is scattered across systems, documents, conversations, and individual employees.

And adding another search bar won’t magically fix that.

In this article, we’ll look at eight signs your company has a knowledge problem, why those problems happen, and what you can do to make important information easier for people—and AI—to find and use.

why is information so hard to find at work?

Information is hard to find at work when organizational knowledge is scattered across too many places, poorly maintained, disconnected from its original context, or dependent on individual people to explain it.

The issue isn’t always that information is missing.

Often, there’s too much of it.

Think about everything your company creates in a normal week:

• Emails

• Slack or Teams messages

• Meeting notes

• Recorded calls

• Project plans

• Process documentation

• Customer records

• Sales notes

• Presentations

• Spreadsheets

• Training materials

• Decisions made during meetings

• Lessons learned while completing the work

Now multiply that by every employee, every department, and every year your organization has been operating.

That’s a lot of knowledge floating around.

The problem is that creating information and being able to find, trust, understand, and reuse it later are two very different things.

A 2025 knowledge management study found that 55% of respondents had three or more knowledge silos within their organizations, while 51% were using three or more knowledge management tools.

In other words, many companies aren’t suffering from a lack of places to put information. They’re suffering from too many disconnected places to put it.

So, how can you tell if your organization has crossed from an occasional “Where the heck is that file?” moment into a larger knowledge problem?

8 signs your company has a knowledge problem

1. people keep asking the same question

Every company has repeat questions.

Where’s the latest proposal template? How do I submit this request? What did we decide about that customer? Who approves this? How do we handle this situation?

The warning sign is when the same questions keep requiring another person to answer them.

Maybe the answer technically exists in a document, but no one knows where that document lives. Maybe the process was documented six months ago, but everyone knows it has changed since then. Or maybe the answer has never been written down because “Sarah knows how that works.”

At that point, your employees become human search engines.

And unlike Google, they’re also trying to finish their own work.

Repeated questions are often one of the earliest signs that knowledge isn’t accessible enough to be useful. The information might exist, but the organization hasn’t created a reliable way to retrieve it when someone actually needs it.

Pay attention to questions that start with:

• “Does anyone remember…?”

• “Where do we keep…?”

• “Who knows how to…?”

• “Is this still the process?”

• “Which version are we supposed to use?”

• “Why did we decide to do it this way?”

One question isn’t a knowledge management crisis.

The same question being answered for the 47th time might be worth investigating.

2. a few employees know how everything works

If your company depends on a handful of employees to explain processes, find information, or provide historical context, you have a knowledge concentration problem.

You probably know these people.

They’ve been around for years. They know which client had that unusual requirement in 2021. They remember why the sales process includes that seemingly unnecessary step. They know which spreadsheet actually matters and which one everyone stopped using two years ago.

They’re incredibly valuable.

They’re also a risk if the knowledge they carry exists primarily in their heads.

This is often called institutional or tribal knowledge: the experience, context, relationships, and practical know-how people accumulate by doing their jobs over time.

And when experienced employees leave, some of that knowledge can leave with them.

LinkedIn’s 2025 Workplace Learning Report specifically examined skills most at risk of being depleted through employee attrition. Among them were business strategy, strategic planning, sales management, and project planning—skills that depend heavily on experience, judgment, and institutional knowledge.

The goal isn’t to make your experienced employees less important.

It’s to make what they know more available to everyone else.

3. employees have to search five different systems for one answer

Your CRM says one thing.

The project management tool has another piece.

There’s a Google Doc with some additional context.

Someone mentioned an update in Slack.

And, naturally, the final answer is buried in an email thread from eight months ago.

When finding one answer requires searching multiple disconnected systems, your company is dealing with knowledge fragmentation.

At media junction, we call this Knowledge Scatter: useful organizational knowledge exists, but it’s spread across the systems and people that created it.

This happens naturally.

Marketing adopts one platform. Sales uses another. Operations has its preferred project management system. Finance has its software. Teams build spreadsheets to fill gaps. Employees create their own folders and documents because they need to get work done.

Individually, each decision may make perfect sense.

Collectively, you end up with a scavenger hunt.

Microsoft’s 2025 Work Trend Index illustrates just how fragmented the modern workday has become. Its research found employees are interrupted by a meeting, email, or chat an average of 275 times per day—roughly once every two minutes during working hours.

Not every interruption is caused by missing knowledge, of course. But when getting an answer means jumping between tools, messages, meetings, and coworkers, finding information becomes another tax on an already fragmented day.

This doesn’t necessarily mean you need fewer tools.

It means those tools need a better way to work together.

For a related example, our article on signs your financial services firm needs a secure client portal shows how fragmentation can spill over from internal operations into the customer experience.

4. you find answers, but you don’t know if they’re right

Finding a document is one problem.

Finding three versions of the document is another.

If employees regularly have to ask whether information is current, approved, or trustworthy, findability isn’t your only issue. Your organization has a knowledge trust problem.

Picture this:

You search for the onboarding process and find:

• Customer-Onboarding.docx

• Customer-Onboarding-UPDATED.docx

• Customer-Onboarding-FINAL.docx

• Customer-Onboarding-FINAL-v2-USE-THIS-ONE.docx

A timeless classic.

The consequences become more serious when the outdated information involves pricing, compliance requirements, customer commitments, technical processes, or internal policies.

Strong organizational knowledge needs more than storage. People need to know:

• Who owns the information

• When it was last reviewed

• Whether it’s still accurate

• Which source should be trusted

• What changed and why

That last point matters.

Keeping only the newest version may tell you what the organization does today. Preserving the reasoning behind changes tells you why it does it that way.

That context becomes especially valuable when circumstances change again.

5. your company keeps revisiting decisions it already made

When teams repeatedly debate questions the company has already answered, important decision-making context probably isn’t being preserved.

Documentation tends to capture outcomes:

“We decided to use option B.”

Useful organizational knowledge captures the reasoning:

“We chose option B because option A caused these three problems, the customer needed X, and our team learned Y during implementation.”

Six months later, that context matters.

Without it, a new employee can look at option B and reasonably ask, “Why on earth are we doing it this way?”

And suddenly the team is spending another meeting reopening a decision that already consumed three meetings last year.

This is one reason a knowledge problem is bigger than document storage.

Documents tell you things.

Organizational memory helps you remember what happened, what you learned, and why decisions were made.

That history helps teams build on previous experience instead of continually starting from zero.

6. new employees have to learn by asking around

There’s nothing wrong with learning from coworkers.

In fact, some of the best onboarding happens through conversations, mentoring, observation, and hands-on work.

The problem is when that’s the only way someone can learn how the organization operates.

If onboarding depends heavily on who a new employee happens to ask, your company is relying on informal knowledge transfer rather than accessible organizational knowledge.

You’ll hear things like:

• “Just shadow me for a while.”

• “Ask Brian. He knows that system.”

• “I’ll send you the doc if I can find it.”

• “That’s technically the process, but nobody actually does it that way.”

• “You’ll pick it up eventually.”

New employees shouldn’t need to reconstruct the company one coworker at a time.

And this issue becomes more important as people change jobs. The 2025 Work Institute Retention Report notes that employee turnover can create ripple effects that include the loss of institutional knowledge alongside recruiting costs and reduced engagement among remaining employees.

Good onboarding still involves people.

But those people should be able to build on a shared foundation of trusted information instead of retelling the entire history of the organization from memory.

7. customers have to repeat themselves

Knowledge problems don’t stay behind the scenes.

Eventually, customers feel them.

When information doesn’t move with the customer from one employee or department to another, the customer ends up doing the organization’s remembering for it.

• They repeat the same background information to sales and service.

• They explain a preference they’ve already discussed three times.

• A new account manager asks questions the previous account manager already answered.

• Marketing communicates one thing while sales says another.

• Support doesn’t know what implementation promised.

From the customer’s perspective, those aren’t “data integration issues” or “knowledge management challenges.”

They’re frustrating experiences.

Customers don’t care how many systems your company uses. They care whether your company appears to remember who they are and what has already happened.

That’s why organizational knowledge isn’t only an internal efficiency issue.

It affects consistency, trust, and customer experience.

8. your AI tools give generic answers about your own company

Here’s where the knowledge problem is becoming much harder to ignore.

AI can only use organizational context it can access. If your company’s knowledge is scattered, outdated, undocumented, or inaccessible, AI will have the same blind spots your employees do.

You can ask a general-purpose AI tool to write a sales email.

But does it understand why your best salespeople position one service differently for manufacturers than for financial services companies?

You can ask it to create a project plan.

But does it know which steps your team added after a painful lesson three projects ago?

You can ask it to answer an employee’s question.

But does it know whether the 2023 policy or the 2026 policy is correct?

AI is moving quickly into knowledge work. McKinsey’s 2025 State of AI report found knowledge management had become one of the business functions where organizations most commonly reported using AI.

But AI doesn’t eliminate the underlying knowledge problem.

It exposes it.

The 2025 study of AI and knowledge management found that organizations were still struggling with siloed knowledge, fragmented tools, and untrusted content. The researchers warned that simply layering generative AI over existing silos doesn’t resolve the underlying problem.

That’s the catch.

Everyone wants smarter AI.

But before AI can understand your organization, your organization needs a better way to understand and preserve itself.

If you’re exploring how AI fits into your broader business operations, our AI for Business Guide looks at practical ways different teams are already using it.

Is this a documentation problem or a knowledge problem?

Documentation is part of organizational knowledge, but creating more documents alone usually won’t solve a larger knowledge problem.

You can document every process your company has and still end up with information nobody can find.

You can create a knowledge base full of articles nobody trusts.

You can record every meeting and create thousands of hours of information nobody wants to watch again.

The better question isn’t:

• Have we documented this?

It’s:

• Can the right person find the right information, understand its context, trust that it’s current, and use it when they need it?

That’s a much higher bar.

And it brings us to a concept most companies already have, whether they use the term or not: organizational memory.

Organizational memory is the collective knowledge your company builds over time—its decisions, processes, standards, project history, customer context, lessons learned, and institutional knowledge.

Your organization is creating that memory every day.

The challenge is preserving it in a way that remains useful.

what should you do if your company has a knowledge problem?

Start small. Pick one important workflow where people regularly struggle to find information, then identify what they need, where that knowledge currently lives, and what prevents them from accessing or trusting it.

Trying to “organize all company knowledge” is a great way to create a gigantic project that nobody wants to own.

Instead, choose a real business problem.

For example:

• New employees take too long to become productive.

• Sales can’t find the latest customer information.

• Customer handoffs repeatedly lose context.

• Teams keep recreating proposals or deliverables.

• Employees ask the same process questions.

• AI tools can’t reliably answer internal questions.

Then trace the knowledge behind that workflow.

find where the knowledge lives

It may be spread across several tools and people.

That’s okay. Your first job is to see the problem clearly before trying to fix it.

decide what should be trusted

Identify which information is authoritative and who is responsible for maintaining it.

Not every Slack message deserves eternal preservation.

Preserve context, not just files

Capture why decisions were made, what teams learned, and what changed—not just the final artifact.

That context is often the part people need most later.

make knowledge easier to retrieve

Think about how employees actually look for information during their work.

Good knowledge management shouldn’t require them to become professional librarians first.

build for people and AI

Increasingly, the same well-organized, trusted knowledge that helps an employee answer a question can also provide the context an AI system needs to give a useful answer.

Microsoft’s 2025 Work Trend Index found 82% of leaders considered 2025 a pivotal year to rethink major aspects of strategy and operations as AI changes knowledge work.

That makes cleaning up organizational knowledge less of a housekeeping exercise and more of a foundation for whatever comes next.

turn what your company knows into something you can use

If you recognized your company in a few of these eight signs, you now know the problem probably isn’t that your organization lacks information.

Your company already has a lot of valuable knowledge. It lives in your processes, project history, customer interactions, past decisions, lessons learned, documents, systems, and—yes—the heads of the people who have been around long enough to remember why things work the way they do.

The problem is making that knowledge easy to find, trust, understand, and use.

That’s organizational memory.

And once you start looking at the problem through that lens, those everyday frustrations look a little different. The employee asking the same question for the fifth time isn’t necessarily a training problem. The 20-minute hunt through Slack, Google Drive, and your CRM isn’t just a search problem. And AI giving you a generic answer isn’t necessarily an AI problem.

They can all be signs that your organization needs a better way to preserve and connect what it already knows.

That’s the problem we’re working to solve at media junction.

We help businesses bring together their customer systems, organizational memory, and AI so people and technology can work from the same trusted understanding.

We call the approach our Context Operating System™, and the goal is a Connected System where the knowledge your organization has accumulated doesn’t just sit somewhere—it can actually help people do better work.

If this article helped you recognize the symptoms, the next step is understanding the bigger idea behind them. Read our Organizational Memory Guide to learn what organizational memory is, why businesses lose it, how it affects your people and customers, and how to start preserving what your company knows.