Skip to content
How to ThinkIn the Age of AI

Question

How do I practice system documentation?

beginner

Quick Answer

Open a blank document titled 'How My System Works.' Write answers to these five questions: (1) Where does new information enter my system? (2) How do I decide what to keep versus discard? (3) What does my review cadence look like — daily, weekly, monthly? (4) How do I find something I captured three months ago?

(5) When did I last change how my system works, and why? If you cannot answer any of these from memory, that is the gap this lesson addresses. The goal is a document that would let a motivated stranger — or your future self after a disruption — reconstruct your operating procedures.

Common pitfall: Documenting your tools without documenting your processes. You write 'I use Obsidian for notes and Todoist for tasks' and call it system documentation. But tools are not systems. The system is the set of decisions, triggers, cadences, and rules that determine how information flows through those tools. When you confuse tool inventory with system documentation, you lose everything that made the tools work when circumstances force a change.

This practice connects to Externalization Mastery — building it as a repeatable habit compounds over time.

Learn more in these lessons

  • Externalize your system itself

    Document your process for managing knowledge — not just the knowledge itself. Your system should be explicit enough that you could rebuild it from documentation alone.