📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
Blank, who built customer development, uses a real founder story to show how a team defaulted to 'build a smaller product' when the right move was a test that cost almost nothing. The piece pushes you to name your riskiest assumption and design the cheapest possible experiment against it. It is a direct match for the idea that your MVP might be a conversation or a fake feature, not code.
From
steveblank.com
by Steve Blank
7 min read
- Start from the assumption that could kill you, then test only that
- The cheapest experiment that answers the question beats a small polished build
- You are selling the vision but delivering the minimum feature set
Open
steveblank.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
The free, original essay that defined the MVP before the book existed, written plainly by the person who coined the term. It clears up the most common mistake founders make, which is thinking an MVP has to be a working product when a landing page or a video often teaches you more, faster. Useful as a quick primer you can send someone in one link.
From
Startup Lessons Learned (Eric Ries)
by Eric Ries
~15 min read
- An MVP is the smallest thing that produces validated learning, not the smallest product
- A page or a video can be a legitimate MVP if it tests real demand
- Aim for maximum learning per unit of effort, not feature completeness
Open
startuplessonslearned.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 →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
The essay that put 'product-market fit' into the startup vocabulary. Read it for the gut-level description of what PMF feels like when it's happening vs when it isn't, the intuition behind the metrics.
From
pmarchive.com
by Marc Andreessen
~15 min read
- Market matters most; a great market pulls product out of a startup.
- You can feel PMF, customers buy as fast as you can ship.
- Before PMF, do whatever it takes to get there; nothing else counts.
Open
pmarchive.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 →
✍️ 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
Beginner
Why we picked it
The canonical fake-door test, told by the founder who ran it. Buffer started as a two-page site: one page pitched the tool, a pricing button led to an email capture, and every signup got a personal note. Real demand, real conversations, a paying customer in weeks, and not a line of product code.
From
Buffer
by Joel Gascoigne
~10 min read
- Test willingness to pay with a pricing page before you build.
- Email every signup by hand and start a conversation.
- A landing page measures behaviour, not opinions.
Open
buffer.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
This is the cleanest short explanation of the two manual-first MVPs and, more importantly, how they differ, which is where most founders get confused. Concierge means you are the visible front end doing the work by hand, Wizard of Oz means you have a real interface but a human quietly runs the back end. It walks a single concrete product example through both, so you can see which one actually answers the question you are trying to answer.
From
Mind the Product
by Amanda White
~8 min read
- Concierge MVP: no interface yet, you personally take inputs and deliver the result by hand, and the user knows it is manual.
- Wizard of Oz MVP: a real front end that users think is automated, while humans do the work behind it, useful for testing whether people will use the interface itself.
- Pick based on what you need to learn: concierge tests whether the service is wanted, Wizard of Oz tests whether the product experience works before you build the automation.
Open
mindtheproduct.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A clear, jargon-free explainer that corrects the most common misuse of the term, where teams ship a broken product and call it 'minimum viable.' It stresses that viable means it still has to deliver real value, even while being small. A good grounding read if you are unsure where the line sits between too little and just enough.
From
Nielsen Norman Group
by Sara Paul
8 min read
- Minimum and viable both matter, so it must still deliver real value
- An MVP is for learning, not for shipping a knowingly broken experience
- Scope down features, not the quality of the core value you promise
Open
nngroup.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Beck, a foundational voice in software, adds useful nuance about what minimal really means and why teams so often get it wrong. His argument that you rarely know the right minimal product up front, so start smaller, guards against building too much under the MVP label. A thoughtful counterweight when your MVP is quietly growing into a full product.
From
Tidy First (Kent Beck)
by Kent Beck
~1,000 words
- You usually do not know the true minimal product in advance
- When in doubt, start smaller than feels comfortable
- Minimal is defined by the learning you need, not the roadmap
Open
newsletter.kentbeck.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
The nuanced counterweight: PMF isn't a single binary moment, it can be lost, and 'market' is doing more work than founders think. Read after the Andreessen essay to avoid the common traps.
From
a16z.com
by Andreessen Horowitz (a16z)
~20 min read
- PMF is a spectrum, not an on/off switch, and it can decay.
- Product-user fit often comes before product-market fit.
- Beware false positives from a small, unrepresentative group.
Open
a16z.com →
📄 Article
✓ Link checked
Freemium
Intermediate
Why we picked it
Years on, Ries revisits what the lean method got right and where the MVP idea gets abused, which is precisely the trap in your question. He is candid that the hardest part is knowing what minimal, viable, and product really mean up front, so start smaller. A grounded read that treats the MVP as a tool that is easy to misuse rather than a magic word.
From
Lenny's Newsletter
by Lenny Rachitsky and Eric Ries
~4,000 words
- The MVP label is often stretched to excuse shipping too much
- Nobody knows the exact minimal product at the start
- Learning speed, not launch speed, is the real goal
Open
lennysnewsletter.com →
Why we picked it
The book that gave the world 'MVP', 'build-measure-learn', and 'validated learning'. It reframes a startup as a series of experiments, not a bet, the mental model everything else in this category builds on.
From
theleanstartup.com
by Eric Ries
~330 pages
- Progress = validated learning, not features shipped.
- Build the minimum that produces a real learning loop.
- Decide pivot-or-persevere on evidence, on a schedule.
Open
theleanstartup.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 →
Why we picked it
A step by step process for taking an idea to something people want without building the wrong product first. Maurya's mantra, love the problem not your solution, keeps your first MVP focused on testing risk rather than shipping features. Practical if you want interview scripts and a repeatable order of experiments instead of theory.
From
Ash Maurya (O'Reilly)
by Ash Maurya
~336 pages
- Rank your assumptions and test the riskiest one first
- Love the problem, not your solution
- A one page model beats a long plan for an early idea
Open
oreilly.com →
