Frequently asked questions about thinking, epistemology, and cognitive tools. 4568 answers
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.
When everything important is externalized — every decision, reasoning chain, emotion, goal, assumption, commitment, priority, mental model, blocker, energy pattern, learning, feedback signal, failure, progress marker, thinking condition, and system design — you gain complete cognitive freedom. The.
When everything important is externalized — every decision, reasoning chain, emotion, goal, assumption, commitment, priority, mental model, blocker, energy pattern, learning, feedback signal, failure, progress marker, thinking condition, and system design — you gain complete cognitive freedom. The.
When everything important is externalized — every decision, reasoning chain, emotion, goal, assumption, commitment, priority, mental model, blocker, energy pattern, learning, feedback signal, failure, progress marker, thinking condition, and system design — you gain complete cognitive freedom. The.
When everything important is externalized — every decision, reasoning chain, emotion, goal, assumption, commitment, priority, mental model, blocker, energy pattern, learning, feedback signal, failure, progress marker, thinking condition, and system design — you gain complete cognitive freedom. The.
When everything important is externalized — every decision, reasoning chain, emotion, goal, assumption, commitment, priority, mental model, blocker, energy pattern, learning, feedback signal, failure, progress marker, thinking condition, and system design — you gain complete cognitive freedom. The.
Conduct the Phase 10 Integration Audit. For each of the twenty domains covered in this phase, answer the question: Is this domain currently externalized in my system? Use a three-point scale: (0) not externalized at all, (1) partially externalized or inconsistently captured, (2) systematically.
Believing you have achieved externalization mastery because you have a lot of notes. Volume is not mastery. A person with 10,000 notes and no system for reviewing, connecting, or acting on them has an archive, not an extended mind. Externalization mastery is not about how much you have captured..
When everything important is externalized — every decision, reasoning chain, emotion, goal, assumption, commitment, priority, mental model, blocker, energy pattern, learning, feedback signal, failure, progress marker, thinking condition, and system design — you gain complete cognitive freedom. The.
A schema is a mental model that has been externalized, named, and structured so it can be examined, tested, and improved — turning invisible cognitive habit into visible cognitive infrastructure.
A schema is a mental model that has been externalized, named, and structured so it can be examined, tested, and improved — turning invisible cognitive habit into visible cognitive infrastructure.
Identify one recurring decision you make at work or in life — how you choose what to work on first, how you evaluate whether a meeting was productive, how you decide what to read. Write down the rule you actually follow (not the rule you think you should follow). Name it: 'My [domain] schema.'.
Confusing knowing about schemas with having explicit schemas. You can read this entire lesson, nod at every paragraph, and still operate tomorrow on the same invisible mental models you used yesterday. The failure is intellectual agreement without externalization. If your schema is not written.