Frequently asked questions about thinking, epistemology, and cognitive tools. 1498 answers
An idea that looks like one thing is often several things fused together, each carrying unstated assumptions that silently constrain what you can do with it.
Take one belief you currently hold about your work, career, or a project — something you'd state as a single sentence. Write it down. Now decompose it: list every assumption that must be true for that sentence to hold. Aim for at least four. For each assumption, ask: 'Have I actually tested this,.
Decomposing the idea intellectually but continuing to act on it as a monolith. You'll know this is happening when someone challenges one part of your plan and you defend the whole thing — because in your mind, it's still one idea. The decomposition only works if each piece gets evaluated.
An idea that looks like one thing is often several things fused together, each carrying unstated assumptions that silently constrain what you can do with it.
What you saw and what you concluded from it are distinct and must not be fused.
Pick one situation from the last 24 hours that triggered a strong reaction. Write two separate entries: (1) the raw observation — only what a camera would record, and (2) the interpretation — what you concluded it meant. Look at the gap between them. That gap is where most of your errors live.
You write the observation and the interpretation in the same sentence, believing you're being objective. 'He was rude in the meeting' feels like an observation, but it's already an interpretation. The observation is: 'He interrupted me twice and did not make eye contact.' Until you can reliably.
What you saw and what you concluded from it are distinct and must not be fused.
Each atom exists in relationship to others — atomicity is about self-containment not loneliness.
Open your note system and pick any ten recent atomic notes. For each note, ask: what other note does this one support, contradict, extend, or depend on? Create at least one explicit link from each note to another. When you are done, you should have at least ten new connections that did not exist.
Creating atomic notes and filing them into folders by topic, then never linking them to anything. The notes are technically self-contained, but they function as isolated fragments because nothing connects them. You end up with a well-organized graveyard: everything is in its place, nothing is in.
Each atom exists in relationship to others — atomicity is about self-containment not loneliness.
A tag is the simplest way to declare that two atoms share something in common.
Open your note system and pick 10 recent atoms. For each one, add 1–3 tags that answer this question: 'If I had this same insight again in a different context, what word would I search for?' Do not overthink. Do not build a taxonomy first. Tag by instinct, then review your tags as a batch. Notice.
Creating a tag taxonomy before you have enough atoms to need one. You design a careful hierarchy — #work/meetings/retrospectives — and then spend more energy maintaining the structure than writing the notes. The system collapses under its own organizational weight. The opposite failure is never.
A tag is the simplest way to declare that two atoms share something in common.
Write down insights from conversations immediately — social memory is especially lossy.
Your emotions are data, not noise. Recording them creates the only dataset that reveals what your conscious reasoning consistently misses.
When you trust your capture system your mind stops trying to hold everything.
Conduct a cognitive freedom audit. Set a timer for 60 minutes during your next session of focused work — writing, designing, coding, or any task requiring sustained attention. Keep a tally sheet beside you with two columns: 'Captured' and 'Held.' Every time an unrelated thought intrudes, note.
Confusing system completeness with system trust. You build an elaborate capture infrastructure — multiple apps, complex workflows, automated integrations — and assume that because the system is comprehensive, you trust it. But trust is not a feature of the system. Trust is a psychological state.
When you trust your capture system your mind stops trying to hold everything.
Every time you switch tasks, you pay a recovery tax — between 10 and 25 minutes of degraded cognition while your brain reloads the previous context. This cost is invisible because you feel busy the entire time.
Your attention goes where your intention already pointed it. Decide what to focus on before you start, and your perceptual system reorganizes around that decision — filtering, prioritizing, and surfacing what matters while suppressing what does not.