Most large organizations acknowledge that knowledge silos are a problem. Few have a clear way to measure how severe their specific silo problem is or where in the organization the worst concentrations are. This matters because the word "silos" tends to get applied to a broad range of organizational friction, and not all of it is the same problem. Some of what gets called a knowledge silo is actually a coordination failure. Some is a communication culture issue. Some is genuine knowledge hoarding. And some is structural: knowledge that is concentrated in pockets because there is no mechanism for it to flow, not because anyone is holding it back.
The patterns below are the ones we have seen most consistently when organizations have a genuine knowledge silo problem, as opposed to the general organizational friction that gets misdiagnosed as silo behavior. Each one is observable without any special tooling, though tooling can make the measurement more precise. We offer these as diagnostic signals, not as definitive tests. An organization can exhibit one or two of these for reasons unrelated to knowledge silos. Seeing multiple of them simultaneously, especially in persistent and widespread form, is a stronger signal.
Signal 1: New projects start with a search, not a plan
When a project lead at a large organization gets assigned a new initiative, how do they begin? If the typical answer is "I make a few calls to figure out who has done something similar before," the organization has a knowledge silo problem. The first week or two of a project should not be spent discovering what the organization already knows. That information should be accessible.
The specific indicator to look for is the pattern of informal outreach that precedes any formal project planning. How many people does a project lead contact before they start scoping? What fraction of those contacts are referred onward to a third person ("You should talk to so-and-so, they did something like this in 2022")? If every project kickoff involves a multi-hop search through an informal network before the relevant expertise is located, the organization is paying a recurring tax on every initiative it runs. The cost is not obvious because it is distributed across many individuals' time and normalized as "how projects start here."
Signal 2: The same problem gets solved in multiple places
This one is harder to detect in real time, but it becomes visible in retrospectives, during organizational restructurings, and in situations where teams need to integrate their work. Multiple teams in different parts of the organization build the same tooling, develop the same process documentation, or arrive at the same analytical framework independently. No one knew the others were working on it.
We discussed in a previous post a manufacturing firm where three separate engineering units each built their own data normalization utility without knowledge of each other. This is a vivid example, but the pattern extends beyond technical work. Procurement teams at different business units develop separate vendor evaluation frameworks. HR business partners in different regions develop similar onboarding process guides. Finance teams in different functions build parallel models for the same reporting requirement. The duplication is not discovered because no one has visibility into who is building what.
The cost of this signal is not just wasted effort. It is the absence of shared learning. When three teams solve the same problem independently and only one of the three solutions is good, the other two remain in use. When the teams learn of each other after the fact, there is rarely a mechanism to consolidate on the best approach. The silo problem compounds into a consistency problem.
Signal 3: Specific people become unavoidable bottlenecks
In every large organization, some people are referred constantly because they know things that others need to know to get their work done. This is a natural consequence of expertise accumulation. But when the same small set of individuals becomes a required input to a wide range of decisions and projects across the organization, it signals that knowledge is not flowing outward from those people. They are knowledge concentrations, not knowledge hubs.
The distinction matters. A knowledge hub shares what it knows and creates new channels for the knowledge to propagate. A knowledge concentration absorbs requests for access to knowledge that other people have not acquired. In organizations with severe silo problems, a few individuals develop a reputation for being the only person who knows how a specific system works, the only person who understands a specific client relationship, or the only person who can navigate a specific regulatory area. That pattern is a warning signal. The individual's departure, planned or unplanned, creates a knowledge vacuum that the organization cannot quickly fill.
Signal 4: Cross-functional collaboration relies on personal relationships
In organizations with functional knowledge silos, collaboration between departments happens primarily when a personal relationship bridges the gap. Two people who worked together on a previous project can collaborate effectively across departments because they know each other. Two people who do not have that prior relationship struggle to connect, even when their work domains overlap significantly and they would benefit from interaction.
The diagnostic question is: when a team member needs something from a department they have no prior relationship with, what is the typical outcome? In healthy organizations with accessible knowledge infrastructure, the answer involves some kind of findable resource or structured routing. In organizations with silo problems, the answer typically involves frustration, escalation to a manager who has a relationship, or giving up and finding a workaround.
Signal 5: Knowledge transfer plans are event-driven, not continuous
Many organizations have succession plans and knowledge transfer processes for planned departures. What they rarely have is a continuous mechanism for capturing and distributing expertise before departure becomes imminent. Knowledge transfer gets triggered by an announcement, a retirement notification, a resignation letter. At that point, the organization scrambles to extract what it can before the window closes.
Organizations with silo problems tend to manage knowledge transfer reactively because they have no infrastructure for managing it proactively. They cannot easily answer who holds concentrated knowledge, so they cannot plan for its transfer. They deal with each departure as a discrete event rather than as an instance of a pattern that requires systematic management.
If your organization's approach to knowledge transfer is primarily triggered by individual departures rather than by a continuous map of where expertise concentration and risk intersects, the reactive approach is a signal that the underlying knowledge landscape is not visible enough to manage proactively. That visibility gap is the silo problem in its most operationally consequential form.
What to do with these signals
Identifying these patterns in your organization is a starting point, not a solution. Each of them points to a category of knowledge flow failure that has different root causes and different remediation approaches. A single well-scoped knowledge mapping exercise, targeted at the part of the organization where these signals are strongest, will typically reveal more about the specific nature of the problem than any general diagnostic. The goal is not to catalogue all the knowledge silos. It is to identify the ones that are costing the most, and address those first.
