Frequently asked questions about thinking, epistemology, and cognitive tools. 9738 answers
Reserve low-attention tasks for times when deep focus is not available.
For one full workweek, maintain two separate task lists: a Deep List (tasks requiring sustained focus, creative synthesis, or complex reasoning) and a Shallow List (tasks you could do while mildly distracted — email, scheduling, filing, routine updates, approvals). Each morning, schedule Deep List.
Two opposite traps. First: treating shallow work as the enemy and trying to eliminate it entirely, which causes administrative debt to pile up until it becomes an emergency that destroys an entire deep work day. Second: letting shallow work colonize your peak hours because it feels productive —.
Reserve low-attention tasks for times when deep focus is not available.
Most people are wrong about how they spend their attention — measure it.
Observation and evaluation are neurologically distinct operations. Your brain can register what is happening before deciding whether it is good or bad — but only if you train the pause between the two. Collapsing them into a single act distorts perception and triggers defensive reactions in others.
Temporarily releasing the need for certainty improves the quality of your observations.
Strong feelings about an observation usually mean it touches something important.
Your mental and physical energy follows predictable patterns you can map and leverage.
Deep engagement with fewer sources extracts more signal than shallow engagement with many. Depth builds the perceptual structures that make signal detection possible. Breadth, pursued without depth, produces the illusion of being informed while degrading your capacity to understand anything.
Social media platforms are not neutral information channels. They are adversarial environments engineered to maximize engagement by disguising noise as signal — and your nervous system is the target.
Imagining failure in advance corrects for optimistic perception biases.
Imagining failure in advance corrects for optimistic perception biases.
Information has no inherent meaning. Meaning is constructed at the intersection of information and context. Change the context, and the same data, sentence, or signal means something entirely different.
Recording the context of a decision prevents future confusion about why you made it. Without a written record of the forces, constraints, and reasoning at the moment of choice, your future self — and everyone else — will reconstruct a fiction and call it memory.
Choose three decisions you have made in the past month — one personal, one professional, and one that felt obvious at the time. For each decision, write a Decision Context Record using this format: (1) Date and decision statement — what you decided, in one sentence. (2) Context — the specific.
The most common failure is not refusing to document decisions — it is documenting the decision without documenting the context. People write "We chose React" without writing "because our team had three React developers and zero Angular developers, we had a six-week deadline, and the client.
Recording the context of a decision prevents future confusion about why you made it. Without a written record of the forces, constraints, and reasoning at the moment of choice, your future self — and everyone else — will reconstruct a fiction and call it memory.
Always give your audience the context they need to interpret your message correctly.
Assumptions you never write down are assumptions you never question. Every plan, decision, and belief rests on invisible premises — and the invisible ones are the ones that destroy you.
A personal dashboard transforms scattered signals into a coherent picture of your current state — making drift visible before it becomes crisis.
Teams that share mental models coordinate better than teams that do not.
Choose a project or recurring collaboration where you and at least one other person must coordinate. Together, write down the shared schema that governs how you work: What are the key terms you both use? What is the implicit process flow? Where do you agree on definitions, and where have you been.
Assuming alignment exists because the words sound the same. Two people can say 'we need better testing' and mean completely different things — one means more unit tests, the other means more user research. Shared vocabulary without shared schema is the most common collaboration failure, and it is.