Frequently asked questions about thinking, epistemology, and cognitive tools. 1498 answers
Progress you cannot see is progress you will not sustain. Externalize it or lose it.
Progress you cannot see is progress you will not sustain. Externalize it or lose it.
Progress you cannot see is progress you will not sustain. Externalize it or lose it.
Progress you cannot see is progress you will not sustain. Externalize it or lose it.
Progress you cannot see is progress you will not sustain. Externalize it or lose it.
Progress you cannot see is progress you will not sustain. Externalize it or lose it.
Choose one area where you are actively trying to improve — a skill, a habit, a project. Create a single document or spreadsheet with three columns: date, what you did, and what changed. Fill in the last seven days from memory (you will notice gaps — that is the point). From today forward, spend.
Building an elaborate tracking system that becomes its own project. The overhead of maintaining the tracker exceeds the value of the insight it produces. You stop updating it after a week, which feels like a failure, which makes you less likely to try again. The antidote is radical simplicity — a.
Progress you cannot see is progress you will not sustain. Externalize it or lose it.
Your physical and digital workspace is an externalization of your cognitive priorities. Design it deliberately, or it designs your thinking for you.
Your physical and digital workspace is an externalization of your cognitive priorities. Design it deliberately, or it designs your thinking for you.
Your physical and digital workspace is an externalization of your cognitive priorities. Design it deliberately, or it designs your thinking for you.
Your physical and digital workspace is an externalization of your cognitive priorities. Design it deliberately, or it designs your thinking for you.
Your physical and digital workspace is an externalization of your cognitive priorities. Design it deliberately, or it designs your thinking for you.
Your physical and digital workspace is an externalization of your cognitive priorities. Design it deliberately, or it designs your thinking for you.
Audit your current thinking environment — both physical and digital. List every object within arm's reach and every application visible on your screen right now. For each item, answer: does this support the cognitive work I need to do, or does it compete for my attention? Remove or hide three.
Treating workspace design as aesthetics rather than cognition. You reorganize your desk to look clean, buy matching containers, post motivational quotes — and mistake the visual satisfaction for cognitive improvement. The test is not whether your environment looks good. The test is whether it.
Your physical and digital workspace is an externalization of your cognitive priorities. Design it deliberately, or it designs your thinking for you.
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.
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.
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.
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.
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.
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.