✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the one principle that answers your worry head on: users spend most of their time on other apps, so they expect yours to work the way those do. It names why familiarity is a feature, not laziness, and where the mental models your users already carry come from. Treat it as the case for copying on purpose, then read the counterpoint below for where copying stops paying off.
From
Laws of UX
by Jon Yablonski (principle by Jakob Nielsen)
5 min read
- Users build expectations from every other app they use, then bring those expectations to yours, so matching known patterns lowers the effort to learn your product.
- Copying a convention is not unoriginal, it frees the user to focus on the task instead of decoding your interface.
- The familiarity that helps is external consistency (matching the wider category), not just internal consistency inside your own app.
Open
lawsofux.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The most accessible, practical intro to usability ever written, you can read it in a weekend and immediately fix your product. The definition of 'make it obvious, not clever.'
From
sensible.com
by Steve Krug
~200 pages
- Self-evident design is the goal, kill anything that adds thinking.
- Users satisfice: they scan and click the first reasonable option.
- Cheap, frequent usability testing beats large formal studies.
Open
sensible.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Concrete evidence for what originality in the wrong place actually costs. It shows how novel patterns confuse users and slow them down, with real examples. Read it before you decide your product's checkout, search, or menu needs to look different from everyone else's.
From
Nielsen Norman Group
by Katie Sherwin
8 min read
- Unfamiliar patterns force users to stop and relearn basic actions.
- Novelty for its own sake reads as friction, not delight.
- The safest place to be different is your actual value, not your plumbing.
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This separates internal consistency (within your product) from external consistency (matching the wider world of apps your users already use). That second kind is exactly what the short answer is about. It gives you a clean way to reason about which conventions to inherit.
From
Nielsen Norman Group
by Nielsen Norman Group
7 min read
- External consistency means following the norms of the whole industry.
- Words, icons, and actions should mean what users already expect.
- Consistency is not about your product agreeing with itself alone.
Open
nngroup.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
When you and your technical hire are arguing about the stack, this essay reframes the whole fight: the goal is not the best or newest tool, it is shipping a product and keeping the company alive. McKinley's idea that every team has only about three innovation tokens gives you a shared, honest test to settle most stack disagreements before they turn personal. It is the closest thing to a neutral referee both sides can respect.
From
mcfunley.com
by Dan McKinley
~20 min read
- Every team gets about three innovation tokens, so spend novelty only where it is core to the product, not on the database or the framework.
- Prefer well understood technology, because its failure modes are documented and the long-term cost of keeping things running dwarfs any early convenience.
- Adopting new tech should require a real conversation about the problem it solves, not one person's preference, which is exactly the frame a founder and hire need.
Open
mcfunley.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Design tactics written specifically for developers and non-designers who need to ship good-looking UI without a design background. The most practical 'make it not ugly' resource there is.
From
refactoringui.com
by Adam Wathan & Steve Schoger
~250 pages
- Use spacing, hierarchy, and font weight, not just color, for visual hierarchy.
- Start with too much whitespace, then remove.
- Design in grayscale first to nail hierarchy before adding color.
Open
refactoringui.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The book behind the site, and worth it if you want the reasoning, not just the rules. Yablonski walks through familiar apps and shows exactly how Hick's, Fitts's, Jakob's, and a handful of others shaped them. Short enough to finish in a weekend and give you a real mental model instead of a list to memorize.
From
Laws of UX
by Jon Yablonski
Approx. 150 pages
- Real app teardowns show each law in the wild
- Covers the ethics of using psychology, not just the tactics
- A weekend read that upgrades how you look at any interface
Open
lawsofux.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Users judge attractive products as more usable, which is why polish matters and also why it can hide real problems. As a founder this cuts both ways: a clean look buys goodwill, but it can mask issues that surface once users hit a real task. Read it so you know when to trust a good looking demo and when not to.
From
Nielsen Norman Group
by Kate Moran
8 min read
- People perceive attractive interfaces as easier to use
- A pretty design forgives small usability flaws but not large ones
- Good looks can hide problems during your own testing
Open
nngroup.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
The foundational text on human-centered design that every product person should read once. It rewires how you see every product, including your own.
From
jnd.org / Basic Books
by Don Norman
~350 pages
- Make affordances and signifiers obvious, users shouldn't guess.
- Give clear, immediate feedback for every action.
- Design out errors rather than blaming users ('human error' is usually design error).
Open
jnd.org →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
A practical, structured playbook for the exact fear in this question: users quietly leaking away. Lenny breaks retention into activation, engagement, and resurrection, and shows that almost every durable win comes from fixing the first 7 to 30 days. It gives you concrete levers to pull rather than a vague plea to care more.
From
Lenny's Newsletter
by Lenny Rachitsky
~15 min read
- Most retention wins come from improving the earliest days of use
- Find the single early action that separates users who stay from those who go
- If people activate and still leave, the issue is fit, not onboarding
Open
lennysnewsletter.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
The law in the author's own words, with the reasoning and the stakes spelled out. Nielsen explains why users transfer expectations across sites and what it costs you to fight that. Read the primary source once so you understand the idea, not just the slogan.
From
Jakob Nielsen (Substack)
by Jakob Nielsen
7 min read
- The principle direct from the person who named it
- Explains why users transfer habits between products
- Makes the real cost of ignoring conventions concrete
Open
jakobnielsenphd.substack.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Argues for stripping the interface down to essentials, which pairs neatly with copying conventions: keep the common parts quiet and familiar so your one genuinely new idea has room to stand out. A practical rule for what to leave plain.
From
Nielsen Norman Group
by Therese Fessenden
7 min read
- Every extra element competes with the thing that matters most.
- A calm, conventional surface makes your real value more visible.
- Restraint is how you keep familiar from turning into cluttered.
Open
nngroup.com →
