The Naming Problem

Taxonomy names are the interface between the structure and the people using it. Two categories named "Client Onboarding" and "Customer Onboarding" create a split that looks like an organizational decision but is actually a naming failure. Users learn that the system has an inconsistency and start losing confidence in whether they found everything relevant. At scale, naming failures compound: the knowledge base becomes a place where you know things exist but cannot trust that you found them all.

1. Establish a Controlled Vocabulary A controlled vocabulary is a list of approved terms. For every concept, there is exactly one canonical name. All synonyms redirect to that canonical name. "Client" and "Customer" are the same entity — pick one, make it the canonical term, and document the decision. This is not a style preference; it is a retrieval integrity constraint.
2. Disambiguation for Ambiguous Terms When a term is genuinely ambiguous across contexts, use explicit disambiguation. "Onboarding (Client)" and "Onboarding (Employee)" are better than creating two "Onboarding" categories that silently diverge. The disambiguation parenthetical signals that the ambiguity was recognized and resolved, not ignored.
3. Aliases and Synonyms as First-Class Objects Every controlled vocabulary term should have a list of known aliases. When a user searches "API key rotation" and the canonical term is "Credential Management," the alias must surface the right results. Aliases are not a search hack — they are the mechanism that makes controlled vocabulary usable by people who do not know it exists.
4. Consistent Grammatical Form Pick a grammatical pattern for category names and hold it across the entire taxonomy. "Client Onboarding," "Incident Response," and "API Integration" are all noun phrases — consistent. Mixing in verbs ("Onboarding Clients," "Responding to Incidents") creates cognitive friction at the navigation layer. Users spend attention parsing the naming inconsistency instead of evaluating the category relevance.

# Controlled vocabulary entry structure
terms:
  - canonical: "Credential Management"
    aliases:
      - "API key rotation"
      - "password reset"
      - "secret rotation"
      - "token management"
    disambiguation: null
    notes: "Covers all credential lifecycle operations. Distinct from 'Access Management' (user permissions)."

  - canonical: "Client Onboarding"
    aliases:
      - "customer onboarding"
      - "new client setup"
      - "account provisioning"
    disambiguation: "(Client) — see also Employee Onboarding"
    notes: "Post-contract, pre-go-live activities for new clients. Not internal HR onboarding."

  - canonical: "Incident Response"
    aliases:
      - "IR"
      - "incident handling"
      - "outage response"
    disambiguation: null
    notes: "Production system failures and security events. Use 'Bug Triage' for non-production defects."