✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the single best starting point if you think design just means making things look nice. Riley wrote it as an open letter to founders, walking through what design actually is (problem solving, clarity, direction) and why it decides whether people take your product seriously. It is short, visual, and written for non designers, so a technical founder can read it in one sitting and come away with a working mental model.
From
Wells Riley
by Wells Riley
15 min read
- Design is about how a product works and communicates, not just how it looks
- A clear point of view and consistency read as competence to users and investors
- You can build design sense even without a design background if you pay attention
Open
startupsthisishowdesignworks.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
This is the book behind the whole idea that good design is affordances and feedback, the exact language in our short answer. Norman shows why people fail with confusing products (a door they push when they should pull) and how clear signifiers let anyone succeed without instructions. Read it and you will stop blaming users for being confused and start seeing the confusion as a design bug you can fix.
From
Don Norman
by Don Norman
Book, approx 350 pages
- Affordances and signifiers tell people what they can do without a manual
- Every action needs immediate, visible feedback or users feel lost
- When someone fails to use your product, the design failed, not the person
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
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
This is the famous story of Airbnb flying to New York and photographing listings door to door, the most literal example of doing things that do not scale to fix a dead marketplace. Revenue doubled that week after eight flat months, which is the proof that hand work on supply changes the whole market. Read it when you need the courage to go do unscalable things yourself.
From
First Round Review
by First Round Review
12 min read
- Founders personally fixed listings instead of writing guidelines
- One week of manual work doubled revenue after months of flat
- The unscalable fix taught them what to build for everyone else
Open
review.firstround.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Graham argues that good design is not just personal opinion, it has real properties (simplicity, honesty, solving the hard problem) you can learn to see. For a founder, this reframes taste as a skill you build rather than something you are born with. It is the essay that gives you a vocabulary for why one solution is genuinely better than another.
From
Paul Graham
by Paul Graham
25 min read
- Good design is simple, honest, and solves the actual problem
- Taste is a trainable judgment, not random personal preference
- Good design is redesign, expect to throw away early versions
Open
paulgraham.com →
📄 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 →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This backs up the first three seconds claim with research: people judge a page in milliseconds, and that snap verdict is hard to reverse. It explains the psychology of why a cluttered or unclear first screen makes visitors bounce before they read a word. Useful when you need to justify to a cofounder why the homepage and onboarding deserve real attention.
From
Nielsen Norman Group
by Therese Fessenden
10 min read
- Users form a gut judgment about your product almost instantly
- A messy first screen gets people to leave before they understand the value
- Clean, familiar layouts let the brain process your product effortlessly
Open
nngroup.com →
📖 Book
✓ Link checked
Free
Beginner
Why we picked it
Free to read online, with chapters like "Build Less" and "Half, Not Half-Assed" that name your exact trap. It argues that cutting scope is a feature, and that the version with fewer things done well beats the bloated one. A fast, opinionated read you can skim straight to the chapters that sting.
From
Basecamp / 37signals
by Jason Fried, David Heinemeier Hansson (37signals)
Free online, ~4 hr
- Build half a product, not a half-built product.
- Every feature you add is one more thing to maintain and explain.
- Deliberately underdo the competition on scope.
Open
basecamp.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Linear is a small, largely distributed team that ships a famously polished product, and this breaks down how they organize around projects and keep scope tight. You will see how a lean team stays accountable through clear ownership and shipped work rather than process theater. Relevant because it is a modern example of the visible-output, small-team model working in practice.
From
Lenny's Newsletter
by Lenny Rachitsky
~20 min read
- Teams form around a project, then disband when it ships
- Keep scope small so progress stays visible
- Ownership and shipped work replace heavy process
Open
lennysnewsletter.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
The most memorable proof that watching users pays. A single confusing choice on a checkout form was quietly costing a retailer a fortune, and it only surfaced when the team observed real people stumble on it. Read it when you need to convince yourself, or a co-founder, that an afternoon of watching users is worth it.
From
LukeW / User Interface Engineering
by Luke Wroblewski
~6 min read
- One confusing button silently blocked huge numbers of users
- The fix was obvious only after watching people fail
- Small usability problems can carry very large costs
Open
lukew.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
This is the piece that gives you permission to stop waiting for a big study. Nielsen shows that just five people uncover roughly 85 percent of the usability problems in your app, and that running several small tests beats one large one because you can fix things between rounds. For a founder with no budget, it reframes testing from a scary research project into something you can do this week.
From
Nielsen Norman Group
by Jakob Nielsen
About a 10 minute read
- Five users find about 85 percent of usability problems, so you do not need a large sample to learn what is broken
- Running three small tests and fixing between them beats a single big study
- The rule holds for qualitative testing of a fairly similar user group, so split into small groups if your users are very different
Open
nngroup.com →
Why we picked it
Facebook's first design VP explains what design actually is beneath the surface of pretty screens. She frames it as solving a real problem for a real person, which reframes the whole should-I-learn-Figma question. It is a short, calming read for a founder anxious that they are not a designer.
From
The Year of the Looking Glass
by Julie Zhuo
8 minute read
- Design is problem solving for people, not decoration
- Caring about the user's experience is the core skill, tools are secondary
- You do not need a design degree to design thoughtfully
Open
medium.com →
