Testing Labels With Users

Labels should be tested with real, representative users, not just during initial design, but again after launch, since a labeling system that made sense on paper can still fail once real people encounter it in context. One simple technique is asking participants to describe what they expect to find at a link's destination before they click it, then comparing that expectation to what's actually there.

Two methods covered earlier in this course are particularly effective for label testing specifically. Card sorts, open, modified-Delphi, or closed, reveal how people understand structure, categories, and the words that should describe them. Free-listing surfaces a domain's vocabulary and boundaries directly from participants, without the researcher's own assumptions shaping what gets tested in the first place.

A label that made perfect sense in a design review can still fail its first real test, the only way to know for certain is asking the people who were never in that room.

Exercise

The scenario: A government digital service needs to test labeling decisions at three different stages of the project.

Stage 1, early Discovery: the team wants to understand what terms citizens actually use for a complex bureaucratic process, before any labels have been proposed.
Stage 2, mid-Design: the team has a proposed set of primary navigation labels and wants to know whether citizens would group content correctly under them.
Stage 3, post-launch: the team wants to know whether the live navigation labels are causing users to rely on search rather than browsing.

1. Which method is most appropriate for Stage 1, understanding citizens' vocabulary before any labels exist?
2. Which method is most appropriate for Stage 2, testing whether citizens would group content correctly under proposed labels?
3. Which method is most appropriate for Stage 3, understanding a live site's navigation-versus-search behavior?