📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The single most-cited usability framework in the field, from the definitive UX research authority. A checklist you can hold your product up against this afternoon.
From
Nielsen Norman Group
by Jakob Nielsen
~15 min read
- Visibility of system status, always tell users what's happening.
- Match the real world, use the user's language and mental models.
- Prevent errors, and make consistency and standards the default.
Open
nngroup.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 →
📖 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
Free
Beginner
Why we picked it
A crisp, visual reference of the psychology principles behind good UX, perfect for a founder who wants the 'why' without a design degree. Bookmark it and consult it while you build.
From
lawsofux.com
by Jon Yablonski
reference site
- Hick's Law, more choices increase decision time; reduce options.
- Fitts's Law, make important targets large and close.
- Jakob's Law, users expect your product to work like the ones they already use.
Open
lawsofux.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The practical answer to a crowded screen: show the few things most people need first, and tuck the advanced options behind a click. This one technique reduces the thinking a user has to do and lowers error rates without cutting features. Useful the moment your product grows past a simple form.
From
Nielsen Norman Group
by Jakob Nielsen
8 min read
- Show common options first, hide rare ones until asked
- This helps beginners focus and saves experts scanning time
- It resolves the tension between power and simplicity
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
This is the how behind reduce the thinking to zero. It names the three levers you actually control: cut visual clutter, build on existing mental models, and offload work with smart defaults and re-displayed information. Concrete, checklist ready advice you can apply to any screen.
From
Nielsen Norman Group
by Kathryn Whitenton
9 min read
- Remove clutter that competes for the user's attention
- Reuse familiar layouts so users do not relearn your product
- Offload memory and decisions with defaults and pre filled data
Open
nngroup.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 →
📄 Article
✓ Link checked
Free
Advanced
Why we picked it
Tognazzini built Apple's original interface guidelines, and this is his deep list of principles: anticipation, autonomy, consistency, discoverability, latency, and more. It goes further than the ten heuristics and is worth the read once the basics feel obvious. Dense, but every item is load bearing.
From
AskTog (Bruce Tognazzini)
by Bruce Tognazzini
40 min read
- Anticipate what the user needs next and put it within reach
- Consistency lets users transfer knowledge from screen to screen
- Perceived speed matters as much as actual speed
Open
asktog.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 →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Crisp, opinionated principles from the team that made government services genuinely usable at massive scale. Start with user needs, do less, and do the hard work to make it simple read like a founder's manifesto. It is short, opinionated, and free of jargon.
From
GOV.UK (Government Digital Service)
by UK Government Digital Service
10 min read
- Start with real user needs, not the org chart or your assumptions
- Do the hard work to make the product simple for the user
- Be consistent, not uniform, so patterns feel familiar without being rigid
Open
gov.uk →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Error prevention is one of Nielsen's ten heuristics, and this unpacks how to actually do it: match the user's mental model, offer sensible defaults, and use confirmations sparingly. It also warns that constant confirm dialogs backfire and train users to click through blindly. Direct, practical support for the prevent errors part of your answer.
From
Nielsen Norman Group
by Page Laubheimer
8 min read
- Mistakes come from a wrong mental model, so fix the model
- Overusing confirmation dialogs makes users ignore all of them
- Good defaults and constraints prevent errors before they start
Open
nngroup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Human short term memory is tiny, so making people remember things across screens is a hidden tax on your product. This explains why showing options beats making users recall them, with examples like visible menus over blank command lines. A concrete lens for reducing the thinking a user has to do.
From
Nielsen Norman Group
by Raluca Budiu
7 min read
- Recognition is easy, recall is hard, so keep options visible
- Do not make users remember information from a previous screen
- Context and cues help users retrieve what they need
Open
nngroup.com →
📄 Article
✓ Link checked
India
Free
Intermediate
Why we picked it
An Indian product team writing about how they think, not just how they draw. Zomato argues that good UX starts from understanding the outcome you want, then designing the experience that leads there, before touching pixels. Useful to see world class product thinking from a company building for Indian users at scale.
From
Zomato
by Zomato Design
10 min read
- Understand the desired outcome before you design the screen
- Make constraints explicit so the whole team decides together
- Design serves the product goal, it is not decoration on top
Open
zomato.com →
📄 Article
✓ Link checked
India
Free
Intermediate
Why we picked it
A behind the scenes look at how an Indian company built consistency into a fast moving product with a shared design system. It shows why consistency, one of Nielsen's heuristics, is an engineering and process problem, not just a taste one. A good read once your product has enough screens that they start to drift apart.
From
Zomato
by Zomato Design
8 min read
- Consistency at scale needs reusable components and shared rules
- A design system speeds up shipping while keeping the UI coherent
- Simplicity, user centricity, and consistency can be stated as explicit principles
Open
zomato.com →
✍️ Essay
Free
Intermediate
Why we picked it
Facebook's former head of product design on what separates good design from decoration, which reframes polish as clarity and intent rather than prettiness. It backs our point that users forgive a simple product but distrust a sloppy one. A short read that changes how you decide what to polish.
From
The Year of the Looking Glass (Julie Zhuo)
by Julie Zhuo
8 min read
- Good design is intentional and clear, not merely decorated
- Simplicity done well signals competence and care
- Decide what matters most, then make that unmistakably clean
Open
medium.com →
Why we picked it
Forms are where most products lose users, whether it is signup, checkout, or onboarding. This is the definitive guide to label placement, error handling, inline validation, and cutting fields you do not need. If your funnel dies at a form, the fix is almost certainly in here.
From
Luke Wroblewski (Rosenfeld Media)
by Luke Wroblewski
~226 pages
- Cut every field you do not truly need to reduce abandonment
- Place labels and validation where they cut thinking, not add it
- Show errors clearly and in context, next to the field
Open
rosenfeldmedia.com →
