This post is part of the BRIDGE framework series, which explores how organizations preserve knowledge continuity when people retire, change roles, or move on. Informed by interviews, lived experience, and research, the series looks at how tacit knowledge and professional judgment can be carried forward during periods of change and transition.
In Record What Matters, we established that while documentation is necessary, it is not sufficient. Manuals and handbooks describe how things are done, but they don’t say why.
Involve Others is the keystone of the BRIDGE framework because it explains why documentation has limits.
Professional expertise cannot be transferred in isolation. This post explains why knowledge transfer is especially fragile at moments of transition, how expertise actually moves between people, and what organizations and departing employees can do earlier to improve the process.
Why Knowledge Transfer is Fragile When People Leave
Knowledge transfer is fragile because the most valuable expertise is rarely explicit. As professionals gain experience, judgment becomes increasingly automatic. Decisions are made quickly and confidently, without conscious explanation. When organizations attempt to capture this expertise late—typically close to retirement or departure—they are trying to document something that has already slipped out of reach.
Research supports this loss of knowledge. APQC’s Great Retirement survey found that 41% of organizations rarely or never attempt to capture knowledge from retiring employees. Even where efforts do exist, they are often late and uneven, focused on producing documentation rather than understanding how judgment is formed and applied in practice.
Timing matters because automatic expertise is difficult to access under pressure. Practitioners consistently point to this constraint. Loraine Wiseman, for example, advocates for open conversations two to three years before retirement. These allow expertise to be surfaced gradually, while it is still active and contextualized, rather than compressed into a rushed handover at the end.
Taken together, these factors explain why effective knowledge transfer so often fails. The conditions it depends on—trust, permission, proximity, and time—have already eroded. This is not a failure of goodwill, but a structural misunderstanding of how expertise develops and how quickly it becomes invisible unless it is deliberately surfaced while still embedded in practice.
How Knowledge Actually Moves Between People
Written instruction matters, but it is not how judgment is learned. People learn by listening, watching, asking questions, and working through problems together. They absorb how others respond to uncertainty, why a particular choice was made, and when a rule should be followed or questioned. This kind of understanding forms through interaction, not in isolation.
What is often described as “wisdom” in knowledge management shows up in practice as professional judgment: the ability to interpret information, assess risk, and act appropriately in context. This is the capability organizations rely on every day, even though it is rarely written down or formally taught.
Organizations already know this. When assessing expertise, they rarely rely on written evidence alone. Recruitment processes include interviews, sample work, probation periods, and working style or personality assessments. These exist because documentation cannot establish trust, judgment, or fit on its own. Professional capability is evaluated socially before it is relied upon operationally.
Anne describes this gap clearly:
“It’s like muscle memory. As an experienced legal knowledge professional, you can check whether a case is still good law almost on autopilot. A lot of that is just experience—the same as in any role. A mechanic with twenty years’ experience will change a wheel far quicker than someone with one year, and all the knowledge in the world won’t change that.
Repositories help with knowledge transfer, but you can’t expect someone with less experience to be as effective in the same way—even if they may be better in other areas. That’s why I think organizations sometimes focus too narrowly on roles rather than people. Job descriptions often describe the skills of the previous role holder, not what the role could become.
There’s always a balance. You may lose time in one area while someone builds experience, but you often gain time or value elsewhere through new skills and ideas. What you’re really weighing is what’s lost through indwelling experience against what’s gained through fresh thinking.”
Her point reframes the problem. Knowledge transfer is not about recreating the outgoing role holder in documentary form. It is about deciding what must be carried forward, what can only be learned through use, and where space should be left for new capability to appear.
At moments of transition, this logic is often reversed. Knowledge transfer is treated as a one-way task: write it down, store it somewhere, and assume it will hold. As people approach retirement or departure, professional interaction is usually reduced just as it becomes most necessary.
What is lost is not information, but sense-making. Successors inherit workflows without understanding the reasoning that shaped them. Continuity is expected to appear from records alone, rather than from shared work while expertise is still active.
Creating the Conditions for Knowledge to Move
If this is how knowledge is transferred, the next question is why firms rarely create the conditions for it to happen before someone leaves.
Most people are willing to share what they know. The problem is not motivation, but the environment. Hierarchy can make experienced staff feel distant or unapproachable. Likewise, long tenure can discourage questioning. When time is tight, reflection gives way to instruction, and conversation dries up.
Shared problem-solving is especially effective because it introduces strategic friction. Working through a real issue together slows thinking just enough to surface judgment that normally stays automatic. Observation alone rarely achieves this because fluency hides reasoning.
Here are some examples of strategic friction in a KM context: writing notes by hand forces you to slow down and think about the process. Reviewing past work manually, rather than relying on automated summaries, ensures you register connections and trigger useful memories.
These conditions cannot be improvised at the point of the person’s departure. They need time, permission, and deliberate design. For organizations, this means treating knowledge transfer as participation rather than an exit task. For departing employees and retirees, it means engaging with people more than ever.
Practical Ways to Involve Others
Creating the right conditions for knowledge transfer is often simpler than it sounds. Many organizations already use mentoring, shadowing, and shared work to support learning. These activities become much more powerful when they are treated deliberately as ways of surfacing and sharing expertise before it is lost.
Learning Through Shared Work
Shared judgment develops when people work through real problems together, explain their decisions, and see what “good” looks like in practice. The examples below support this by focusing conversations on live issues rather than abstract process.
- Mentoring creates continuity through relationships, allowing experience to be questioned, refined, and transferred over time.
- Joint problem-solving reveals how priorities are set and trade-offs made in practice.
- Short-term role swaps, shadowing, or secondments expose hidden dependencies that are otherwise taken for granted.
- Facilitated reflection sessions and after-action reviews make sense-making explicit, rather than leaving it implicit in experience.
Used consistently and mindfully, these practices keep knowledge in circulation. They allow expertise to be exercised, questioned, and reinforced while it is still active, rather than waiting to be extracted in a hurry.
Facilitation and Stewardship: Making Sharing Possible
Facilitation can play a role in deliberately interrupting “autopilot.” Skilled facilitators create safe conditions for asking questions. They help slow conversations down just enough to surface tacit reasoning, and they translate live discussion into insight that can be shared and reused. Facilitation shifts the dynamic from extraction to exploration.
This role is particularly valuable in hierarchical environments, or where long-serving professionals are reluctant to “explain themselves.” It enables knowledge to be surfaced without undermining authority or professional identity.
Stewardship sustains this work. Stewards maintain quality, relevance, and trust. They ensure that captured knowledge remains current, contextualized, and open to challenge as conditions change. Stewardship validates legacy without freezing it. Authority shifts from individuals to transparent, shared processes.
Facilitation and stewardship are not add-ons to knowledge management; they are the conditions that make shared expertise possible.
Authority and Knowledge
Knowledge gains authority through shared use. When it is discussed, tested, and challenged in real work, it remains trustworthy. When participation drops, even well-maintained documentation becomes a record of the past rather than a guide for what comes next.
This is the bridge to the next stage of the framework. Once judgment has been surfaced through shared work, it can be documented in ways that remain usable, findable, and open to reinterpretation. Without that social validation, documentation struggles to carry authority on its own.
Judgment Surfaces Through Interaction
Professional judgment does not move intact through documents alone. It becomes visible through interaction—when work slows enough to allow explanation, challenge, and shared sense-making.
This is why Involve Others sits at the center of the BRIDGE framework. The other stages depend on it. When judgment is surfaced socially, knowledge can travel. When it is not, documentation—however careful or complete—cannot carry continuity on its own.
The next stage of BRIDGE turns to what follows once judgment has been made visible: how to document knowledge accessibly, so it remains usable, findable, and meaningful for those who come next.
0 Comments