Latest / 5 Minute UX / Project Common Language and Glossary: What It Is and Why It Matters
Transcript
- 0:08This lesson is Project Common Language and Glossary: What It
- 0:11Is and Why It Matters. Let's get started.
- 0:20There’s a specific moment in UX projects where effort vanishes,
- 0:23and it usually starts with a single word. Imagine a designer
- 0:26calls a wireframe a 'mockup,' but the client expects a high-
- 0:28fidelity visual, leading to wasted effort and frustration.
- 0:31Without shared definitions, diverse stakeholders like
- 0:34designers, developers, and subject matter experts interpret
- 0:37terms differently, creating friction. This misalignment
- 0:39creates a 'black hole of ideas' where stakeholder time and
- 0:42effort feel lost to the void. We need to stop this leak before it
- 0:45drains the project’s momentum and trust.
- 0:53By the end of this section, you'll be able to define a
- 0:56project common language and glossary, identifying its three
- 0:58core components: terms, roles, and deliverables. You'll learn
- 1:01to describe how this shared vocabulary solves stakeholder
- 1:04confusion and builds essential trust in your work. A project
- 1:07glossary is a documented set of definitions for specific
- 1:09terminology used throughout a UX project, grounding your team in
- 1:12a single source of truth. It includes clear explanations of
- 1:15project terms, roles, and the relationships between different
- 1:18deliverables or concepts, ensuring everyone sees the same
- 1:20structure. This is not merely a dictionary of words, but a
- 1:23strategic alignment artifact that defines the marching orders
- 1:26and approach for the team. When you establish this common
- 1:29vocabulary for deliverables, stakeholders understand exactly
- 1:31what type of output to expect at various stages of the project.
- 1:34This clarity prevents the black hole of ideas where effort feels
- 1:37lost, because everyone agrees on what a wireframe or prototype
- 1:40actually represents. It builds trust that their time and effort
- 1:43isn’t going into a void, but toward a well-defined set of
- 1:46marching orders. That foundational definition sets the
- 1:48stage for how we distinguish this artifact from style guides
- 1:51or general objectives in the next section.
- 1:59Think back to a project where the word prototype meant a
- 2:01clickable file to you but a rough sketch to the client. You
- 2:03likely felt that friction in early meetings when the lack of
- 2:06clarity on marching orders created unnecessary confusion.
- 2:08This happens because diverse stakeholders, including clients
- 2:11and subject matter experts, bring different professional
- 2:13vocabularies to the table. Without a shared language, their
- 2:16time and effort feel like they are going into a black hole of
- 2:18ideas. You already know that aligning on project goals is
- 2:21critical for success, but you must also align on the language
- 2:23used to discuss those goals. The source material emphasizes that
- 2:26a common language defines how the team communicates about
- 2:28objectives, not just what those objectives are. This distinction
- 2:31matters because conceptual consistency prevents the same
- 2:33misunderstandings from derailing your progress repeatedly.
- 2:36Experienced practitioners note that taking time at the start of
- 2:38meetings to define terms builds immediate trust. When you
- 2:41clarify the semantics of the project, you ensure that
- 2:43discussions remain productive and focused on actual work. The
- 2:46signal of strong alignment is a team that shares a common
- 2:48vocabulary for deliverables from day one. That shared vocabulary
- 2:51prevents confusion among diverse stakeholders, which sets the
- 2:53stage for distinguishing this artifact from other documents.
- 3:02The first move is to distinguish your glossary from other common
- 3:05project artifacts. It is easy to assume that any document
- 3:07containing definitions serves the same purpose, but
- 3:09experienced practitioners know that the function of the
- 3:12artifact determines its value in the workflow. You need to
- 3:14understand exactly what this tool does not do before you can
- 3:17leverage what it does do. This clarity prevents you from using
- 3:20the wrong instrument for the job at hand. Consider how project
- 3:22objectives differ from a common language glossary. Project
- 3:25objectives define what the project aims to achieve in terms
- 3:28of outcomes and goals. The glossary, however, defines how
- 3:30the team communicates about those objectives and the
- 3:32deliverables. One sets the destination, while the other
- 3:35sets the vocabulary for the journey. This distinction
- 3:37ensures that everyone is speaking the same language while
- 3:39working toward the same target. A glossary is also not a simple
- 3:42list of tasks or a checklist of activities. Task lists focus on
- 3:45actions and deadlines, whereas a glossary focuses on semantics
- 3:48and relationships between terms. It maps out the conceptual
- 3:50landscape rather than the chronological timeline of the
- 3:53work. This means you are aligning on meaning, not just
- 3:55managing a schedule of events. Another frequent confusion
- 3:57involves the difference between a glossary and a style guide.
- 4:00Style guides govern visual and tonal consistency across design
- 4:03elements and brand voice. A project glossary governs
- 4:05conceptual and terminological consistency among stakeholders
- 4:08and team members. One ensures the product looks right, while
- 4:10the other ensures the process is understood correctly. Both are
- 4:13essential, but they serve entirely different masters in
- 4:15the project ecosystem. This strategic alignment artifact
- 4:18belongs in the initial alignment and planning phases. You should
- 4:21establish this shared vocabulary before deep work begins on the
- 4:23design or development. Introducing it early prevents
- 4:26the black hole of ideas where stakeholder effort feels lost.
- 4:28It builds trust by clarifying deliverables and demystifying
- 4:31the design process for everyone involved. By applying the
- 4:33distinction between a project glossary and a style guide or
- 4:36general objectives, you protect your team from misalignment. You
- 4:39are creating a well-defined set of marching orders that everyone
- 4:42can reference. This proactive measure solidifies the
- 4:44foundation of the project work before complexity sets in. The
- 4:46result is a smoother collaboration where time and
- 4:49effort are directed effectively. Now that you understand what the
- 4:51glossary is not, the next section walks through how to
- 4:54apply the glossary strategy in your own projects.
- 5:02In your next project, start by identifying key terms, roles,
- 5:05and deliverables that may be ambiguous to your specific
- 5:08stakeholders. Create a simple document or visual diagram
- 5:10defining these terms and illustrating their
- 5:12relationships. Share this glossary at the beginning of the
- 5:15project and revisit it in early meetings to ensure ongoing
- 5:18alignment and clarity. This practice builds trust by
- 5:20clarifying that stakeholder effort is directed toward clear,
- 5:23well-understood outputs. That brings the lesson full circle,
- 5:25back to the listener and the moment they'll first put the
- 5:28protocol into practice.
- 5:32Welcome to The Take. I'm joined by a fellow practitioner and
- 5:35together we're going to dig into Project Common Language and
- 5:38Glossary: What It Is and Why It Matters — what it means in
- 5:41practice and what's worth remembering.
- 5:44[HOST] That distinction between defining the destination versus
- 5:47defining the vocabulary really hit home for me. We often
- 5:50confuse setting goals with aligning on language. [LEARNER]
- 5:53Exactly. I’ve seen teams waste weeks arguing over a prototype
- 5:56because they never agreed on what that word actually meant in
- 5:59this context. [HOST] It creates that black hole of effort where
- 6:02everyone is working hard but pulling in different semantic
- 6:05directions. The glossary stops that leak before it starts.
- 6:07[LEARNER] But maintaining that single source of truth is harder
- 6:11than creating it. People naturally drift back to their
- 6:13departmental jargon once the kickoff meeting ends. [HOST]
- 6:16True, which is why we have to treat it as a living artifact
- 6:19rather than a static document. We need to revisit those
- 6:22definitions when new stakeholders join the project.
- 6:24[LEARNER] I wonder if AI could help enforce that consistency
- 6:27during daily standups or async updates. Imagine a tool that
- 6:30flags when someone uses a term differently than the glossary
- 6:33defines it. [HOST] That’s a compelling idea, though it risks
- 6:36feeling like semantic policing rather than collaboration. We
- 6:39want shared understanding, not just automated correction.
- 6:42[LEARNER] Fair point. The human element of trust is what
- 6:44actually locks that shared language in place. Technology
- 6:47can’t replicate the relief stakeholders feel when confusion
- 6:50vanishes. [HOST] Right. The glossary is just the map, but
- 6:53the trust is the terrain we’re actually navigating together.
- 6:56Keeping that distinction clear protects the project’s momentum.