Aller au contenu
Global sound
5 Minute UX

5 Minute UX

How to Define a Shared Vocabulary

· 12 min · Saison 1 Épisode 437

Notes d’épisode

Establish a common list of terms and definitions for roles and deliverables to prevent stakeholder confusion. Apply this shared vocabulary during requirements-gathering meetings to align expectations and build trust in the design process.

Learning Objective: By the end of this lesson, learners will be able to construct a shared vocabulary document that clarifies role definitions, deliverable distinctions, and conceptual differences for a specific project.

Transcript

Six Categories of Ambiguous Terminology

Start by identifying the three role categories that cause the most friction in early design phases. First, user roles, where you determine whether the people using the system are called users, customers, or clients. Second, professional roles, which means clarifying if your team prefers interaction designer or information architect, especially since those responsibilities often blur with content strategists. Third, interacting roles, such as a job seeker versus a client, or a content producer versus an editor.

Once you have those labels locked in, you can move to the outputs. Define your primary deliverables, like functional specifications, wireframes, and site maps, so everyone knows exactly how they differ. This prevents stakeholders from asking for a site map when they actually need a wireframe.

You are identifying the six specific categories of terminology requiring explicit definition in UX projects, and that clarity sets the stage for your next move: clarifying information hierarchy and concepts.

Key Points:

• User Roles: Determine whether system participants are called 'users,' 'customers,' or 'clients'

• Professional Roles: Clarify if the team prefers 'interaction designer' or 'information architect,' noting potential overlap with content strategists

• Interacting Roles: Define roles that interact within the system, such as job seeker vs. client or content producer vs. editor

• Deliverables: Define primary outputs like functional specifications, wireframes, and site maps, providing brief descriptions of how they differ

Clarifying Information Hierarchy and Concepts

Once you’ve settled on the people involved, the next layer is how information itself gets organized. You need to establish clear distinctions between structural levels, specifically the difference between a Category, a Subcategory, a Topic, and an Article. Without these definitions, a stakeholder asking for a new page might mean a top-level section or a single content piece, and the team will build the wrong thing.

This same clarity applies to abstract concepts, where the most common trap is the confusion between needs and ideas. A stakeholder will often state a solution they want, but if you treat that as a requirement, you miss the actual problem. Clarifying that a need is a user’s underlying goal, while an idea is a proposed feature, prevents you from misinterpreting their feedback during requirements-gathering sessions.

You also have to align on role…

Site web: castopod.gogomito.com

En direct, dernière heure : 16 305 titres sur 7 673 stations dans 142 pays

Découvrez le monde par la radio

Plus de façons de découvrir (9)

Vous avez entendu quelque chose de bien ? Enregistrez-le, ou ouvrez-le directement dans Spotify.

★ Artist of the week The fastest riser on the radio this week
Your song here? From € 9 per week →
Rádioweb Cult 22Continuer l’écoute