Frequently asked questions about thinking, epistemology, and cognitive tools. 567 answers
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.
Treating all relationships as the same type — usually causal. When every connection in your mental model is "A causes B," you lose the ability to distinguish influence from structure, sequence from dependency, and correlation from mechanism. The result is a flat map where everything seems to cause.
Treating all relationships as undirected by default. This is the symmetry assumption — the implicit belief that if A relates to B, then B relates to A in the same way. You'll recognize this pattern when you assume that because you trust someone, they trust you; that because you depend on a tool,.
Treating all relationships as binary — either connected or not. You'll recognize this when your maps, lists, or mental models show connections without any indication of how strong, reliable, or significant each one is. The result is flat thinking: you treat a casual acquaintance's opinion with the.
Skipping prerequisites because they feel too basic. You will recognize this pattern when you repeatedly fail at something 'simple,' when explanations that should make sense remain opaque, or when you can follow a procedure but cannot adapt it to new situations. The deeper failure is confusing.
Confusing correlation with enabling. Two things that tend to appear together are not necessarily in an enabling relationship — one may not actually create the conditions for the other. You will recognize this failure when you invest heavily in a condition that you believed was enabling, but.
Resolving the tension prematurely. The most common failure is to feel the discomfort of contradiction and rush to eliminate it — either by dismissing one side as wrong, or by constructing a false compromise that waters down both ideas until neither has any force. You will recognize this pattern.
Confusing volume of evidence with independence of evidence. You'll recognize this pattern when you have accumulated many sources that all say the same thing — but they all derive from the same original study, the same methodology, or the same person's opinion repeated across platforms. Ten.
Treating examples as decoration rather than structure. You'll recognize this when you add an example after explaining an abstract concept and treat it as optional illustration — 'for instance...' tacked onto the end like a garnish. The deeper failure is the inverse: reasoning entirely in.