A design team is building a new feature where users confirm before deleting their account. A junior designer proposes a custom 'swipe-to-confirm' interaction they invented. A senior designer suggests using the team's existing modal dialog component. What principle most strongly supports the senior designer's recommendation?
AEfficiency — the modal is faster to build, so it is always preferable
BUsers already understand the modal confirmation pattern, reducing cognitive load — a custom interaction requires learning a new micro-interface for a common task
CCreative design requires avoiding existing patterns whenever possible
DThe swipe interaction should be preferred because it is more innovative
Most design problems are not novel — they are variations on well-understood interaction types. 'Confirm before destructive action' is a classic, established pattern. Using the existing modal dialog means users immediately understand what to do (they have seen this hundreds of times), reducing cognitive load. A custom swipe-to-confirm interaction requires every user to learn a new interaction for a problem that already has a proven solution. As the explainer states, reaching for a custom solution when a standard pattern would serve the user better 'is not being creative; they are adding unnecessary learning cost for the user.'
Question 2 Multiple Choice
What is the relationship between a design pattern and a component?
AThey are synonyms — both refer to reusable visual elements in a design system
BA component is the abstract solution; a pattern is its concrete implementation in code or Figma
CA pattern is the general, abstract solution to a recurring problem; a component is the specific, reusable implementation that brings the pattern to life
DPatterns are for interaction design; components are exclusively for visual styling
The explainer uses the recipe/ingredient analogy: a pattern is the recipe ('use a modal dialog to confirm destructive actions') — a general approach at an abstract level. A component is the pre-made ingredient — a specific, reusable building block with defined appearance, behavior, and code. The same pattern can be implemented by different components in different contexts. Conflating the two confuses levels of abstraction: patterns answer 'what approach to use,' components answer 'here is the specific implementation.'
Question 3 True / False
Using design patterns limits designer creativity by constraining which solutions are considered.
TTrue
FFalse
Answer: False
This is explicitly the misconception the topic addresses. Well-chosen patterns *free* designers to focus creative energy on genuinely novel problems. If a designer must reinvent a search interface, a modal confirmation dialog, and a navigation structure from scratch every project, creative capital is spent on solved problems. Patterns handle recurring, well-understood challenges so creativity can be directed at the genuinely novel aspects of the design problem. The creativity lies in choosing the right pattern, adapting it skillfully, and recognizing the rare situations that require something truly new.
Question 4 True / False
A design component in a design system should be customized separately for each new use case to ensure it fits each project's context perfectly.
TTrue
FFalse
Answer: False
Components are specifically designed to be *reusable across contexts* — that is their defining purpose. A component rebuilt or heavily customized for every use case defeats the core benefits: consistency, reduced reinvention, and the ability to work at scale. Design systems provide components as shared, stable building blocks precisely so teams can use them across many projects without recreating them. When a component needs significant customization every time, it may indicate the component was designed at the wrong level of abstraction, or that a genuinely new component needs to be added to the system.
Question 5 Short Answer
In your own words, explain why knowing *when not* to use an existing pattern is as important as knowing how to apply one.
Think about your answer, then reveal below.
Model answer: Most design problems are variations of known patterns, and the skill is recognizing which pattern fits and applying it. But occasionally a genuinely novel interaction problem arises that no existing pattern adequately addresses. Using an ill-fitting pattern in that case can be worse than designing from scratch: forcing users into a familiar-looking interaction that behaves unexpectedly is more disorienting than encountering something clearly new. Knowing when not to use a pattern requires understanding *why* the pattern works — its underlying logic and what user needs it serves — so you can judge whether those conditions are actually met.
This judgment separates skilled from novice designers. A novice may reach for the wrong pattern because it looks superficially similar to the problem at hand. An expert recognizes that the superficial similarity masks a functional difference making the pattern inappropriate. The result of misapplying a pattern is often worse than using no pattern at all, because users arrive with wrong expectations set by the familiar-looking element. New patterns, once designed and tested, should be contributed back to the pattern library for future reuse.