📖 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
Intermediate
Why we picked it
This answers the flip side of the question, how much design to do yourself versus when to bring in a real designer. It lays out what a first design hire actually changes and how to know you are ready. A founder learns where the do-it-yourself Figma phase ends and a professional should take over.
From
First Round Review
by First Round Review
30 minute read
- Founders should do early design themselves before hiring
- Know the signals that it is time for a real designer
- A first designer shapes product, brand, and trajectory, not just screens
Open
review.firstround.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
This is a clear, opinionated take from an investor who has watched many teams get the timing wrong. It argues for hiring design earlier than most technical founders instinctively do, and it names the real cost of waiting: compounding design and product debt that gets expensive to pay down later. Read it as a starting point to pressure-test your own "is it time yet" gut call, not as a rule that fits every stage or budget.
From
Amplify Partners
by Joshua Goldenberg
- The signal is not just aesthetics: if your product is only usable through a UI, a designer becomes a core pillar alongside product and engineering sooner than you think.
- Waiting compounds design debt (weak information architecture, muddled features) that is far cheaper to fix early than after the product grows.
- For a very early founder without designer budget, the practical read is to close the gap with a strong design system now and hire once the design work is steady enough to keep someone busy.
Open
amplifypartners.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Practical guidance from someone who has placed many founding designers, on when the hire actually pays off and how to run the process. It is specific about the signals that tell you it is time, rather than vague encouragement to hire early. Keep it for when a template genuinely stops being enough.
From
Andy Budd
by Andy Budd
- Look for concrete signals of readiness, not a calendar date.
- A founding designer needs range, not just craft.
- Run a real process so you are not swayed by a pretty portfolio.
Open
andybudd.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
The counterargument worth hearing: that a strong designer earns their keep before polish, by shaping the product around real user needs. Reading it alongside the "wait" pieces keeps you honest about the tradeoff instead of anchoring on one side. Useful for deciding which kind of designer, if any, your problem calls for.
From
Andy Budd
by Andy Budd
- Design can be product strategy, not just decoration.
- Bringing design in too late means polishing the wrong product.
- The real question is what kind of designer, not just when.
Open
andybudd.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
A calm, structured walkthrough of hiring your first designer: what to look for, how to scope the role, and how to evaluate portfolios when you are not a designer yourself. It helps a technical founder run the process without being bluffed by attractive work. Save it for when you have decided the hire is real.
From
Designer Fund
by Heather Phillips
- Judge process and problem solving, not just finished visuals.
- Define the role around your current stage and gap.
- A structured evaluation protects a non-designer founder from guessing.
Open
designerfund.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 →
✍️ 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 →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
From a former Facebook VP of Design, this clarifies what senior design judgment actually buys you, which is the "taste" you might be tempted to hire early. Understanding it helps you tell when that judgment is worth paying for versus when a component library suffices. It also sharpens how you interview when the time comes.
From
The Looking Glass
by Julie Zhuo
- Senior design judgment is about noticing, not just producing.
- Naming what great design does helps you decide if you need it yet.
- The same lens makes you a better interviewer when you do hire.
Open
lg.substack.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 single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
From
momtestbook.com
by Rob Fitzpatrick
~130 pages
- Talk about their life, not your idea.
- Ask about specifics in the past, not opinions about the future.
- 'That's so cool, I'd totally buy it' is a compliment, not data, dig for commitment and evidence.
Open
momtestbook.com →
Why we picked it
A free, fast preview of the Refactoring UI mindset that you can apply this afternoon. It gives you seven fixes (use more white space, add a hint of color, use fewer borders, think outside the box) that instantly lift a default no-code layout. If you only read one thing before your next design pass, read this.
From
Refactoring UI (Medium)
by Adam Wathan and Steve Schoger
10 min read
- Extra white space alone makes a cramped screen feel considered
- Accent color and soft shadows replace heavy borders and boxes
- Emphasize by de, emphasizing everything else, not by making one thing louder
Open
medium.com →
