Most Companies Don't Know What They Know

One of the more curious characteristics of growing companies is that they often spend an extraordinary amount of time looking for knowledge they already possess.

A founder asks whether anyone has spoken to customers about a particular feature, only to discover weeks later that the customer success team has been hearing the same feedback for months. A pricing discussion unfolds as though it were being considered for the first time before someone remembers that the company debated the exact issue during the previous year. An executive asks for a competitive analysis, unaware that another team completed a remarkably thorough version only a few quarters earlier. Entire meetings are organized around questions whose answers already exist somewhere inside the organization, quietly waiting to be rediscovered.

These situations are so common that they are usually accepted as part of operating a business. People shrug, forward another document, search through old Slack messages, or ask around until someone eventually uncovers the missing context. The company moves on, and everyone assumes the problem has been solved.

In reality, nothing has been solved at all.

The document was found, but the organization's inability to know that it already possessed the knowledge remains exactly as it was before.

This distinction is easy to miss because we naturally think of knowledge as something that either exists or does not exist. If the information can be located eventually, we assume the company knew it all along. Yet there is a meaningful difference between possessing knowledge and being able to recognize that you possess it when it matters.

Human memory illustrates this distinction remarkably well. There are moments when someone asks us a question and we immediately answer, not because we have consciously stored the information in preparation for that moment, but because our minds somehow recognize that the knowledge already exists and retrieve it almost effortlessly. At other times we experience the opposite sensation. We are convinced we know the answer, yet we cannot reach it until hours later when the connection unexpectedly returns.

The information did not change.

Our ability to access it did.

Organizations experience the same phenomenon on a much larger scale.

Every conversation with a customer leaves behind an observation. Every pricing experiment teaches the business something about demand. Every product launch reveals assumptions that proved correct and others that did not. Every failed hire, successful negotiation, engineering incident, marketing campaign, and strategic discussion contributes another piece to the organization's understanding of itself. Collectively, these experiences form something far richer than a collection of documents. They become the accumulated knowledge of the company.

The difficulty is that experience accumulates much faster than organizations develop mechanisms for recognizing it.

As companies grow, knowledge becomes scattered across documents, dashboards, spreadsheets, project management systems, customer relationship platforms, emails, meeting notes, and thousands of conversations that were never formally recorded at all. Every system faithfully preserves a small part of the organization's history, but no individual system understands how those pieces fit together. The company gradually becomes richer in experience while simultaneously becoming poorer at recognizing the experience it already possesses.

This explains why so many discussions inside mature organizations feel strangely repetitive. Teams often revisit questions that were settled months earlier, not because the previous decision was forgotten, but because the reasoning behind that decision has become increasingly difficult to discover. Employees who participated in the original discussion move into different roles or leave the company altogether. New leaders inherit the conclusion without inheriting the context that made the conclusion sensible. Eventually the organization begins solving the same problems repeatedly, each generation believing it is confronting them for the first time.

We often describe this phenomenon as losing institutional knowledge, but that phrase can be misleading because it suggests the knowledge itself has disappeared. Much of it has not. More often, the organization has simply lost the ability to recognize where that knowledge lives, how trustworthy it is, and why it mattered when it was first created.

Perhaps this is one of the defining differences between individual intelligence and organizational intelligence.

A person who cannot recognize what they already know struggles to reason effectively. The same is true of companies. Before an organization can answer a question, it must first recognize that the answer already exists somewhere within its collective experience. Without that recognition, every important question feels like a new question, every difficult decision feels unprecedented, and every lesson risks being learned more than once.

Artificial intelligence has made this challenge more visible rather than less. Modern systems can search enormous collections of documents, summarize years of conversations, and retrieve information at remarkable speed. These capabilities are undeniably valuable, but retrieval alone does not solve the deeper problem. A company may still retrieve ten documents without recognizing which one captures the understanding that should guide today's decision. Access to information is not the same as awareness of organizational knowledge.

The organizations that operate most effectively over the coming decade will not simply accumulate more knowledge than everyone else. Information is becoming abundant for every business. Their advantage will come from maintaining a continuous awareness of what they already understand, what they have already learned, and where the boundaries of their knowledge still remain.

Perhaps that is what organizational maturity really looks like.

Not a company that knows everything.

A company that knows what it knows, understands why it knows it, and recognizes when it does not know enough to decide with confidence.