Frequently asked questions about thinking, epistemology, and cognitive tools. 1668 answers
Listing only the assumptions you are already aware of — the safe, obvious ones. The assumptions that destroy plans are the ones so deeply embedded you mistake them for facts. If your assumption list feels comfortable, you haven't gone deep enough. The real practice is surfacing what you don't know.
Treating the written list as a one-time exercise instead of a living document. You write your priorities once, feel the clarity, and never update them. Within two weeks the list is stale, your actual behavior has drifted, and you are back to reacting. The list only works if you revisit it — weekly.
Describing your mental model in prose instead of drawing it. Writing a paragraph about what you believe preserves the linear, narrative structure that hides gaps. A paragraph can skip over missing relationships because language flows forward and the reader — including you — fills in the blanks.
Waiting until the blocker is fully understood before writing it down. This is the most common failure — the belief that you need to diagnose the problem before you can name it. But diagnosis follows naming, not the other way around. If you wait until you understand the blocker completely, you will.
Tracking only when you feel bad — which creates a dataset that confirms you always feel bad. Or tracking for two days, seeing no pattern, and concluding the practice doesn't work. Energy and mood patterns only emerge across a minimum of seven days. Anything shorter is noise you're mistaking for.
Confusing capture with learning. The most common failure mode is treating externalization as transcription — copying quotes, saving bookmarks, highlighting passages, filing articles into folders. This produces an archive of other people's thinking, not a record of your own learning. If your.
Filtering feedback before you record it. You hear criticism, decide it was 'unfair' or 'they don't understand the context,' and don't write it down. Three months later, when someone else raises the same point, you treat it as new information instead of a confirmed pattern. The filter isn't.
Turning failure analysis into self-punishment. The goal is not to catalogue everything wrong with you — it's to extract usable signal from an outcome that didn't work. If your failure log reads like a list of personal deficiencies rather than a set of causal observations, you've replaced analysis.
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.
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.
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.
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..
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.
Believing you see reality as it is. The deepest failure mode of schema-driven perception is that it feels like seeing, not interpreting. You don't experience your schema filtering your perception — you experience a world that simply looks a certain way. The fish doesn't know it's in water. The.
Treating 'inherited' as synonymous with 'wrong.' Many inherited schemas are perfectly functional — language, hygiene practices, basic social norms. The failure is not having inherited schemas. The failure is never examining them, which means you cannot distinguish the ones that serve you from the.
Confusing introspection with inspection. Thinking 'I know my own biases' without writing them down is not schema inspection — it's self-flattery. Genuine inspection produces artifacts: written statements of what you believe, where it came from, and where it breaks. If you finish this exercise with.
Intellectually agreeing that 'the map is not the territory' while continuing to treat your schemas as if they were complete representations of reality. The most common version: you update your map once, then act on it for months without checking whether the territory has changed. The map-territory.
Two failure modes dominate. First: treating 'all models are wrong' as permission to ignore evidence and use whatever schema feels comfortable — epistemic laziness wearing a philosophical costume. Second: demanding perfect accuracy before acting, which produces analysis paralysis. The entire point.
Believing you can eliminate default schemas entirely. You cannot. Automatic cognition is not a flaw — it is the engine that lets you navigate complex environments without being paralyzed by deliberation. The failure is not having defaults. The failure is having defaults you have never surfaced,.
Treating this as a fun linguistics fact rather than an operational reality. You nod at the Sapir-Whorf examples, enjoy the bit about Russian blues, and then return to your default vocabulary unchanged. The lesson fails when it stays intellectual. It succeeds when you catch yourself mid-sentence,.
Two common failure modes. First: dismissing intuitive schemas as irrational and trusting only what you can explicitly articulate — which strips you of pattern recognition built from thousands of hours of experience. Second: treating every gut feeling as wisdom and refusing to examine it — which.
Treating every schema as universal. You learn a framework in one domain, it works brilliantly, and you assume it works everywhere. The failure isn't ignorance — it's over-extrapolation. The more successful a schema has been in its home domain, the harder it is to notice when you've carried it past.
Treating this lesson as an indictment of other people's schemas while exempting your own. The most expensive bad schemas are the ones you've held so long they feel like reality rather than interpretation. If you finish this lesson thinking 'I see how others fall into this trap,' you've.
Treating schema construction as something you learned about rather than something you practice. You can narrate the entire twenty-lesson arc of Phase 11 — definitions, properties, limits, dynamics, costs — and still walk into tomorrow's decisions using the same unexamined implicit models you had.