Question
What is organizational memory?
Quick Answer
A well-written document delegates explanation, alignment, and decision context to the future.
Example: An engineering team debates the same database migration trade-offs in three consecutive sprint plannings. Nobody remembers what was already considered and rejected. Then one engineer writes a two-page Architecture Decision Record capturing the context, options evaluated, and rationale for the chosen approach. The next time the question surfaces — six months later, from a new hire — nobody needs to be in the room. The document explains the decision, the alternatives, and the reasoning. The document does the work the original engineer would have done, without requiring that engineer's time, presence, or memory.
This concept is part of Delegation Patterns in the How to Think curriculum.
Learn more in these lessons
Go beyond the answer
This topic is part of Delegate to AI Without Losing Judgment — a guided sequence of 16 lessons.
After completing this path you will run a working delegation boundary: a criteria framework for what goes to AI versus what stays with your judgment, specifications clear enough that AI output comes back usable, a verification practice that catches errors without redoing the work, and the warning signs of over-delegation before your judgment atrophies.
Start the path →