Frequently asked questions about thinking, epistemology, and cognitive tools. 9738 answers
Categories reduce complexity by treating similar things as equivalent for a given purpose.
Categories reduce complexity by treating similar things as equivalent for a given purpose.
Categories reduce complexity by treating similar things as equivalent for a given purpose.
Categories reduce complexity by treating similar things as equivalent for a given purpose.
Pick one classification system you use daily — your email labels, your task priorities, your contact groups. Write down three things that system compresses away (details it ignores) and three things it preserves (distinctions it keeps). Then ask: is the compression ratio right? Are you losing.
Two failure modes in opposite directions. Over-compression: you reduce so aggressively that distinctions which matter for your decisions disappear — like triaging all customer feedback into 'positive' and 'negative' when the actionable signal lives in the subcategories. Under-compression: you keep.
Categories reduce complexity by treating similar things as equivalent for a given purpose.
The best category systems adapt as you learn more about what you are organizing.
The best category systems adapt as you learn more about what you are organizing.
The best category systems adapt as you learn more about what you are organizing.
Pick the classification system you've used longest — your file folder structure, your task management categories, your note-taking tags, your bookshelf organization. Now conduct an evolution audit. First, write down the original categories as you remember them. Then write down the current.
Treating your classification system as finished. You'll recognize this pattern when you keep forcing new items into categories that no longer fit, when your 'Miscellaneous' or 'Other' bucket grows faster than any named category, or when you find yourself working around your own system rather than.
The best category systems adapt as you learn more about what you are organizing.
The connections between things carry as much meaning as the things themselves.
The connections between things carry as much meaning as the things themselves.
The connections between things carry as much meaning as the things themselves.
Pick five concepts you've captured in your knowledge system. Write each one on a separate card or line. Now draw every connection you can identify between them — label each connection with a verb: 'causes,' 'enables,' 'contradicts,' 'supports,' 'requires.' Count the relationships. You should have.
Collecting entities obsessively while never mapping what connects them. You end up with a warehouse of isolated facts — perfectly organized, perfectly useless. The notes are there. The understanding isn't. You'll recognize this failure when you can't explain how any two ideas in your system relate.
The connections between things carry as much meaning as the things themselves.
Writing down how two ideas relate prevents assuming a connection that does not exist.
Writing down how two ideas relate prevents assuming a connection that does not exist.
Writing down how two ideas relate prevents assuming a connection that does not exist.
Pick a domain where you make frequent judgments — your work, a hobby, a recurring decision. Write down five pairs of things you believe are related (e.g., 'morning exercise' and 'productive workday,' or 'client responsiveness' and 'project success'). For each pair, write one sentence articulating.
Operating on assumed relationships without examining them. You will recognize this pattern when you make decisions based on connections you have never articulated — when you avoid a strategy because you assume it conflicts with a goal (without checking), when you invest in an activity because you.