Michael Seibel - How to Plan an MVP

Definition of Minimum Viable Product (MVP)

• The MVP is defined as the simplest possible artifact capable of delivering value to a specific set of initial users.
• It is explicitly intended as a starting point for iteration, not a polished final product.

Strategic Principles for Early-Stage Startups

• Primary Goal: Launch something imperfect quickly; this principle is cited as the most critical takeaway for Y Combinator startups.
• User Discovery: Founders should engage with potential users prior to building, ideally by being their own users to validate problems immediately.
• Validation Requirement: Founders must obtain the first customer interaction to validate that the product solves a real problem; without user interaction, the idea remains theoretical.
• Feedback Loop: Immediate feedback on early, "shitty" versions is essential to verify assumptions before investing in a full-scale build.
• Strategic Rigidity: Founders should hold the problem and the customer tightly, but hold the solution loosely to allow for pivotability.
• Iteration vs. Pivoting:
  • Founders often erroneously pivot to new use cases for a broken solution (e.g., using a broken screwdriver for cooking instead of fixing it for the mechanic).
  • Correct iteration involves refining the solution to better serve the original problem and user.

MVP Construction Guidelines

• Timeline: A lean MVP should be buildable in weeks, not months.
• Feature Scope: Functionality must be condensed to only the highest-order problems of a small, specific user segment; all other features are to be ignored initially.
• Execution Methods: Startups may use landing pages, spreadsheets, or manual services (e.g., founders integrating software manually) rather than fully automated software.
• Psychological Barriers: Founders should avoid over-valuing the MVP as a "special" artifact; it is merely a base for iteration.

Case Study: Historical MVPs of Major Companies

• Airbnb (2008):
  • The initial version lacked payment processing (users exchanged cash in person).
  • There was no map view for property locations.
  • Development was executed part-time with no complex infrastructure.
• Twitch (as Justin TV):
  • Launched as a single-channel reality show about the founder's life.
  • Initially had zero video games content.
  • Utilized extremely low-resolution video without modern streaming features.
• Stripe (initially "slash payments"):
  • Featured almost no functionality and no pre-existing bank deals.
  • Founders manually integrated the product into clients' offices to identify bugs.
  • The approach prioritized speed and direct customer interaction over feature completeness.

Exceptions: "Heavy" MVPs

• Applicability: Heavy MVPs are sometimes necessary for highly regulated industries (insurance, banking), hard tech (rockets, biotech), or moonshot infrastructure (high-speed rail, subways).
• Strategy: In these sectors, the MVP may begin as a simple website to facilitate conversation while the complex build process proceeds.
• Outcome: A simple explanatory website can sometimes be developed faster than a functional software MVP for these complex problems.

Launch Philosophy

• Myth Busting: The concept of a high-profile "press launch" or massive buzz is largely a misconception; successful companies like Google did not have memorable launch days.
• Definition of Launch: A launch is effectively defined as the moment the first paying or active customer is acquired.
• Research vs. Reality: Theoretical research and pitch decks are less valuable than a tangible product that allows customers to test the solution.

Operational Hacks for Rapid MVP Development

• Timeboxing: Constrain the specification strictly to features buildable within a set timeframe (e.g., three weeks).
• Specification Writing: Document the initial plan in writing to prevent scope creep driven by anecdotal feedback from users or investors.
• Aggressive Cutting: If a deadline is missed, cut features regardless of importance; the primary objective is releasing something to the market to gain momentum.
• Emotional Detachment: Founders must not fall in love with the initial MVP, treating it as a rough draft rather than a final vision.