Organizations lose institutional knowledge every day. Loss of critical knowledge could be caused by retirement, turnover, or even worse, restructuring. The reason doesn’t change the result: critical knowledge disappears, and the people left behind scramble to recreate what was already known.
I’ve witnessed this happen recently in federal agencies and universities, as well as in the corporate world during my time in finance, back in the early 2000s. The universal scenario works like this: A subject matter expert leaves. Their replacement arrives weeks or months later to discover that the documentation is outdated, the processes aren’t written down, and/or the informal networks that made things work are no longer in place. Anyone who has been in the workforce for a length of time has seen it.
The Knowledge Management Gap
Most organizations treat knowledge management as a documentation problem. Create better SOPs. Maintain more detailed process guides. Build comprehensive wikis.
But documentation alone doesn’t capture institutional knowledge. It doesn’t capture the why behind decisions or explain which workarounds exist because of legitimate constraints versus which ones exist because “that’s how we’ve always done it.” It doesn’t preserve the relationships between systems, stakeholders, and strategic priorities.
Real knowledge management requires understanding that knowledge exists in three forms:
Explicit knowledge lives in documents, databases, and formal training materials. This is what most KM systems capture.
Tacit knowledge resides in people’s minds; it is the experience-based insights that experts utilize without conscious thought. This is harder to transfer but equally critical.
Embedded knowledge lives in processes, culture, and organizational relationships. This is nearly impossible to document, but devastating to lose.
What Actually Works
Organizations that maintain knowledge through transition do three things differently:
They build redundancy into expertise. Critical knowledge doesn’t live in one person’s head. Multiple people understand key systems, maintain important relationships, and can execute essential processes. This isn’t inefficient, it’s resilient. As a former university colleague once taught me, there should never be a single point of failure.
They create learning pathways, not just documentation. New team members don’t just read manuals. Instead, they work alongside experienced colleagues, participate in communities of practice, and have structured opportunities to ask questions and make sense of what they’re learning. (Something my current organization does well.)
They treat knowledge transfer as continuous work, not crisis response. Knowledge management isn’t something you do when someone gives notice. It’s built into regular operations—shadowing rotations, cross-training, documented decision-making processes, and accessible repositories that people actually use. It also doesn’t hurt to have a team focused on knowledge management. (Shout out to the KM team!)
The Real Cost of Lost Knowledge
When institutional knowledge leaves the organization, it’s not just efficiency that is lost; it’s also the expertise and experience that are lost. Organizations lose the ability to learn from past mistakes. They repeat failures that were already solved. Decisions are made without understanding the historical context.
In learning and development specifically, lost institutional knowledge means:
- Training programs that don’t connect to organizational strategy because the people who understood both are gone
- Assessment practices that measure the wrong things because no one remembers why current metrics were chosen
- Technology implementations that ignore lessons from previous failures
- Competency frameworks that drift from business needs because the connection isn’t documented
The cost shows up months later, in small inefficiencies and repeated mistakes that compound over time.
Building Resilient Knowledge Systems
Effective knowledge management isn’t about preventing people from leaving. It’s about building systems that can absorb transitions without losing critical capabilities.
That means:
- Documenting decisions, not just processes. Capture why choices were made, what alternatives were considered, and what constraints influenced the outcome.
- Creating apprenticeship opportunities. Pair experienced staff with newer team members on real projects, not just training exercises.
- Building accessible knowledge repositories. Systems people actually use, organized around how work gets done, not how information is categorized.
- Maintaining communities of practice. Regular opportunities for people to share insights, solve problems together, and build collective understanding.
- Making knowledge sharing part of performance expectations. Reward people for developing others, not just for individual expertise.
What This Means for Learning Leaders
For those of us in learning and development, knowledge management is central, not peripheral, to our work. We’re responsible for building organizational capability. That includes the capability to preserve and transfer what we know.
During times of transition, that responsibility becomes more visible. The question isn’t whether knowledge will be lost. The question is whether we’ve built systems that can minimize that loss and accelerate recovery.
The organizations that navigate transitions successfully aren’t the ones that prevent change. They’re the ones who treat knowledge management as an essential and continuous infrastructure, worth the investment even when things are stable.
What knowledge management practices have you seen work (or fail spectacularly) during organizational transitions? The approaches that work in stable times may not work under pressure.
