Knowledge Retention, Archiving, and Lessons Learned
This domain tests retention and lessons-learned discipline from project start to archive. Retention balances legal and regulatory duties, operational need, and cost; archiving preserves context and access; lessons learned must change behavior.
Rules
- Retention schedule: record class, trigger event, retention period, disposition, legal hold.
- Archive with metadata, access rules, and an index; separate archive from backup.
- Lessons process: identify, validate, analyze, recommend action, assign owner, share, apply, verify.
- Collect throughout, not only at closure; use after-action reviews and retrospectives.
- Distinguish lessons identified from lessons learned (applied and embedded).
- Plan for turnover: exit interviews, knowledge handover, succession, mentoring.
Worked example
At closure, a team has 40 lessons but no changes. Hold a validation workshop to remove blame and confirm causes; convert five into specific updates (checklist item, template field, risk prompt); assign owners and dates; archive the rest with metadata and a retention class. Reasoning: volume is not learning. Action, ownership, and embedding in process create reuse; archiving preserves evidence.
Traps
- Running lessons learned as a blame session.
- Collecting only at the end.
- Storing lessons without actions or owners.
- Keeping everything forever or deleting too early.
- Confusing backup with archive.