Discovering Possible Labels for Categories

Good labels rarely come from a single source. Analyzing existing content, page titles, subheadings, summaries, surfaces the vocabulary already in use. Competitive analysis reveals the conventions an entire domain has already converged on. User research, particularly open card sorting, captures the actual language real users apply when they group and name content themselves. Domain-specific controlled vocabularies or thesauri, where they already exist, bring a level of consistency that's hard to match from scratch. Subject-matter experts, technical support staff, and content authors all carry vocabulary a design team wouldn't otherwise have access to. And search-log analytics, the terms people actually type when looking for something, are some of the most honest evidence available, since nobody phrases a search query to be polite or on-brand.

No single source is sufficient on its own. Combining several, and cross-checking the terms they surface against each other, is what actually produces a labeling system grounded in reality rather than internal assumption.

The team that already works inside an organization is often the worst-positioned group to guess what outsiders will call something, which is exactly why label discovery has to reach beyond the room the decision is being made in.

Exercise

The scenario: A team is designing the navigation for a new peer support platform for people experiencing mental health challenges. The domain is sensitive, and the vocabulary is genuinely contested, clinical terms, community-preferred terms, and outdated or stigmatizing terms all coexist for the same concepts. The target audience is diverse in age, background, and familiarity with mental health language. The team has eight weeks before navigation labels need to be finalized.

Given the sensitivity of this domain and the contested vocabulary, which combination of methods would you prioritize in the eight weeks available?
Try It With Your Data: Survey Analysis Suite

Fill in your own details below; the prompt updates as you type. When it's ready, copy it into Claude or whatever AI tool you use.

What this prompt does

Synthesizes survey responses into IA-relevant themes with counts, quotes, and recommended actions.

  • After conducting user surveys about documentation experience
  • To quantify qualitative findings from interviews
  • To validate label choices with user preference data
  • To identify findability problems at scale
The exact question text you asked
Number of respondents
One per line, e.g. "'Settings', 42% (105 responses)"
Brief description
The term you use today
Terms competitors use, if known
Assembled prompt