Design and product terminology

Design vocabulary shapes team communication and project efficiency. When a designer says "hero section," the entire team should understand it refers to the prominent area below the navigation. Distinguishing between terms like "wireframes" and "mockups" prevents delivery misalignments.

Component terminology requires special attention in design systems. A "card" component might include variants like "product card," "blog card," or "user card," each with specific usage guidelines. Teams should also align on naming patterns — for example, using "button-primary" versus "primary-button" consistently across design and code. Make sure your documentation includes visual examples alongside terms. For example, when defining "modal," include screenshots of the component to reinforce understanding.

Similarly, establish a shared understanding of project management terms. For example, when a product manager mentions "MVP" (Minimum Viable Product), the entire team should understand it refers to the smallest set of features needed to validate a product hypothesis.