Frequently asked questions about thinking, epistemology, and cognitive tools. 190 answers
Treating this lesson as an indictment of other people's schemas while exempting your own. The most expensive bad schemas are the ones you've held so long they feel like reality rather than interpretation. If you finish this lesson thinking 'I see how others fall into this trap,' you've.
Treating schema construction as something you learned about rather than something you practice. You can narrate the entire twenty-lesson arc of Phase 11 — definitions, properties, limits, dynamics, costs — and still walk into tomorrow's decisions using the same unexamined implicit models you had.
Treating your current categories as 'the way things are' rather than a system you chose. You'll know you've fallen into this when someone suggests a different way of grouping and your first reaction is 'that's wrong' rather than 'that's different — what would it make visible?' The failure is.
Treating your own categories as objective features of reality. You will know this is happening when someone proposes an alternative categorization and your first reaction is that they are wrong rather than that they are serving a different purpose. The emotional signature is irritation at.
Creating explicit categories and then never revisiting them. The point of making categories explicit is not to freeze them — it's to make them visible so they can be evaluated and improved. If you define your categories once and treat them as permanent, you've just traded one kind of rigidity.
Replacing every binary with a spectrum just to feel nuanced. Some decisions genuinely require a binary output at the end — ship or don't ship, accept the offer or decline it. The lesson isn't 'never use binaries.' It's that the reasoning process should preserve information as long as possible.
Turning everything into a spectrum, including things that genuinely are binary. Some categories are discrete: a transaction either committed or it didn't, a patient is either pregnant or not. The skill isn't abolishing categories — it's recognizing which phenomena are continuous and ensuring your.
Building a taxonomy that is too deep. You create seven levels of nesting because it feels rigorous, then abandon the system because filing anything requires navigating a maze. The hierarchy becomes a bureaucracy. Most useful personal taxonomies operate at three to four levels. Beyond that, the.
Two common failures. First: achieving mutual exclusivity by making categories so narrow that gaps appear everywhere. You split 'Communication' into 'Email' and 'Slack' and miss phone calls entirely. Second: achieving collective exhaustiveness by making categories so broad that everything overlaps..
Over-constraining too early, before you understand the domain. A type system that rejects legitimate inputs is worse than no type system at all — it trains people to work around your constraints rather than within them. The discipline is knowing when you have enough signal to lock down a type and.
Tracking status without defining valid transitions. When any state can follow any other state — when a task can jump from 'not started' to 'done' without passing through 'in progress' — you lose the workflow that status types are supposed to provide. Status becomes decoration instead of.
Treating all items as high priority, which collapses the type system into a single undifferentiated list. If everything is urgent, nothing is — and you are back to scanning 47 items with no structural advantage. The other failure is building elaborate priority schemes with seven or more levels.
Assigning role types once and treating them as permanent fixtures rather than context-dependent labels. Roles are relational and situational — someone who is the decision-maker for architecture may be merely informed on hiring. The failure is freezing roles into identity rather than treating them.
Believing the debt is too small to matter. Each individual inconsistency is trivial. That's precisely why it accumulates — the cost is invisible at the point of creation and only becomes visible when you need the system to actually work. By then, the cleanup cost has grown by orders of magnitude.
Two failure modes bracket this lesson. The first is reclassification paralysis: refusing to change categories because the change feels like admitting you were wrong. This is classification debt compounding (L-0232) — the longer you avoid reclassification, the larger the eventual cleanup. The.
Treating miscategorization as a minor clerical issue — a wrong label that can be corrected later. In practice, categories activate entire action chains. By the time you notice the label was wrong, the actions have already compounded. The cost is never just the label. It is everything the label set.
Treating your categories as neutral descriptions of reality rather than as value-laden choices. You'll know you've fallen into this when you can't imagine organizing the same material differently — when the categories feel inevitable rather than chosen. The moment classification feels obvious is.
Treating the prototype as the definition. When 'productive day' prototypically means 'eight hours of deep coding,' you start classifying days with difficult conversations, strategic planning, or mentoring as 'unproductive' — even when they created more value. The prototype becomes a filter that.
Treating boundary cases as exceptions to ignore rather than evidence to examine. The instinct is to force the ambiguous item into the nearest category and move on — filing the tomato under 'vegetable' and forgetting about it. This preserves the illusion that your system is complete while.
Two failure modes bracket the problem. The first is dimensional poverty: classifying items along only one dimension and treating it as sufficient. You file notes by topic and then cannot find the ones relevant to a project. You sort tasks by status and then cannot identify which ones belong to a.
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.
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.
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.
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.