Heuristics H4 5 min read

Same dosa, every time

04 Heuristic 4 Consistency and Standards

Users shouldn't have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

Users arrive with expectations built from every product they've ever used. When your design breaks those expectations — even creatively — they don't complain. They just leave. Consistency is not a constraint. It's how trust is built.

01 — Consistency everywhere

Consistency is not just a design word

Want to build muscle? Train consistently. Want to become a better singer? Practice consistently. Want to succeed at anything? Consistency is what gets you there.

Design is no different. The problem is when we hear "consistency" in a design context, we limit it to colours, icons, or layout. But it runs much deeper — through process, language, interaction patterns, and the mental models users bring every time they open a product.

"Consistency isn't boring. It's how users build trust with a product — one interaction at a time. Every time the product behaves the way they expect, that trust deepens."

— The real meaning of H4

02 — The dosa story

When creativity broke my expectation

Personal story — South India

A Masala Dosa with beetroot. I left after half

I'm from South India, and like most people here, I love dosas — especially Masala Dosas. Crispy crepes with spicy potato filling inside. There's a strong mental model for what a Masala Dosa is supposed to taste like.

About seven years ago, a new restaurant opened near my area. Curious, I went in and ordered one. The chef had added beetroot to the potato filling. The dosa arrived pinkish, slightly sweet, and completely unexpected.

It wasn't terrible. But it wasn't what I came for. I ate half and left. I never went back — not because the food was bad, but because my expectation was broken. I couldn't trust what I'd be getting next time.

Same name. Same category. Completely different experience. They didn't complain — they just never returned.

Apply this directly to digital products — if users expect one thing and experience another, they won't complain. They'll just never return. Broken consistency doesn't generate feedback. It generates quiet churn.

03 — Two types of consistency

Internal and external — both matter

Consistency in design operates at two levels. Most designers focus on one and forget the other.

Internal consistency

Your product speaking one language

If text links are light blue with underline on hover in one section, that same pattern should apply everywhere. Change it on another page — same visual element, different behaviour — and you've broken the user's mental model of your own product.

Internal consistency means your product has one clear design language from start to finish. Every screen, every state, every interaction should feel like it came from the same place.

External consistency

Your product fitting into the world

Users bring habits from every other product they've used. Blue means clickable. Magnifying glass means search. Cart means checkout. These conventions exist across the web — and users arrive at your product already knowing them.

You can break these conventions. But you'll pay for it in confusion, support queries, and drop-off. Creativity is great — but not at the cost of learnability.

Internal consistency keeps your product coherent. External consistency keeps it learnable.

04 — Jakob's Law

Users bring the whole internet with them

J
Jakob's Law — Jakob Nielsen

"People spend most of their time using digital products other than yours."

This means users arrive at your product with expectations already formed — shaped by every other product they've ever used. Your product is not their first. It won't be their last. Design with that in mind.

When a user opens your product for the first time, they already know what a magnifying glass means, what the cart icon means, that blue text is usually clickable. That prior knowledge is an asset — if you honour it.

The moment you replace a standard icon with a custom one — or change a convention just to feel different — you're asking users to spend cognitive effort on something they'd already solved in every other product they've used.

"Creativity is great. But not at the cost of learnability. When a standard already exists, the best design decision is often to use it."

— Jakob's Law applied

05 — Why standards exist

The magnifying glass is universal for a reason

Why is the search icon a magnifying glass everywhere? Why do all e-commerce platforms use a cart? Because across millions of users and decades of usage, these conventions have become universal. Users recognise them instantly — without thinking.

Search magnifying glass
Checkout cart icon
Home house icon
Menu hamburger icon

This heuristic connects directly back to H2 — Match Between System and the Real World. Consistency and real-world mapping are two sides of the same coin. Standards exist because they work. And they work because everyone already knows them.

06 — Closing thought

One click, one screen, one dosa at a time

A consistent experience doesn't limit creativity — it amplifies clarity. When users can predict how your product will behave, they stop thinking about the interface and start focusing on their actual goal. That's when a product truly disappears — and becomes effortless.

Design for internal consistency so your product feels unified. Design for external consistency so your product feels familiar. That's how trust is built — interaction by interaction, screen by screen.

The lesson from H4

Consistency isn't boring. It's smart UX. And the dosa story is proof: when you break the expectation — even with good intentions — users leave quietly. Build the dosa they came for.

T1

Apply this to your next design

Do a consistency audit. Pick one interaction pattern in your product — a button style, a link colour, an icon — and trace it across every screen. Does it behave the same everywhere? If not, you've found your first H4 fix.

T2

Up next

H5: Don't Fix Mistakes. Prevent Them. Why the best error message is the one that never needs to appear — and how good design stops mistakes before they happen.