Michael Seibel - How to Plan an MVP

11 insights saved from this video by @business

@business
Airbnb tested its lodging marketplace without payments or maps, proving later features can wait.
@business
Twitch began as Justin TV, a single-channel, low-resolution livestream of one founder’s life.
@business
Stripe’s founders integrated the product themselves to win users and find bugs before customers encountered them.
@business
During a three-week sprint, remove nonessential features after one week. If none qualify, remove important features to ship.
@business
Customer use reveals whether a product solves the problem. Interviews cannot fully validate something unbuilt.
@business
An MVP can be a landing page and spreadsheet if users can engage with its core value proposition.
@business
Hold the problem and customer tightly. Keep the solution flexible when your first implementation fails.
@business
Your first users should be people you already know have the problem, not an undefined audience.
@business
Many founders stop before a single user touches their product. Launching is the first critical threshold.
@business
Writing the specification exposes scope drift before a short plan quietly becomes a much longer one.
@business
Talk to users first, launch tiny, hold the problem constant, and keep iterating until the solution works.

More from Y Combinator

Startup Experts Discuss Doing Things That Don't Scale15 insights

See everything from Y Combinator

Keep what you found in Michael Seibel - How to Plan an MVP

A free account saves any of these cards to your Collection, and Korva resurfaces them so you actually remember.