Series ID: EDKS-BASIC-ZH-0114 · Lesson No.114 · Expert Maintenance: Knowledge Transfer
Knowledge Handoffs, Succession and Institutional Memory | 知识交接、传承与组织记忆
A handoff fails when the document transfers tasks but not the context needed to make the next good decision.
Expert knowledge often contains invisible parts: why a rule exists, which exceptions are dangerous, what has already been tried, which people or systems depend on the work, and what signals mean a situation has changed.
真正的知识交接不只是“把文件交出去”。它还要把判断依据、历史原因、依赖关系、例外情况、失败经验和下一步风险一起传下去。
Chinese Edition Hub · 中文版入口 · ← Lesson No.113 · Writing Requirements, Specifications and Acceptance Criteria
The knowledge-transfer map | 知识传承地图
- explicit knowledge
- tacit knowledge
- context
- decision history
- dependencies
- handoff
- shadowing
- teach-back
- succession
- institutional memory
1. Explicit knowledge | 显性知识
Knowledge that can be written down relatively easily:
- procedures
- contacts
- definitions
- system maps
- deadlines
2. Tacit knowledge | 隐性知识
Judgement built through experience:
- which warning matters
- when to escalate
- which exception is normal
- which shortcut is unsafe
3. Tacit knowledge is hardest to transfer | 隐性知识最难传
It often appears only when someone asks “why?” or encounters an unusual case.
4. Task handoff vs knowledge handoff | 任务交接 vs 知识交接
Task handoff transfers current work. Knowledge handoff transfers capability.
5. Handoff minimum | 最低交接内容
- current status
- owner
- next action
- deadline
- known risks
6. Knowledge handoff adds context | 知识交接还要加上下文
- why
- history
- dependencies
- decision rationale
- exceptions
7. Context | 背景
Explain the environment in which the work makes sense.
8. Decision history | 决策历史
Record major decisions and rejected alternatives where future teams may revisit them.
9. Why rejected options matter | 为什么要记录没选的方案
Otherwise a future team may repeat an old failed experiment.
10. Decision record | 决策记录
| Decision | Why | Evidence | Review trigger |
|---|---|---|---|
| Use Option B | higher reliability | pilot data | cost exceeds threshold |
11. Dependency map | 依赖地图
What systems, people, vendors, documents or approvals does the work depend on?
12. Upstream dependency | 上游依赖
What must happen before your process can begin?
13. Downstream dependency | 下游依赖
Who relies on your output?
14. Hidden dependency | 隐藏依赖
Knowledge often sits in personal messages, informal habits or one person’s memory.
15. Single-person risk | 单人风险
If one person’s absence stops the work, institutional memory is weak.
16. Bus-factor concept | 单点人员风险
The idea asks how many people can disappear before critical knowledge is lost.
17. Succession | 传承/继任
Succession prepares another person to assume responsibility, not merely receive files.
18. Shadowing | 跟岗观察
The successor watches the experienced person perform real work.
19. Reverse shadowing | 反向跟岗
The successor performs while the experienced person observes.
20. Teach-back | 反向讲解
Ask the receiver to explain the system back in their own words.
21. Teach-back exposes false agreement | 反向讲解暴露假理解
“Yes, I understand” is weaker evidence than successful explanation or execution.
22. Practice case | 实战案例
Give the successor an unfamiliar but realistic scenario.
23. Exception library | 例外案例库
Store recurring unusual cases and how they were handled.
24. Failure library | 失败案例库
Preserve failures, causes and lessons.
25. Success pattern library | 成功模式库
Also preserve what worked and why.
26. Runbook | 运行手册
Documents operational responses for recurring conditions.
27. Playbook | 场景手册
Useful when judgement and scenario variation matter.
28. Knowledge map | 知识地图
Shows where critical knowledge lives and who owns it.
29. Document hierarchy | 文档层级
- overview
- playbook
- SOP
- reference
- decision history
30. Do not bury critical knowledge | 不要埋掉关键知识
Layer documents so urgent users can find the action quickly.
31. Institutional memory | 组织记忆
The shared ability to remember important decisions, methods, failures and context beyond individual people.
32. Memory decays | 组织记忆也会退化
Documents become stale; people reinterpret old decisions; links break.
33. Knowledge review cycle | 知识复审周期
Assign owner and review date to high-value knowledge.
34. Stale-document signal | 过期文档信号
- old role names
- broken links
- obsolete tools
- contradictory steps
35. Version control | 版本控制
Know which version is current.
36. Archive, do not confuse | 归档但不要混淆
Historical records may be useful but must not look current.
37. Source of truth | 可信来源
Define where current operational knowledge is authoritative.
38. Handoff meeting | 交接会议
Use the meeting for questions, uncertainty and judgement—not merely reading documents aloud.
39. Handoff agenda | 交接议程
- scope
- current state
- dependencies
- risks
- decision history
- open questions
40. Open issues | 未解决问题
Do not pretend handoff is complete when important uncertainty remains.
41. Ownership transfer | 责任转移
State date/time when new owner assumes responsibility.
42. Confirmation | 接受确认
The receiver should explicitly accept ownership.
43. Sensitive knowledge | 敏感知识
Access should follow applicable privacy, security and organisational policy.
44. Do not overshare credentials | 不要把密码当知识交接
Use approved secure credential-management processes.
45. Knowledge loss after departure | 离职后的知识流失
Start succession before the final day where possible.
46. Emergency handoff | 紧急交接
Prioritise current state, risk, owner, access and next action.
47. Planned succession | 计划性交接
Add shadowing, teach-back and progressively independent work.
48. Cross-team handoff | 跨团队交接
Translate specialist assumptions for the receiving team’s context.
49. Cross-cultural handoff | 跨文化交接
Make implicit norms and expectations more explicit; do not rely on shared local context.
50. Mandarin transfer: “交接”可对应 handoff / handover | 用法依地区和语境
51. Mandarin transfer: “传承”常不是一个单词 | succession / knowledge transfer / continuity
52. Practice A | 练习 A
Build a one-page handoff summary for a recurring responsibility.
53. Practice B | 练习 B
Create a decision-history table with three past decisions.
54. Practice C | 练习 C
Run teach-back: receiver explains the system without looking.
55. Error clinic | 常见问题
| Problem | Repair |
|---|---|
| Only tasks transferred. | Add rationale/context. |
| One person holds key knowledge. | Add redundancy. |
| Old decisions forgotten. | Keep decision history. |
| Receiver says “understood”. | Use teach-back. |
| Docs stale. | Add owner/review cycle. |
56. First weak link diagnosis | 第一个卡点诊断
- receiver knows steps but cannot adapt → tacit knowledge gap.
- old mistakes repeat → institutional-memory gap.
- work stops with absence → succession gap.
- handoff accepted but errors rise → teach-back/practice gap.
- documents disagree → version-control gap.
57. Seven-day training cycle | 七天训练
| Day 1 | knowledge map | 知识地图 |
| Day 2 | handoff summary | 交接摘要 |
| Day 3 | decision history | 决策历史 |
| Day 4 | exception library | 例外库 |
| Day 5 | shadowing | 跟岗 |
| Day 6 | teach-back | 反向讲解 |
| Day 7 | ownership transfer test | 综合 |
58. Self-test | 自测
Transfer a real responsibility so another person can explain the rationale, perform the routine, handle an exception and know when to escalate.
59. For parents and teachers | 给家长和老师
Students can practise by teaching a process to a classmate and checking whether the classmate can execute it independently.
60. Final real-world challenge | 最终真实任务
- Choose critical responsibility.
- Map knowledge sources.
- Write current-state handoff.
- Add decision history.
- Add dependencies.
- Add exception cases.
- Run shadowing.
- Run teach-back.
- Transfer ownership.
- Retest after one week.
Next: Lesson No.115 | 下一课
The next lesson develops cross-cultural professional communication without stereotypes: explicitness, directness, hierarchy, turn-taking, politeness, time, feedback and shared working norms across international teams.
Lesson No.115 · Cross-Cultural Professional Communication · 跨文化专业沟通
Reference floor: expert-maintenance knowledge transfer. A handoff transfers judgement, context and capability—not files alone.
