If decisions and lessons live only in people, inboxes, and end-of-project memories, turnover and time erase them—and teams pay to reconstruct what the organization once knew.

Organizational memory is not a document dump. Useful memory preserves the problem, context, decision, evidence, result, owner, and conditions under which the lesson remains valid. Excess documentation becomes stale bureaucracy, so the goal is selective externalization with ownership, maintenance, and retirement.

Contents (6 sections)

Evidence snapshot

Supported by cited sources
FindingScope or qualification
A 2023 systematic review synthesized 91 empirical studies of turnover-induced knowledge loss.Effects depend on who leaves, what they know, and the transfer mechanisms.
NASA found end-of-project lesson collection difficult because staff were transitioning and memory was fading.High-stakes case evidence; continuous capture worked better in another mission.
GAO found NASA did not routinely identify, collect, or share lessons and could not assure future use.Historical institutional failure later addressed by reforms.

What the evidence does not prove

Supported by cited sources

Documentation costs time, tacit judgment cannot be fully captured, and old guidance can freeze bad practice. Turnover can also introduce useful new knowledge.

Why different stakeholders can care

Proposed

Workers avoid repeated failure; managers preserve continuity; new hires learn faster; customers receive consistent service; and institutions become less dependent on one person or expert.

Question to investigate

Open question

What The Solar Guild must test

Research question

Can a minimal maintained record let a newcomer reproduce the right action faster, while remaining fresh enough to retire obsolete guidance?

Core sources

Supported by cited sources
Systematic review of turnover-induced knowledge lossNASA Lesson 600 — Knowledge CaptureGAO — NASA Lessons Learned

References and limits

This page is published by The Solar Guild. Sources are listed so readers can inspect the basis of the page. A project statement is not independent proof unless the page identifies supporting outside evidence.

  • Problem 12 in The Solar Guild — Twenty Problems Worth Testing v1.0
  • Direct source links are provided above; quantitative claims retain their stated scope and qualification
  • The Solar Guild's response is explicitly separated from evidence that the problem exists