Shared Language
Building a Pattern Language
A shared vocabulary for the whole team — components, behaviors, and concepts
Key Insight
A pattern language is the complete vocabulary a team uses to discuss design — not just component names, but terms for interactions, states, behaviors, and concepts. When everyone on the team speaks the same language, design critiques are faster, handoffs have less friction, and new members ramp up quickly. Building it is collaborative: everyone contributes, no one imposes.
Key Points
- •Pattern language includes names for components, behaviors, states, and concepts
- •Shared vocabulary accelerates critiques, reviews, and retrospectives
- •It is built collaboratively — unilateral naming creates the problem it tries to solve
- •Language evolves as the product and team evolve — maintain it actively
- •A living glossary is the artifact: searchable, owned jointly, reviewed annually
Guidelines
- ✓Start a living glossary early — even a shared doc is enough to begin
- ✓Define terms when ambiguity causes confusion, not as a preemptive exercise
- ✓Include examples alongside definitions — abstract definitions drift
- ✓Prune annually: remove terms for deprecated patterns
- ✓Make the glossary part of new team member onboarding
Want to learn this interactively?
Experience hands-on experiments and test your understanding.
🔥
Practice this topic
Active recall — strengthens long-term retention