Classification friction reveals missing categories — map what resisting items have in common
When items consistently resist classification in your system (you hesitate, force-fit, or leave uncategorized), map what those resistant items have in common to diagnose missing categories that represent dimensions you care about but haven't encoded.
Why This Is a Rule
Classification friction — the hesitation, force-fitting, or abandonment that happens when items don't fit existing categories — is not noise. It's a diagnostic signal that your classification system is missing a dimension. The items that resist classification share a property that matters to you but hasn't been encoded into the system.
Force-fitting is the most damaging response: you stuff the item into the closest-but-wrong category to avoid the discomfort of having nowhere to put it. The item is now findable (under the wrong label), which is worse than being unfindable — it produces false matches when you search the wrong category and missed matches when you search the right one.
Mapping what resistant items have in common reveals the missing dimension. If your project management system has tasks that keep being force-fit into "bug" or "feature" when they're actually "technical debt cleanup" — the missing category is technical debt. Adding it eliminates the friction and makes an invisible class of work visible.
When This Fires
- When you consistently hesitate about where to classify certain items
- When items accumulate in "Miscellaneous" or "Other" categories
- After noticing force-fit classifications that feel wrong
- During system audits when uncategorized items have accumulated
Common Failure Mode
Treating resistant items as edge cases rather than as symptoms: "Those are just weird items that don't fit neatly." If the resistance is consistent (3+ items over time), it's not an edge case — it's a missing category. The resistance pattern is telling you something about your mental model that hasn't been encoded yet.
The Protocol
When classification friction recurs: (1) Collect the items that resisted classification (hesitated over, force-fit, or left uncategorized). (2) Map what they have in common: what property do they share that your existing categories don't capture? (3) If a shared dimension emerges → create a new category for it. The dimension was already important to you (that's why the friction existed); you just hadn't encoded it. (4) Reclassify force-fit items into the new category. The friction should disappear for this class of items.