Knowledge management has spent much of its history trying to improve the movement of knowledge.
Organizations invest in repositories to make knowledge accessible. Communities of practice are established to encourage exchange. Collaboration platforms are deployed to connect people across functions and geographies. Lessons learned programs seek to ensure that experience from one project informs future work. Behind these efforts lies a largely unquestioned assumption: valuable knowledge already exists within the organization, and the primary challenge is ensuring that it moves efficiently to where it is needed.
The language of the discipline reflects this assumption. Knowledge is said to flow. It is transferred, shared, disseminated, exchanged, distributed, and circulated. The metaphors are revealing because they imply movement. Knowledge is frequently treated as though it behaves like a resource capable of travelling through an organization if the appropriate channels are established.
Yet organizational reality tells a different story.
Most organizations can point to examples where critical knowledge failed to reach the people who needed it. Teams repeat mistakes that have already been documented elsewhere. New employees spend months discovering information that already exists within the enterprise. Experts solve problems that colleagues solved years earlier. Business units unknowingly develop competing solutions to identical challenges. Lessons are captured but rarely influence future decisions. Valuable expertise remains concentrated within small groups despite substantial investment in knowledge-sharing initiatives.
These failures are often interpreted as evidence of insufficient knowledge sharing. Consequently, organizations respond by creating more repositories, encouraging more collaboration, and generating more content. The assumption is that greater knowledge availability will naturally produce better knowledge utilization.
The persistence of these problems suggests a different possibility.
Perhaps knowledge does not move through organizations as easily as we assume.
Perhaps every attempt to create, communicate, interpret, transfer, or apply knowledge encounters resistance.
This resistance may be understood as knowledge friction.
Knowledge friction refers to the forces that impede the movement, interpretation, and application of knowledge within organizations. The concept draws attention to something that knowledge management has often overlooked. The challenge is not simply generating knowledge or making it available. The challenge is that knowledge encounters resistance at every stage of its journey.
This resistance begins with the nature of knowledge itself.
Information can be transmitted. Documents can be distributed. Databases can be replicated. Knowledge operates differently. Knowledge exists within human understanding. It is shaped by experience, judgment, assumptions, and context. When one person attempts to communicate knowledge to another, the knowledge itself does not move. What moves are words, symbols, documents, demonstrations, and conversations. The recipient must then interpret these signals and reconstruct meaning using their own experiences and mental models.
This distinction is fundamental.
A document may be transferred perfectly while understanding is transferred imperfectly.
A lesson may be communicated clearly while being interpreted differently.
An expert may explain a process accurately while failing to convey the judgment that makes the process effective.
The assumption that knowledge moves directly from one individual to another obscures the complexity of what actually occurs.
Every transfer involves reconstruction.
Every reconstruction introduces friction.
The concept becomes particularly important when considering expertise. Organizations frequently focus on identifying experts and encouraging them to share what they know. This appears sensible. Experts possess valuable knowledge. Sharing should therefore increase organizational capability.
In practice, expertise often generates its own friction.
The more experienced individuals become, the more deeply their knowledge becomes embedded in intuition, habit, and pattern recognition. Decisions that once required conscious reasoning become automatic. Assumptions become invisible. Nuances become difficult to articulate. Experts frequently struggle not because they are unwilling to share knowledge, but because they can no longer fully observe the knowledge they possess.
This creates a paradox. The individuals who know the most are often the least capable of explaining everything they know.
Knowledge friction emerges not from resistance to sharing but from the very nature of expertise itself.
The organizational environment introduces additional layers of resistance. Every function develops its own language, priorities, assumptions, and definitions of success. Engineers, marketers, lawyers, financial analysts, and operations professionals often interpret the same information differently because they operate within different professional realities. Knowledge that appears obvious within one domain may require substantial translation before it becomes meaningful in another.
What organizations frequently describe as silos may therefore represent something deeper than structural separation. They may reflect accumulated friction between different ways of understanding the world.
Technology, despite its promise, can also amplify friction. For decades, organizations have attempted to solve knowledge problems through improved access. Better repositories, more sophisticated search capabilities, enterprise social networks, collaborative workspaces, and increasingly intelligent systems have all been introduced with the expectation that accessibility will improve knowledge flow.
Accessibility matters, but access does not eliminate friction.
Finding information is not the same as understanding it. Understanding it is not the same as trusting it. Trusting it is not the same as applying it. Applying it is not the same as generating value from it.
At every stage, additional resistance emerges.
The result is that organizations often possess far more knowledge than they effectively utilize.
Perhaps the most significant source of friction, however, is context.
Knowledge is never created in a vacuum. Every decision, lesson, process, and best practice emerges from a specific set of circumstances. Context determines meaning. Context determines relevance. Context determines applicability.
As knowledge moves away from its original environment, portions of that context are inevitably lost. Future users inherit conclusions without experiencing the conditions that produced them. They encounter recommendations without understanding the constraints under which they were developed. They receive solutions without fully appreciating the problems those solutions were designed to solve.
The further knowledge travels from its point of origin, the greater the risk that context will deteriorate.
This form of friction is particularly dangerous because it often remains invisible. Knowledge appears available. Documentation exists. Repositories are populated. Yet the knowledge cannot be effectively applied because the contextual understanding necessary for interpretation has been lost.
Viewed through this lens, many longstanding knowledge management challenges begin to appear differently.
Lessons learned programs frequently fail not because lessons are absent but because friction separates experience from future application.
Knowledge repositories become underutilized not because employees reject knowledge sharing but because friction increases the effort required to locate, interpret, validate, and apply stored knowledge.
Communities of practice struggle not because members lack expertise but because friction limits the translation of expertise across different contexts.
Even organizational memory itself may be understood as a battle against friction. The challenge is not simply preserving knowledge over time. The challenge is preserving enough context, understanding, and relevance for future generations to make meaningful use of what has been preserved.
The implications for knowledge management are significant.
For many years, organizations have attempted to solve knowledge problems by increasing knowledge production. More content. More documentation. More lessons learned. More repositories. More sharing initiatives.
These efforts assume that knowledge scarcity is the primary obstacle.
In many organizations, the greater challenge may be knowledge friction.
Knowledge already exists. The question is whether it can move, be understood, be trusted, and ultimately be applied.
This suggests a subtle but important shift in how knowledge management is understood. The role of KM may not be to maximize knowledge flow. Such a goal may be impossible because friction is an inherent feature of human organizations. Instead, the objective may be to identify where friction exists, understand why it emerges, and determine which forms of friction should be reduced and which should be preserved.
Not all friction is harmful. Review processes create friction. Governance creates friction. Critical thinking creates friction. Expert validation creates friction. These forms of resistance often improve decision quality and reduce risk. The goal is not frictionless knowledge movement. The goal is intelligent friction.
Organizations that understand this distinction may begin asking different questions. Rather than asking how knowledge can be shared more effectively, they may ask where knowledge encounters resistance and why. Rather than measuring repository growth, they may examine how much effort employees expend to transform available knowledge into actionable understanding. Rather than assuming that knowledge naturally flows, they may recognize that movement requires continuous effort.
Knowledge management has traditionally focused on the assets organizations possess. Knowledge friction directs attention toward something equally important: the forces that prevent those assets from creating value.
The future of knowledge management may depend not on how much knowledge organizations create, but on how well they understand the resistance that knowledge encounters as it attempts to move through the enterprise.