Frequently asked questions about thinking, epistemology, and cognitive tools. 4568 answers
Pick one category system you use daily — email folders, project labels, task statuses, note tags. Write down every category. Then ask two questions: (1) Can any single item legitimately belong in two or more of these categories? If yes, you have an overlap — your categories aren't mutually.
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..
The best category systems have no overlaps and no gaps.
Assigning types to objects restricts what operations make sense on them.
Assigning types to objects restricts what operations make sense on them.
Assigning types to objects restricts what operations make sense on them.
Assigning types to objects restricts what operations make sense on them.
Pick one field, category, or label you use regularly in your work or personal system — a task status, a priority level, a project phase, a contact type. Write down its current 'type': what values are allowed? If the answer is 'anything,' define a constrained set of 3-5 valid values. Then audit.
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.
Assigning types to objects restricts what operations make sense on them.
Objects often move through defined states — tracking these states enables workflow.
Objects often move through defined states — tracking these states enables workflow.
Objects often move through defined states — tracking these states enables workflow.
Objects often move through defined states — tracking these states enables workflow.
Objects often move through defined states — tracking these states enables workflow.
Pick one recurring process in your life — a project, a piece of writing, a personal goal, a purchase. Map the lifecycle states it actually passes through from beginning to end. Write each state as a node. Draw arrows between them showing which transitions are allowed. Then ask: are there states.
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.
Objects often move through defined states — tracking these states enables workflow.
Classifying items by importance or urgency enables systematic decision-making.
Classifying items by importance or urgency enables systematic decision-making.
Take your current task list — whatever tool you use. Assign every item one of four priority types: P0 (must happen today or something breaks), P1 (must happen this week or progress stalls), P2 (improves something but can wait), P3 (nice to have, no deadline). Count how many items land in each.
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.
Classifying items by importance or urgency enables systematic decision-making.
Defining roles for people and objects clarifies what each is responsible for.