Question
What is document your processes?
Quick Answer
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.
Example: A software engineer keeps a Zettelkasten for technical notes, a task manager for projects, and a reading log for books. But none of these tools document how she decides what goes where, what her weekly review looks like, or what triggers her to archive versus delete. When her laptop dies, she recovers the data from backups — but spends three months recreating the invisible workflows that made the data useful. The knowledge survived. The system didn't.
This concept is part of Externalization Mastery in the How to Think curriculum, which builds the epistemic infrastructure for externalization mastery.
Learn more in these lessons
- Externalize your system itself
- Document your agents
Written agent descriptions can be reviewed refined and shared.