
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 mappi
Podzilla Summary coming soon
Sign up to get notified when the full AI-powered summary is ready.
Free forever for up to 3 podcasts. No credit card required.

Managing Client Expectations with Metaphors

Manage Expectations for Sketches and Storyboards

Evaluating Project Viability Through Prototyping Costs

Classify Site Types to Set Design Goals
Free AI-powered recaps of 5 Minute UX and your other favorite podcasts, delivered to your inbox.
Free forever for up to 3 podcasts. No credit card required.