Design Systems · Lesson 02 / 13
Design principles
What design principles are for, what makes a principle useful, how to write them with your team, real-world examples, and how to keep them alive in everyday decisions.
3 min read · 5 quiz questions
What principles are for
Design principles are a handful of short statements that describe how your product should feel and behave, and what your team values when making trade-offs.
No design system can cover every situation. Principles help people make good decisions when there's no component, pattern or rule for the problem in front of them. They also help settle disagreements: instead of "I like it" vs "I don't", the team asks "Which option better follows our principles?"
What makes a principle useful
| Quality | Weak | Strong |
|---|---|---|
| Specific | Make it simple | Show the next step, hide the rest |
| Implies a trade-off | Be fast and beautiful | Speed over decoration |
| Actionable | Delight users | Celebrate completion, not routine actions |
| Memorable | A paragraph of corporate language | Three to six words, easy to quote |
| Yours | Generic values any company could claim | Reflects your users, product and brand |
A good test: could a reasonable team choose the opposite principle? "Make it usable" fails (nobody wants unusable). "Guidance over flexibility" passes — some products rightly choose flexibility.
Writing principles with your team
- 1Gather inputs: research insights, brand values, product strategy, and the recurring debates your team has.
- 2Run a workshop with design, engineering, product and content. Ask: "What do we want people to feel? What do we always argue about? What would we never do?"
- 3Cluster and draft: group ideas into themes and write a short headline for each.
- 4Add an explanation (one or two sentences) and an example of the principle in the product.
- 5Test them against real past decisions. Would they have helped? If not, rewrite.
- 6Limit to 3–5. If everything is a principle, nothing is.
Examples from public design systems
Many companies publish their principles. A few paraphrased examples show the range of styles:
- GOV.UK — "Start with user needs", "Do less", "Design with data", "Do the hard work to make it simple", "This is for everyone".
- Shopify Polaris has emphasised merchants' needs and making commerce better for everyone.
- Material Design describes material as a metaphor, bold and intentional graphics, and motion that provides meaning.
Notice how GOV.UK's principles imply trade-offs: "Do less" means saying no to features; "This is for everyone" means accessibility is not optional.
A full example
1. Clarity over cleverness
Plain labels beat witty ones. If a user hesitates, we failed.
Example: "Send invoice", not "Fire it off 🚀".
2. One primary action per screen
Every screen has one obvious next step. Everything else is
secondary or tucked behind "More".
3. Accessible by default
Every component meets WCAG 2.2 AA before it ships.
We never trade accessibility for aesthetics.
4. Guide, don't block
Prevent errors with good defaults and helpful hints rather
than disabled buttons and error walls.
5. Consistent before custom
Use an existing component unless there's evidence it fails users.Keeping principles alive
- Put them at the top of the design system documentation.
- Reference them in design reviews: "Which principle does this support?"
- Use them in component docs to explain decisions ("Why buttons are never disabled: Guide, don't block").
- Include them in onboarding for new designers and developers.
- Review them yearly — products and teams change.
Do
- Keep them short, specific and few.
- Write them with the whole team.
- Show an example of each in the product.
- Use them to make and explain decisions.
Don't
- Copy another company's principles.
- Write vague values like "simple", "beautiful", "user-friendly".
- Create ten or more.
- Write them once and never mention them again.
Key takeaways
- Principles guide decisions where no component or rule applies, and help settle disagreements.
- Useful principles are specific, imply trade-offs, are actionable and memorable.
- Write them collaboratively from research, brand and recurring debates; keep 3–5.
- Add an explanation and a product example to each.
- Keep them alive by using them in reviews, docs and onboarding.
Exercise
Draft principles for a product
- Pick a product you know well.
- List five decisions it clearly made (e.g. very few settings, lots of animation).
- Write the principle behind each decision in under six words.
- Check each one: could a reasonable team choose the opposite? Rewrite weak ones.
- Keep the best three and add an example for each.
Test yourself
Design principles quiz
5 questions. Score 70% or more to complete the lesson.
