Naming things is hard: Why words become technical debt

Every mislabeled content type, poorly named component or ambiguous field increases training time, confuses editors and adds to technical debt. Naming isn't a cosmetic decision: it's how people understand, use and sustain your system. This session examines the lifecycle of naming decisions within design systems and their systemic consequences. You will explore how to:

• Create a shared language across stakeholders: understand how unclear or inconsistent labels increase support burden, create confusion for editors and accumulate technical debt.
• Analyze names as contracts: see how designers, developers, editors, product owners and maintainers interpret names differently, and why misalignment breaks systems.
• Evaluate naming strategies across design systems: compare presentational, functional, user-perspective and metaphorical approaches, with a close look at the Yale Design System alongside other public examples, to assess when each strategy succeeds or fails.
• Plan for governance and change: understand the risks of renaming at scale, and learn how decision logs, shared vocabularies and editor training help ensure continuity and reduce disruption over time.

This session is for site owners and technical decision makers of any level. You will leave with both a vocabulary of naming patterns and a decision-making model applicable to any organization maintaining a large-scale platform or design system.