For each category, complete
Document the purpose each category serves by completing the sentence 'this category exists to [do what] for [whom]' to distinguish functional infrastructure from inherited furniture.
When This Fires
- Auditing your knowledge system's folder structure, tags, or categories
- When a classification system feels bloated or confusing
- During quarterly reviews of organizational tools and processes
- Whenever you add a new category and want to ensure it earns its overhead
Common Failure Mode
Keeping purposeless categories because removing them feels risky: "What if we need it?" The purpose test provides the data: if you can't articulate what the category does and for whom, its removal risk is near-zero. If something was misclassified under it, the items will surface naturally through other paths.
The Protocol
For each category in your system: (1) Complete: "This category exists to [specific function] for [specific user/purpose]." (2) If the sentence completes easily with specific terms → functional infrastructure. Keep. (3) If the sentence stalls or produces vague answers → inherited furniture. Remove or merge into a category with a clear purpose. (4) Apply during any classification system audit. A system where every category has a documented purpose is dramatically easier to use and maintain than one carrying inherited furniture.