A design team creates an app where every button is the same shade of blue, every margin is exactly 16px, and every font size follows the same scale — but users report the app 'feels like it was designed by a committee' with no clear purpose. Which concept does this scenario illustrate?
AThe design lacks consistency — the visual rules are not being applied uniformly
BThe design has consistency but lacks coherence — it follows rules uniformly without a unified purpose
CThe design is suffering from too much variety, which disrupts the user's mental model
DExternal consistency is missing — the app doesn't follow platform conventions
This is the core distinction: the design IS visually consistent (same colors, spacing, scales) but lacks coherence — the parts don't communicate a shared purpose or identity. Consistency is a necessary but not sufficient condition for coherence. A uniform is coherent (matching clothes that signal belonging to a purposeful system); perfectly matching clothes without shared purpose is just... matching.
Question 2 Multiple Choice
An e-commerce site uses a bright red button for both 'Add to Cart' and 'Delete Account.' A designer argues that using a different visual style for 'Delete Account' breaks visual consistency. What is the best response?
AThe designer is right — visual consistency requires all buttons to look the same to maintain the user's mental model
BThe designer is right — users expect identical interaction patterns across all screens
CThe designer is wrong — destructive actions should look different from routine actions because the difference in stakes is meaningful information for the user
DThe designer is wrong — but only if the app has a design system that explicitly defines button variants
This is the scenario where breaking consistency is correct. 'Consistent' does not mean 'identical in all cases.' When stakes differ meaningfully — a destructive action versus a routine one — visual differentiation communicates that difference to the user. The same appearance implies the same consequence; different appearances correctly signal different consequences. Making 'Delete Account' look different is not inconsistency — it is purposeful variation, exactly what unity-and-variety principles endorse.
Question 3 True / False
External consistency in design means that a product's own screens maintain the same visual patterns and behaviors across nearly every view.
TTrue
FFalse
Answer: False
False. External consistency refers to following conventions that users bring from other products — placing the shopping cart icon in the top right, using a magnifying glass for search, making blue underlined text clickable. Internal consistency is what applies within a single product. External consistency leverages mental models users already built from other interfaces, reducing the learning curve.
Question 4 True / False
A design can be perfectly internally consistent and still feel disjointed or purposeless to users.
TTrue
FFalse
Answer: True
True. Coherence is the deeper property that consistency alone cannot guarantee. A product where every element follows the same visual rules but those rules don't serve a unified purpose will feel haphazard even though it's 'consistent.' Coherence requires that visual identity, interaction patterns, tone of voice, and information architecture all feel like they belong to the same purposeful whole — not just the same style guide.
Question 5 Short Answer
What is the difference between consistency and coherence in design, and why is coherence considered the deeper concept?
Think about your answer, then reveal below.
Model answer: Consistency means identical elements behave identically — same button style, same interaction pattern, same icon meaning everywhere. Coherence is the property that all elements feel like they serve a unified purpose and belong to the same whole. Coherence is deeper because you can achieve perfect consistency and still lack it: a design where every pixel follows the rules but communicates no clear identity. Coherence asks whether the system has a purpose, not just a style guide.
The uniform-versus-costume analogy captures this well: both are 'consistent' outfits, but a uniform communicates belonging to a system with a purpose. In practice, building coherence requires asking not just 'are the buttons the same?' but 'does everything here reinforce the same story about who we are and what we're trying to do for users?' That question cannot be answered by a style guide alone — it requires design intention at every level of the product.