Frequently asked questions about thinking, epistemology, and cognitive tools. 9738 answers
The connections between things carry as much meaning as the things themselves.
An item can be contained within a hierarchy level or merely referenced from it.
The payoff of building maintaining and connecting schemas is an integrated understanding — a coherent, flexible, self-reinforcing knowledge structure that compounds in value over time, producing fluency, insight, and the deep satisfaction of genuine comprehension.
For most decisions good enough is better than perfect because the search cost exceeds the improvement.
Choose the option you would least regret in five years.
When a beneficial loop exists invest in making it stronger and faster.
Effectiveness means your agent produces the intended outcome, not just that it runs.
Pick one cognitive agent you already run — a decision-making heuristic, a weekly review, a conflict-resolution protocol, anything that fires in response to a trigger and is supposed to produce a specific result. Define its intended outcome in one sentence. Then review the last five times it fired.
Confusing reliability with effectiveness. Your agent fires every time it should — perfect reliability score — so you assume it's working. But firing is not the same as producing the intended result. A smoke detector that sounds every time there's smoke is reliable. A smoke detector that sounds.
Effectiveness means your agent produces the intended outcome, not just that it runs.
When retiring an agent ensure its responsibilities transfer to a new agent or are consciously dropped.
Record not just what you decided but why — because your future self will rewrite the reasoning after the fact, and you will never notice it happening.
Pick one decision you made in the last week — what to work on, which tool to use, whether to attend a meeting, anything. Write a five-line decision record: (1) What you decided. (2) What alternatives you considered. (3) What information you had. (4) What you were optimizing for. (5) What would.
Documenting only the conclusion without the context. Writing 'We chose React' tells future-you nothing. Writing 'We chose React because the team already knows it, the timeline was six weeks, and we valued shipping speed over long-term performance' tells future-you everything. The decision without.
The most valuable thing to capture is why you chose what you chose. Decisions decay faster than facts — and unlike facts, they cannot be reconstructed after the outcome is known.
What is not connected to anything else is either irrelevant or disconnected by mistake.
A link labeled causes is more useful than a generic link labeled related.
Explaining your knowledge to someone else forces you to integrate it.
Reviewing key conditions before starting a task catches errors before they propagate.
Identify one recurring task you perform at least weekly — sending a report, publishing content, deploying code, running a meeting, submitting an invoice. Write a pre-flight checklist of 5-7 conditions that must be true before you execute. These are not steps in the task itself; they are conditions.
Treating a pre-flight check as a formality rather than a genuine verification. The most dangerous version of this is 'flow-through checking' — running your eyes down the checklist and marking each item complete without actually testing the condition. Airline investigators call this 'checklist.
Reviewing key conditions before starting a task catches errors before they propagate.
Delegating too much creates disconnection from the work that matters and atrophies critical skills.
The act of writing generates new thoughts rather than merely documenting existing ones. Writing is not transcription — it is the primary mechanism through which vague intuitions become precise understanding.