A Shared Reference Language
How to create a small, practical vocabulary for tagging and discussing design references across a team
A shared reference language helps a design team describe examples consistently enough to search, compare, and review them. Build a small vocabulary around structure, component, visual treatment, content, behavior, and decision status. Define each important term with positive and negative examples, use the vocabulary in real project reviews, and change labels when they stop improving retrieval or discussion.
A team reference library breaks down when the same words mean different things. One designer tags a page “minimal,” another means generous spacing, and a stakeholder uses the word for almost any interface with a white background. The solution is not a perfect taxonomy. It is a small working vocabulary grounded in examples.
Start with questions the team asks
Review recent briefs and critiques. List the questions that repeatedly trigger reference searches: page structure, component type, content density, navigation behavior, brand tone, motion, or approval status. Build labels around those retrieval needs.
A useful starter vocabulary covers six dimensions:
- structure: landing page, dashboard, article, pricing, onboarding;
- component: hero, navigation, table, card, form, footer;
- treatment: editorial, restrained, expressive, high-contrast;
- content: product proof, comparison, testimonial, explanation;
- behavior: sticky, expandable, filtered, responsive;
- status: research, shortlisted, approved, rejected.
Do not require every reference to use every dimension. Add only the labels that improve the next search or review.
Define terms with examples
A written definition helps, but a positive example and a near-miss make the boundary clearer. If the team uses “editorial,” show a layout that qualifies and one that looks expressive but lacks editorial hierarchy. Record the visible evidence behind the label.
Keep subjective language for discussion, not retrieval. “Feels premium” may be a useful reaction; tags such as restrained palette, serif display type, dense product photography, and generous spacing are easier to inspect.
Separate description from judgment
Tags should describe the reference. Notes should record why the team values or rejects it. Mixing both creates labels such as good hero or bad mobile, which are impossible to reuse consistently.
During review, say: “This is a product-led hero with strong proof, but the copy is too short for our case.” The first part helps classification; the second preserves the project decision.
Test the vocabulary in real work
Ask two people to tag the same ten references independently. Compare where they disagree and search the library using the resulting labels. Merge synonyms, split terms that hide important differences, and remove labels no one uses.
The goal is not perfect agreement. The goal is predictable retrieval and clearer critique. Connect the vocabulary to a reference library the team will use, then review it after several projects instead of designing the entire taxonomy in advance.
A shared language is successful when a teammate can request three examples of a dense mobile pricing comparison and receive roughly the material they expected.