
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 responsibilities, ensuring the team understands exactly how you are defining your role regarding the specific responsibilities you are taking on. Use the term most familiar to the organization, but be explicit about what that role covers in practice. This prevents the overlap where an information architect’s duties blur with those of a content strategist, which would otherwise leave gaps in the work.
With the hierarchy, concepts, and roles defined, you now have the specific terms needed to execute the four-step protocol for maintaining this shared vocabulary.
Key Points:
Information Hierarchy: Establish distinctions between levels such as Category, Subcategory, Topic, and Article
Conceptual Distinctions: Clarify the difference between 'needs' and 'ideas' to prevent misinterpretation of stakeholder statements
Role Responsibility Alignment: Ensure the team understands how you are defining the role regarding specific responsibilities you are taking on
Organizational Familiarity: Use the term most familiar to the organization while ensuring internal clarity on definitions
Four-Step Execution Protocol
You’ve identified the six categories of ambiguous terms. Now you lock them down. The protocol starts with initial agreement: your team must define the common list of terms and definitions before any requirements gathering begins. You don’t move forward until that list is settled.
Next, you build a meeting routine. At the beginning of every session, you state which term is being used and exactly what it means. This prevents the drift where "user" quietly becomes "client" by the third discussion.
Then you create visual aids. A simple diagram mapping the relationships between your defined roles and deliverables keeps the abstract concrete. It shows how a functional specification differs from a wireframe, or how a content producer interacts with an editor.
Finally, you drive stakeholder alignment. You use this shared vocabulary to explain the process and the specific output they can expect. This clarity proves their effort isn’t going into a black hole of ideas. It’s the bridge that turns your defined roles into a trusted, predictable workflow for the entire project.
Key Points:
Initial Agreement: The team gathering requirements must agree on a common list of terms and definitions before proceeding
Meeting Routine: At the beginning of each meeting, state which term is being used and what it means
Visual Aid Creation: Create visual elements (diagrams) that explain relationships between different terms or roles
Stakeholder Alignment: Use the common vocabulary for deliverables to help stakeholders understand the process and expected output
Applying Vocabulary in Stakeholder Meetings
You’ve built the vocabulary. Now you apply it in the room.
The timing is specific: you implement this shared vocabulary at the beginning of the project, and then again at the start of every requirements-gathering meeting. It’s not a one-time setup. It’s a recurring habit that keeps the conversation anchored.
Here’s the real test for you. Think about your last stakeholder meeting. Did you use a defined term to show them their time and effort weren’t going into a black hole of ideas? If not, what’s the one deliverable—like a functional specification or a site map—that you’d define first to bring them that process clarity?
If different people hold roles with blurred responsibilities, like an information architect and a content strategist, you need to discuss collaboration methods at the project’s start. Don’t wait for the conflict to surface. Define the handoff now.
So, pick one ambiguous term from your current project. Draft a one-sentence definition that distinguishes it from a similar concept. Then, plan exactly how you’ll introduce that definition at the start of your next stakeholder meeting. That’s how the vocabulary becomes a working tool, not just a document.
Key Points:
Timing: Implement the shared vocabulary at the beginning of the project and at the start of every requirements-gathering meeting
Trust Building: Use defined terms to show stakeholders their time and effort are not going into a 'black hole of ideas'
Process Clarity: Ensure stakeholders understand the type of output they can expect based on the defined deliverables
Collaboration Method: Discuss collaboration methods at the project's start if different people hold roles with blurred responsibilities
Reflecting on Vocabulary Gaps
So, look at your current project and find one ambiguous term that has caused confusion. Maybe it’s the difference between a customer and a client, or a topic versus an article. Draft a one-sentence definition for that term that clearly distinguishes it from similar concepts. This isn't just about word choice; it's about defining specific responsibilities, like the overlap between an information architect and a content strategist.
Plan how you will introduce this definition at the start of your next stakeholder meeting. You state which term is being used and what it means before you proceed. This routine ensures everyone is aligned on the deliverables, whether that’s a functional specification or wireframes. It builds trust that their time isn’t going into a black hole of ideas.
Consider creating a simple diagram to show the relationship between this term and related roles or deliverables. A visual aid makes the connections clear and prevents misinterpretation of stakeholder statements. This is the moment you apply the shared vocabulary to real work. You are no longer just defining terms; you are using them to guide the project.
Key Points:
Identify one ambiguous term in your current project that has caused confusion
Draft a one-sentence definition for that term that distinguishes it from similar concepts
Plan how you will introduce this definition at the start of your next stakeholder meeting
Consider creating a simple diagram to show the relationship between this term and related roles or deliverables
Weitere Episoden von „5 Minute UX“



Verpasse keine Episode von “5 Minute UX” und abonniere ihn in der kostenlosen GetPodcast App.








