KM-301a · Module 1

Taxonomy Anti-Patterns

5 min read

Most taxonomy failures are not random — they follow recognizable patterns. The same structural mistakes recur because they are intuitive at small scale and catastrophic at large scale. Recognizing these anti-patterns early is cheaper than fixing them after the knowledge base has grown around them.

  1. The Mega-Tree A hierarchical taxonomy that grows indefinitely, adding depth rather than breadth. Starts as a reasonable three-level tree. Over 18 months, reaches seven levels. Users navigating level six have lost context about where they are in the structure. The canonical symptom: team members cannot navigate to content without using search because the tree is too deep to traverse mentally. Fix: impose a depth limit (four levels maximum for most domains), and when depth pressure appears, ask whether the category should be promoted to a top-level facet instead.
  2. The Folder-as-Silo A taxonomy that mirrors organizational structure rather than knowledge structure. "Marketing," "Engineering," "Legal" as top-level categories. When a knowledge item has stakeholders in two departments, it either lives in one and is invisible to the other, or it gets duplicated and diverges. The taxonomy reflects org chart politics, not knowledge retrieval needs. Fix: structure taxonomy around knowledge type and use case, not organizational ownership. Use metadata tags for ownership.
  3. The Orphan Content Problem Content that does not fit cleanly into the existing taxonomy and gets placed in a catch-all "General," "Miscellaneous," or "Other" category — or filed somewhere arbitrary. Over time, these categories accumulate valuable content that becomes effectively invisible. The symptom: teams say "I know we documented that somewhere but I can't find it." The fix: when content doesn't fit, treat it as a taxonomy gap, not a filing failure. Either create the right category or redesign the relevant branch.
  4. The Premature Hierarchy Building a deep, elaborate taxonomy structure before the content exists to fill it. Empty or near-empty categories that represent aspirational organization rather than actual knowledge. The structural overhead discourages contribution — contributors either cannot find the right category or create near-duplicates. Fix: taxonomies should follow content, not precede it. Build the minimum viable structure, let content accumulate, then refactor toward the natural patterns that emerge.

Do This

  • Audit for orphan content quarterly — every item in "General" is a taxonomy debt
  • Cap hierarchy depth at four levels; escalate to facet before adding level five
  • Structure taxonomy around retrieval patterns, not org structure
  • Build taxonomy incrementally from real content rather than speculatively

Avoid This

  • Create "Miscellaneous" or "Other" categories that collect unfiled content permanently
  • Allow hierarchy depth to grow without a governance decision
  • Mirror the org chart and call it information architecture
  • Build 40 empty categories before any content exists to populate them