Frequently asked questions about thinking, epistemology, and cognitive tools. 1675 answers
Use tools and systems to catch errors that manual vigilance misses.
Every correction takes time and energy — reduce the error rate rather than just correcting faster.
Errors teach you more about your systems than successes do.
Identify one error or failure from the past two weeks — a missed deadline, a conversation that went poorly, a habit you dropped, a decision that produced a worse outcome than expected. Spend fifteen minutes writing answers to three questions: (1) What specifically went wrong — not the emotion, but.
Treating error feedback as emotional punishment rather than structural information. When something goes wrong, the instinct is to feel bad, resolve to try harder, and move on. This extracts zero structural learning from the error. The error told you something specific about where your system.
Errors teach you more about your systems than successes do.
The best systems detect and correct their own errors without manual intervention.
When you run several cognitive agents they need to work together not interfere with each other.
Identify three cognitive agents you currently run — habitual routines, decision rules, or structured practices that operate somewhat independently in your life. Write each one down with its trigger condition ('when X happens, I do Y') and its intended output. Now look for overlap: are there.
Treating coordination failure as a motivation problem rather than a structural one. When your morning routine conflicts with your weekly plan and you end up doing neither, the instinct is to blame willpower or discipline. But the problem is architectural: you have multiple agents issuing.
When you run several cognitive agents they need to work together not interfere with each other.
Some agents must run in a specific order — define the sequence explicitly.
Some agents must run in a specific order — define the sequence explicitly.
When agents need to share information define clearly how that information flows.
When agents need to share information define clearly how that information flows.
Common patterns like pipeline fan-out and consensus for coordinating multiple agents.
Coordination itself costs effort — keep the coordination cost proportional to the benefit.
Identify a project, team, or recurring collaboration in your life where more than three people are involved. Map every coordination mechanism currently in use: meetings, status updates, shared documents, chat channels, email threads, approval workflows. For each one, estimate the total.
Treating coordination overhead as a fixed cost that 'comes with the territory' rather than a variable you can design. When you stop measuring coordination cost, it expands invisibly. Meetings breed meetings. Status reports breed status reports. Every new tool, channel, or process adds friction.
Coordination itself costs effort — keep the coordination cost proportional to the benefit.
Sometimes combined agent behavior produces results none of the individual agents intended.
Sometimes combined agent behavior produces results none of the individual agents intended.
Your set of agents is an ecosystem — it needs balance and periodic assessment.
Use clear criteria to decide what to delegate, what to automate, and what to keep.