Frequently asked questions about thinking, epistemology, and cognitive tools. 9738 answers
Treating the finished map as the deliverable rather than the mapping process as the deliverable. When teams create relationship diagrams to "document architecture" or "share context," they often produce a single artifact and then file it away. The map becomes a static record — a snapshot of what.
The act of mapping relationships generates new insights about the system. You do not map what you already understand — you map in order to understand. The diagram is not a record of finished thinking. It is the medium in which thinking happens.
Before resolving a contradiction make the strongest possible case for each side.
Integrating your schemas is also integrating your identity — who you are becomes more coherent.
Define in advance what evidence would cause you to abandon a course of action.
Errors teach you more about your systems than successes do.
Agent monitoring provides the data you need to optimize your cognitive systems.
Consistent 1% improvements produce transformative results over time.
Professional environments are designed to distribute authority hierarchically. Self-authority at work means knowing when to follow the hierarchy and when your independent judgment must override it.
Place capture tools where you will see and use them without having to remember. The best capture system is one your environment triggers automatically — not one that depends on willpower or recall.
Pick one behavior you've been trying to change through willpower alone. Map the current context: what cues trigger the unwanted behavior? What friction exists before the desired behavior? Now redesign one element — move an object, change a default, set a visual cue, or create an implementation.
Designing contexts once and never iterating. Your first context design is a hypothesis, not a solution. If the new arrangement doesn't change behavior within a week, the cues are wrong or the friction is in the wrong place. Context design is an ongoing practice, not a one-time setup.
Rather than relying on willpower create contexts that make desired behavior natural.
When A affects B and B affects A you have a system that can amplify or stabilize itself.
Agents for how to respond in social situations like receiving criticism or giving feedback.
Sometimes combined agent behavior produces results none of the individual agents intended.
Identify three agents (habits, routines, tools, or practices) in your current life that operate independently but share a context — your morning, your work process, your creative practice. For each, write down its individual rule: what it does and when. Then observe: what behavior has emerged from.
Trying to design emergence directly. Emergence is a property of interaction, not intention. When you see a useful emergent pattern — like three routines producing a flow state you never planned — the instinct is to formalize it into an explicit rule. But the moment you replace the interacting.
Sometimes combined agent behavior produces results none of the individual agents intended.
Compare agents against each other and against baselines to identify relative performance.
Evolution built in a tendency to defer to authority — recognize when it activates.
The structure of your environment determines your default behavior.
Link capture to existing habits like morning coffee or commute time so it becomes automatic rather than effortful.
A weekly review catches anything your daily capture missed — it is the redundancy layer that keeps your entire epistemic system trustworthy.