What does it mean that delegation to documents?

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.

Try this: Identify one decision, process, or piece of context that you have explained verbally more than twice in the past month. Write a document that replaces those conversations. Keep it under two pages. Include: the situation or question the document answers, the key context someone needs to understand the answer, the decision or process itself, and why alternatives were rejected or are inappropriate. Share it with the next person who asks. Track whether they need a follow-up conversation or whether the document handled it. Your goal is a document that makes your verbal explanation unnecessary.