Key takeaway: Document the work that repeats, causes mistakes, or must be delegated without friction.
If a task happens often and errors create rework, document it. Repetition plus risk is the clearest signal that a process should exist.
If the work is strategic, exploratory, or heavily dependent on context, start with principles instead of rigid steps.
Treat documentation like a living tool. Lightweight updates after real-world use beat perfect manuals that nobody reads.