Frequently asked questions about thinking, epistemology, and cognitive tools. 1480 answers
Open a knowledge base, project folder, or bookmarks collection you actually use. Identify the top level (the broadest categories) and the leaf level (the individual items). Now look at the middle: are there intermediate levels that help you navigate from broad to specific? If the middle is missing.
Building intermediate levels that reflect how the content is organized in theory rather than how you actually search for it. A folder called 'Q3 2025 Deliverables' makes sense to the person who created it during Q3 2025. Six months later, nobody navigates by quarter — they navigate by client, by.
Middle layers of hierarchy help you find things without getting lost in detail.
What sits at the top of your hierarchy reflects what you consider most important.
Explaining your knowledge to someone else forces you to integrate it.
When you update a schema you must also update everything built on top of it.
Pick one belief or mental model you've updated in the last year. Write it down as 'Old schema: X → New schema: Y.' Then list every decision, habit, relationship, or system that was built on the old schema. For each one, mark it: already migrated, needs migration, or can't migrate yet. You now have.
Updating the schema in your head while leaving the downstream systems untouched. You'll notice this when your new understanding keeps colliding with your old behavior — you believe in delegation but still review every pull request, you believe in rest but still feel guilty on weekends. The belief.
When you update a schema you must also update everything built on top of it.
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.
Teams that share mental models coordinate better than teams that do not.
Dividing things into only two groups forces a false simplicity.
Lazy or inconsistent categorization creates a growing mess that eventually must be cleaned up.
The connections between things carry as much meaning as the things themselves.
Connections that exist today may not have existed yesterday or may not exist tomorrow.
Real knowledge often has items that belong to multiple parent categories. When you force every concept into a single branch of a tree, you destroy information. Lattice structures — where a node can have multiple parents — preserve the multidimensional nature of knowledge. The tree is a special.
What sits at the top of your hierarchy reflects what you consider most important.
Unusual or extreme situations reveal where your schema breaks down.
Explaining your schema to someone else and hearing their objections is a form of validation.
Deliberately try to break your own mental model before relying on it.
Even a well-tested schema may fail in new contexts or at different scales. Validation tells you where a schema works, not that it works everywhere. The boundaries of your tested conditions are the boundaries of your warranted confidence.
Confidence based on tested schemas is categorically different from confidence based on untested assumptions.