Frequently asked questions about thinking, epistemology, and cognitive tools. 1431 answers
Pick a problem you are currently working on. Write it down at three levels of abstraction: (1) the broadest framing — what is the category of problem this belongs to? (2) your current working framing — the level where you have been spending most of your time, (3) the most granular version — what.
Getting trapped at a single level and mistaking it for the whole picture. Abstract thinkers stay zoomed out and produce strategies that ignore implementation reality. Concrete thinkers stay drilled down and produce solutions that miss systemic patterns. The skill is not choosing the right level —.
Moving between levels of hierarchy is an active thinking technique.
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.
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.
Going deep in one branch versus wide across many branches are different strategies with different costs — and the right choice depends on whether you need resolution or coverage.
Going deep in one branch versus wide across many branches are different strategies with different costs — and the right choice depends on whether you need resolution or coverage.
Going deep in one branch versus wide across many branches are different strategies with different costs — and the right choice depends on whether you need resolution or coverage.
The most concrete level of any hierarchy is where actual implementation occurs.
The most concrete level of any hierarchy is where actual implementation occurs.
The most concrete level of any hierarchy is where actual implementation occurs.
The most concrete level of any hierarchy is where actual implementation occurs.
Pick one project or goal you are currently working on. Write it at the top of a page. Decompose it into 2-3 sub-components. Then decompose each sub-component until you reach items that are concrete enough to do in a single sitting without further clarification. Circle those leaf nodes. Count how.
Confusing intermediate categories with actionable work. You reorganize your project plan, refine your goal categories, and relabel your folder structure — all of which feels productive but produces no leaf-level output. The hierarchy gets more elegant. Nothing ships. The symptom is a system that.
The most concrete level of any hierarchy is where actual implementation occurs.
If a root concept is wrong everything organized beneath it inherits the error.
If a root concept is wrong everything organized beneath it inherits the error.
If a root concept is wrong everything organized beneath it inherits the error.
If a root concept is wrong everything organized beneath it inherits the error.
If a root concept is wrong everything organized beneath it inherits the error.
Pick one domain of your life — career, health, a side project, a relationship. Write down the single deepest assumption that everything else rests on. Not a tactic or a preference — the foundational belief. Now ask: if this root concept were wrong, what would collapse? What would suddenly make.
Treating a root concept as self-evident because everything you've built on top of it seems to work. The very success of the downstream structure makes the root feel more true than it is. You stop questioning it precisely because so much depends on it — and that dependency is exactly why.
If a root concept is wrong everything organized beneath it inherits the error.
Middle layers of hierarchy help you find things without getting lost in detail.