Creating a shared terminology glossary for UCD projects
Design projects accumulate vocabularies quickly: research language, product terminology, accessibility language and meeting shorthand. A shared terminology glossary gives these strands a common reference point, helping a user-centred design team in Brisbane interpret findings as a Melbourne product team does.
It is more than a word list. Each entry can record preferred labels, plain-English definitions, examples and relationships between concepts, such as the difference between a persona and a user role. That distinction prevents a reasonable observation from becoming an ambiguous requirement in a backlog.
It also makes collaboration easier to trace. Designers can label decisions consistently, new colleagues can understand why a finding matters, and stakeholders can connect terminology to evidence. For Australian teams working across offices and time zones, a maintained lexicon reduces repeated clarification and supports dependable handovers.
The practical task is deciding what to document, who approves changes and when terms should be retired. UCDmanager supports the surrounding work through personas, use cases, heuristic evaluations, usability testing and accessibility conformance evaluation. A glossary is most useful when it stays connected to those activities.
Why a common vocabulary matters
A shared glossary addresses a common failure: two people use different labels for the same concept and continue without noticing. If “user,” “customer” and “participant” have inconsistent definitions, a recruitment note may look complete while missing the intended audience. Recorded distinctions let teams compare interviews, test scripts and requirements without erasing meaningful differences.
Entries can also connect a term to evidence, ownership and related artifacts. An accessibility barrier should not be filed as a general usability problem merely because both appear on one issue list. Shared vocabulary preserves that distinction and routes each issue toward the appropriate response.
Keep governance light. Appoint a steward and reviewers from research, design, engineering and content, then agree on how changes are approved. An initial workshop can be arranged through the UCDmanager contact page, using a live project example rather than a theoretical list of definitions.
Defining terms without losing meaning
Begin with the words already circulating: research plans, interview guides, heuristic evaluation spreadsheets, interface labels and delivery tickets. For each important term, record a preferred label, a concise definition, acceptable synonyms, discouraged terms, an example, a source and an owner. Keep Australian English spelling consistent throughout.
Check definitions against the artifacts they describe. UCDmanager’s collaborative personas provide a useful test: does “primary user” identify the same role in a research note, a journey map and a use case? Resolve any mismatch before it spreads into test scripts, design requirements and navigation labels.
Keep neighbouring concepts distinct. A persona is a research-based representation of a user group; a user role describes goals and behaviour; a stakeholder may shape the service without using it. Record these boundaries in plain language, attach examples and mark contested meanings for review. Definitions should clarify use, not merely state what a term is not.
Grounding the lexicon in Australian research
Australian projects make the need for precise language visible. Sydney and Melbourne teams may work with participants from many language backgrounds, while services also serve regional, remote and First Nations communities. A glossary should identify the intended community without reducing cultural identity to a vague persona attribute. Definitions can point to relevant research and name the advisers involved in sensitive topics.
Market-facing terms vary too. A “member” in a Brisbane loyalty programme may not mean the same as a “subscriber” on a Perth e-commerce platform, and an Australian Government service may call a service user a “customer.” Review these labels with local content and service teams. Established market language can be checked against AMTA 2020 resources rather than invented from internal habits.
Record Australian conventions where they affect meaning: spellings, inclusive language, date order and currency symbols. A protocol may specify DD/MM/YYYY, Australian English labels and AEST/AEDT for remote sessions. For public-sector work, connect “accessible” and “conforming” to the applicable Australian Government Digital Service Standard and WCAG requirements, including the chosen conformance level.
Turning definitions into team decisions
A definition should explain how a term changes a decision. In a heuristic evaluation, the lexicon can distinguish an observation, an interpretation and a severity rating. In usability testing, it can state whether a completion rate describes a task, a participant or a whole session. This precision prevents teams from averaging incompatible measures or comparing findings that use different units.
When reviewers assess an interface together, collaborative review features show the value of shared labels: comments can refer to the same finding, and disagreements can be resolved against agreed criteria. A glossary therefore needs decision rules as well as descriptions of artifacts and concepts.
Use the lexicon in everyday work: agendas, test scripts, design critiques, acceptance criteria and handovers. Capture corrections during those moments, then confirm them at the next review. Terms with no effect on research methods, design responses or compliance checks can usually remain informal rather than occupying a formal entry.
Maintaining trust and document control
Assign each entry an owner and status, such as proposed, approved or deprecated, and retain a short change history. Review the lexicon after significant research phases and before major releases. The review can sample requirements, use cases and test reports to find words that have drifted, duplicate entries that need merging and definitions that no longer match current evidence.
Controlled distribution matters when a glossary leaves the project team. Some PDF exports include an owner password, and teams should understand whether removing one is permitted before sharing the file; PDF password guidance outlines the legal considerations. Keep restricted research evidence in the controlled workspace and circulate only approved glossary extracts.
Retire terms deliberately, recording their replacement and the date the change took effect. Keep the old term visible in archived notes where that prevents confusion, with a clear reference to the current definition. The result is a compact, evidence-linked vocabulary that keeps Australian UCD teams aligned without trying to prescribe every conversation.