UX Foundations · Step 5 · 6 min read
Patterns and when to break them
Most interface problems have been solved before. What a design pattern is, where to find good ones (Material Design, Apple's Human Interface Guidelines, GOV.UK), why Jakob's Law makes familiar patterns so strong, and how to decide, with evidence, when breaking one is worth it.
You don't have to invent a date picker. Thousands of teams have already designed log-ins, search boxes, checkouts and settings screens, and people have learned how they work. Reusing those solutions isn't lazy; it's respectful of people's time. The skill is knowing the patterns well enough to use them by default, and recognising the rare moment when one doesn't fit.
What you'll be able to do after reading:
- Explain what a design pattern is, with examples
- Find patterns in the main public pattern libraries
- Use Jakob's Law to argue for familiar solutions
- Decide, and justify, when to break a pattern
1. What a pattern is
A design pattern is a proven solution to a problem that keeps coming back. The idea comes from architecture: Christopher Alexander and his colleagues described more than 250 patterns for towns and buildings, each with a problem and a solution, in A Pattern Language (Oxford University Press, 1977). Interface designers borrowed the idea; Jenifer Tidwell's Designing Interfaces (O'Reilly, 3rd edition 2020, with Charles Brewer and Aynne Valencia) is a well-known catalogue.
| Recurring problem | Common pattern |
|---|---|
| People need to find one item among many | Search box with suggestions |
| People need to move between 3 to 5 main areas of a phone app | Bottom tab bar |
| People must confirm a destructive action | Dialog with a clear "Delete" and "Cancel" |
| People fill in a long application | One question per page, with a check-your-answers page |
| People want to see where they are in a process | Step indicator ("Step 2 of 4") |
A pattern is not a component. The pattern is the idea ("tabs for switching between views"); a component is one team's built version of it, in code and in Figma. See What a design system is.
2. Why familiar wins: Jakob's Law
Jakob's Law, in Nielsen's words: "Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know" (NN/g, Nielsen, Jakob's Law of Internet User Experience, video, 2017).
NN/g's article on heuristic 4 explains two kinds of consistency (NN/g, Krause, Maintain Consistency and Adhere to Standards, 2021):
- Internal consistency: the same patterns everywhere in your product.
- External consistency: following "established conventions in an industry or on the web at large".
When you follow a pattern, people bring their knowledge with them. When you break it, they have to learn your product first, and many won't.
3. Where to find patterns
Three public libraries are worth knowing well:
| Library | From | Best for |
|---|---|---|
| Material Design 3 | Google; described as "Google's open-source design system" (first version 2014) | Android and web apps |
| Human Interface Guidelines | Apple; "guidance and best practices that can help you design a great experience for any Apple platform" | Apps for Apple devices |
| GOV.UK Design System | UK Government Digital Service | Forms and services for the public |
NN/g also keeps a study guide that links its research on individual patterns, from toggle switches to tabs (NN/g, Tankala and Kendrick, Design-Pattern Guidelines: Study Guide, 2024).
When you design for one platform, follow that platform's guidelines. An iPhone user expects iPhone patterns, even in an app that also exists on Android.
4. When breaking a pattern is justified
- 1Find the pattern
How do other products solve this?
Libraries, common apps - 2Use it
The default choice. People already know it.
Adapt the details - 3Name the reason
Does it fail your users or your task?
Evidence, not taste - 4Test the break
Is the new way clearly better?
If not, go back to the pattern
NN/g's advice is clear: "designing something against conventions will add to your users' cognitive load. You'll want to do this only if it's absolutely necessary to the task or will improve efficiency" (NN/g, Krause, 2021). The same article gives an example: the floppy-disk "Save" icon is a convention, but many users have never seen a floppy disk, so it may be worth checking what your users actually recognise.
Reasons that can justify a break (the course's own checklist):
- The pattern fails your users. Research shows they don't understand it (a hamburger menu for people who never open menus).
- The task is different. A pattern built for occasional use slows down experts who repeat the task all day.
- Accessibility. The usual pattern excludes people (a drag-only interaction with no keyboard alternative).
- A real new capability. The product does something no pattern covers yet.
Reasons that don't: "it looks fresher", "our brand is different", "the competitor does it" (unless users expect it), "I was bored of tabs".
A worked example. A team wants to replace the normal checkout with a single swipe to pay, because it "feels modern". Run the check: is there a pattern? Yes, a "Pay" button. Does it fail users? No evidence. Is there a gain? Maybe speed, but swipe is hard to discover and harder for some motor impairments. Decision: keep the button. If the team still wants to try, test both versions with users first.
5. Common mistakes
- Inventing a custom control for something a standard one already does.
- Mixing patterns from different platforms (Android-style menus in an iPhone app).
- Copying a pattern from a famous app without checking it fits your users.
- Following a pattern so strictly that it ignores your users' real task.
- Breaking a pattern and never testing whether the new way works.
6. Vocabulary
| Term | Meaning |
|---|---|
| Design pattern | A proven solution to a recurring design problem |
| Pattern library | A collection of patterns with guidance on when to use them |
| Convention | A pattern so common that people expect it |
| Jakob's Law | People expect your product to work like the others they use |
| Internal consistency | The same patterns everywhere in one product |
| External consistency | Following the conventions of the platform and industry |
7. Try it (no tools needed)
- Choose a task, for example "filter a list of products".
- Look at how three different apps or sites solve it. Sketch each in a few lines.
- Write down what they share (that's the pattern) and where they differ.
- Find one app that breaks a pattern you know. Write whether you think the break is justified, using the reasons above.
Reflection questions: Which pattern do you use every day without noticing? When did an unusual design delight you, and when did it just slow you down?
8. If you already practise
- Before a critique, check the platform guidelines for the pattern under discussion; it saves debates about taste.
- Document every deliberate break in your design system, with the reason and the research behind it.
- When you break a pattern, plan a test with people who know the usual pattern well; they are the ones most likely to stumble.
Checklist
Learn more
- NN/g: Jakob's Law of Internet User Experience (video, 2017) · Maintain Consistency and Adhere to Standards (2021) · Design-Pattern Guidelines: Study Guide (2024)
- Pattern libraries: Material Design 3 · Apple Human Interface Guidelines · GOV.UK Design System
- Laws of UX: Jakob's Law
Books, courses and videos to go deeper
- Designing Interfaces: Patterns for Effective Interaction DesignJenifer Tidwell, Charles Brewer and Aynne ValenciaBook · O'Reilly, 3rd edition, 2020 (Amazon)
- A Pattern LanguageChristopher Alexander and othersBook · Oxford University Press, 1977
Book links go to Amazon. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.
Related
What a design system is · How people think · Navigation patterns · Heuristic evaluation · Pattern tiers