📖 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 →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the canonical source of the ship-ugly-first idea, the LinkedIn co-founder's own essay behind the line about being embarrassed by your first version. For a solo dev deciding how much to build into a referral program before shipping, this is the judgment call at the heart of the question, launch the rough version and let real usage tell you what to add. Hoffman also draws the line on where ship-fast should not apply, which keeps it honest rather than a slogan.
From
LinkedIn
by Reid Hoffman
About a 6 minute read
- Ship the version you are slightly embarrassed by, because real user behavior teaches you what to build far faster than internal guessing
- Embarrassing is not the same as harmful: launching fast does not excuse things that alienate users or create real risk
- Speed compounds: earlier feedback means earlier iteration, which matters more than polishing features nobody has asked for yet
Open
linkedin.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Turns the vague feeling of product-market fit into a number you can move. Ask users how they would feel if they could no longer use the product, then track the share who say 'very disappointed'. Under 40 percent means keep working. A test you can run on an idea long before you scale it.
From
First Round Review
by Rahul Vohra
~20 min read
- The 40 percent 'very disappointed' benchmark for product-market fit.
- Segment to your high-expectation customers and build for them.
- Make the fit score a metric you improve quarter by quarter.
Open
review.firstround.com →
📖 Book
✓ Link checked
Free
Intermediate
Why we picked it
Basecamp's battle-tested, opinionated system for shipping meaningful work in fixed cycles without endless backlogs, a primary source, free in full. The antidote to over-planning your roadmap.
From
Basecamp / 37signals
by Ryan Singer
free online book
- Work in short cycles with a cool-down between them.
- Fix time, vary scope, use 'appetites,' not estimates.
- Make bets, not plans; no runaway backlog.
Open
basecamp.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Lenny addresses prioritization specifically for early startups, where the usual scoring frameworks break down and speed matters more than spreadsheets. It helps you decide what to work on when you have almost no data and everything feels urgent. Practical and grounded in how real early teams actually choose.
From
Lenny's Newsletter
by Lenny Rachitsky
~15 min read
- Heavy prioritization frameworks are usually overkill before product-market fit.
- Bias toward the few bets that could actually move whether people want the core thing.
- Shipping and learning fast matters more than perfectly ranking your backlog.
Open
lennysnewsletter.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Des Traynor makes the case that "no" is the product strategy, and that adding a feature for one loud customer quietly costs every other user. It gives you language to defend a tight v1 against constant requests. Short, sharp, and directly about the discipline of cutting.
From
Intercom (Des Traynor)
by Des Traynor
~8 min read
- A cohesive product with clear boundaries beats a pile of tangential features.
- Every feature you add has an ongoing cost, not just a one-time build cost.
- No single customer request is worth more than a coherent product.
Open
intercom.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Cohen argues the MVP framing pushes founders to ship something too broken to love, and offers an alternative: make it Simple, Lovable, and Complete instead. It sharpens the cut so you remove scope without removing quality on the one thing you decide to keep. A useful corrective to "just ship anything."
From
A Smart Bear (Jason Cohen)
by Jason Cohen
~12 min read
- Cut breadth, not quality, so the one workflow you keep is genuinely good.
- Simple and complete beats broad and half-working.
- A narrow product people love earns more than a wide one people merely tolerate.
Open
longform.asmartbear.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The customer-development originator's clearest statement on scoping the minimum feature set to reach your earliest believers. The sharpest antidote to feature creep in v1.
From
steveblank.com
by Steve Blank
~8 min read
- Ship the smallest set your earlyvangelists will actually pay for.
- Extra features before fit are engineering waste.
- The MVP is a Customer Development tactic, get it into users' hands fast.
Open
steveblank.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Cagan draws a sharp line that saves founders real pain: the thing you use to test a hypothesis is an experiment, not a product you ship to everyone. He argues for calling it an MVP test so you do not confuse a throwaway prototype with something customers must be able to rely on. This keeps you from over-building a 'real' product when a rough test is all you need.
From
Silicon Valley Product Group
by Marty Cagan
6 min read
- Separate the MVP test (an experiment) from a product you would ship broadly
- A prototype that proves usable is not proof people will choose to use it
- Keep experiments cheap and disposable, do not gold plate them
Open
svpg.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This companion piece warns about the opposite failure: cutting so hard that the thing is minimal but not actually viable or usable. It helps you find the floor, the point below which the product stops being worth using. Read it alongside your cut list to check you have not gone too far.
From
Silicon Valley Product Group (Marty Cagan)
by Marty Cagan
~6 min read
- Minimal is not enough on its own; the product still has to be usable and worth choosing.
- Find the floor where cutting more would break the core value.
- Viability, not just smallness, is the real target for v1.
Open
svpg.com →
📖 Book
✓ Link checked
Paid
Beginner
Why we picked it
Ries gives you a working method for reading weak signals instead of guessing: build a small test, measure how real people respond, and learn fast enough to change course before a year is gone. Its most useful idea for this question is validated learning and the pivot-or-persevere call, a concrete way to decide whether an idea is worth continuing. Read it as a discipline for catching a dead-end early, not as a growth-hacking manual.
From
theleanstartup.com
by Eric Ries
~330 pages
- Validated learning means progress is measured by what you have actually confirmed with customers, not by how much you have built.
- The build-measure-learn loop is meant to shorten the time between an assumption and honest feedback on it.
- Pivot or persevere is a scheduled, evidence-based decision, so you are not drifting on an idea by default.
Open
theleanstartup.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
Altman's condensed operating manual for founders, including sharp guidance on focus, spending your time on what only you can do, and prioritization. Primary source, endlessly re-read.
From
playbook.samaltman.com
by Sam Altman
long
- A founder's job narrows to a few things: set the vision, hire well, and don't run out of money
- Focus and intensity beat breadth, do a few things extremely well
- Momentum and growth are the founder's core responsibilities
- Protect your time for the highest-leverage work only you can do
Open
playbook.samaltman.com →
Why we picked it
The permission slip to recruit users by hand, do things manually, and deliver 'insanely great' experiences to your first few customers. The cheapest, most honest way to validate demand is to go get it one person at a time.
From
paulgraham.com
by Paul Graham
~15 min read
- Recruit your first users manually, don't wait for them to come.
- A tiny group of users who love you beats a big group who like you.
- Manual, unscalable effort early is a feature, not a failure.
Open
paulgraham.com →
