Latest / 5 Minute UX / How to Define a Shared Vocabulary
Transcript
- 0:08This lesson is How to Define a Shared Vocabulary. Let's get
- 0:11started.
- 0:19Start by identifying the three role categories that cause the
- 0:22most friction in early design phases. First, user roles, where
- 0:25you determine whether the people using the system are called
- 0:28users, customers, or clients. Second, professional roles,
- 0:31which means clarifying if your team prefers interaction
- 0:34designer or information architect, especially since
- 0:36those responsibilities often blur with content strategists.
- 0:39Third, interacting roles, such as a job seeker versus a client,
- 0:42or a content producer versus an editor. Once you have those
- 0:45labels locked in, you can move to the outputs. Define your
- 0:48primary deliverables, like functional specifications,
- 0:51wireframes, and site maps, so everyone knows exactly how they
- 0:54differ. This prevents stakeholders from asking for a
- 0:56site map when they actually need a wireframe. You are
- 0:59identifying the six specific categories of terminology
- 1:01requiring explicit definition in UX projects, and that clarity
- 1:04sets the stage for your next move: clarifying information
- 1:07hierarchy and concepts.
- 1:16Once you’ve settled on the people involved, the next layer
- 1:19is how information itself gets organized. You need to establish
- 1:22clear distinctions between structural levels, specifically
- 1:24the difference between a Category, a Subcategory, a
- 1:27Topic, and an Article. Without these definitions, a stakeholder
- 1:29asking for a new page might mean a top-level section or a single
- 1:32content piece, and the team will build the wrong thing. This
- 1:35same clarity applies to abstract concepts, where the most common
- 1:38trap is the confusion between needs and ideas. A stakeholder
- 1:41will often state a solution they want, but if you treat that as a
- 1:43requirement, you miss the actual problem. Clarifying that a need
- 1:46is a user’s underlying goal, while an idea is a proposed
- 1:49feature, prevents you from misinterpreting their feedback
- 1:51during requirements-gathering sessions. You also have to
- 1:54align on role responsibilities, ensuring the team understands
- 1:57exactly how you are defining your role regarding the specific
- 1:59responsibilities you are taking on. Use the term most familiar
- 2:02to the organization, but be explicit about what that role
- 2:05covers in practice. This prevents the overlap where an
- 2:07information architect’s duties blur with those of a content
- 2:10strategist, which would otherwise leave gaps in the
- 2:12work. With the hierarchy, concepts, and roles defined, you
- 2:15now have the specific terms needed to execute the four-step
- 2:17protocol for maintaining this shared vocabulary.
- 2:26You’ve identified the six categories of ambiguous terms.
- 2:28Now you lock them down. The protocol starts with initial
- 2:31agreement: your team must define the common list of terms and
- 2:33definitions before any requirements gathering begins.
- 2:36You don’t move forward until that list is settled. Next, you
- 2:39build a meeting routine. At the beginning of every session, you
- 2:41state which term is being used and exactly what it means. This
- 2:44prevents the drift where "user" quietly becomes "client" by the
- 2:47third discussion. Then you create visual aids. A simple
- 2:49diagram mapping the relationships between your
- 2:51defined roles and deliverables keeps the abstract concrete. It
- 2:54shows how a functional specification differs from a
- 2:57wireframe, or how a content producer interacts with an
- 2:59editor. Finally, you drive stakeholder alignment. You use
- 3:02this shared vocabulary to explain the process and the
- 3:04specific output they can expect. This clarity proves their effort
- 3:07isn’t going into a black hole of ideas. It’s the bridge that
- 3:10turns your defined roles into a trusted, predictable workflow
- 3:12for the entire project.
- 3:20You’ve built the vocabulary. Now you apply it in the room. The
- 3:23timing is specific: you implement this shared vocabulary
- 3:26at the beginning of the project, and then again at the start of
- 3:28every requirements-gathering meeting. It’s not a one-time
- 3:31setup. It’s a recurring habit that keeps the conversation
- 3:34anchored. Here’s the real test for you. Think about your last
- 3:36stakeholder meeting. Did you use a defined term to show them
- 3:39their time and effort weren’t going into a black hole of
- 3:42ideas? If not, what’s the one deliverable—like a functional
- 3:44specification or a site map—that you’d define first to bring them
- 3:47that process clarity? If different people hold roles with
- 3:50blurred responsibilities, like an information architect and a
- 3:53content strategist, you need to discuss collaboration methods at
- 3:55the project’s start. Don’t wait for the conflict to surface.
- 3:58Define the handoff now. So, pick one ambiguous term from
- 4:01your current project. Draft a one-sentence definition that
- 4:03distinguishes it from a similar concept. Then, plan exactly how
- 4:06you’ll introduce that definition at the start of your next
- 4:09stakeholder meeting. That’s how the vocabulary becomes a working
- 4:12tool, not just a document.
- 4:19So, look at your current project and find one ambiguous term that
- 4:22has caused confusion. Maybe it’s the difference between a
- 4:25customer and a client, or a topic versus an article. Draft a
- 4:28one-sentence definition for that term that clearly distinguishes
- 4:31it from similar concepts. This isn't just about word choice;
- 4:34it's about defining specific responsibilities, like the
- 4:37overlap between an information architect and a content
- 4:39strategist. Plan how you will introduce this definition at the
- 4:42start of your next stakeholder meeting. You state which term is
- 4:45being used and what it means before you proceed. This routine
- 4:48ensures everyone is aligned on the deliverables, whether that’s
- 4:51a functional specification or wireframes. It builds trust that
- 4:54their time isn’t going into a black hole of ideas. Consider
- 4:57creating a simple diagram to show the relationship between
- 5:00this term and related roles or deliverables. A visual aid makes
- 5:03the connections clear and prevents misinterpretation of
- 5:05stakeholder statements. This is the moment you apply the shared
- 5:08vocabulary to real work. You are no longer just defining terms;
- 5:11you are using them to guide the project.
- 5:16Welcome to The Take. I'm joined by a fellow practitioner and
- 5:19together we're going to dig into How to Define a Shared
- 5:22Vocabulary — what it means in practice and what's worth
- 5:25remembering.
- 5:27[HOST] The lesson emphasized stating definitions at the start
- 5:30of every meeting, but I find that often feels like a lecture
- 5:33to stakeholders. [LEARNER] It can, if you just read from a
- 5:36document. I’ve had better luck treating it as a quick alignment
- 5:40check instead. [HOST] How do you frame that check so it doesn’t
- 5:43feel like you’re policing their language? [LEARNER] I ask them
- 5:46to confirm the term, not define it. I say, “When we say
- 5:49wireframe, we mean low-fidelity structure, right?” [HOST] That
- 5:52shifts the burden from you explaining to them confirming.
- 5:55It makes them active participants in the agreement.
- 5:58[LEARNER] Exactly. And it exposes the gap immediately if
- 6:01they were thinking of a mockup. [HOST] I struggled with the
- 6:04needs versus ideas distinction. It’s easy to say, but hard to
- 6:07enforce when a stakeholder is excited about a feature.
- 6:10[LEARNER] That’s the tricky part. You have to validate the
- 6:13idea before reframing it as a need. [HOST] How do you do that
- 6:16without sounding dismissive? [LEARNER] I acknowledge the
- 6:19value of the idea, then ask what problem it solves. “That sounds
- 6:23great. What's the user trying to achieve?” [HOST] So you’re using
- 6:26the idea as a bridge to the underlying goal. [LEARNER] Yes.
- 6:29It keeps the momentum going while redirecting the focus.
- 6:32[HOST] I’ve been thinking about how AI changes this. Can a tool
- 6:35help draft these shared vocabulary documents? [LEARNER]
- 6:38It can generate a list, but it can’t understand the
- 6:41organizational context. [HOST] That’s the key. The ambiguity
- 6:44isn’t in the words, it’s in the specific roles and relationships
- 6:47within that company. [LEARNER] True. AI might suggest
- 6:50“customer” and “client” are synonyms, but in your firm,
- 6:53they've different billing structures. [HOST] So the human
- 6:56judgment is still the bottleneck. The tool just speeds
- 6:59up the formatting. [LEARNER] Right. And it can help visualize
- 7:02the relationships, but you have to decide which ones matter.
- 7:05[HOST] I like that. The diagram is a map, but you’re the one
- 7:08deciding the territory. [LEARNER] And if you get the
- 7:11territory wrong, the map is useless. [HOST] So the lesson’s
- 7:14real value isn’t the list of terms. It’s the discipline of
- 7:17defining them before the work starts. [LEARNER] Agreed. It’s a
- 7:20defensive move that saves time later. [HOST] And it builds
- 7:23trust. Stakeholders respect clarity more than speed.
- 7:26[LEARNER] Definitely. They’d rather be told what they’re
- 7:29getting than guess. [HOST] So the shared vocabulary isn’t just
- 7:32a document. It’s a contract of understanding. [LEARNER] And a
- 7:36contract is only as good as the enforcement. [HOST] Which brings
- 7:39us back to the meeting routine. [LEARNER] Exactly. The
- 7:42definition is only alive when it’s spoken.