Hard Problem MVP Scoping

Hard problem MVP scoping is the pattern of reducing a problem that looks too large for a startup into a narrow first demonstration that can create learning, credibility, and investor belief. In Kyle Vogt on Justin.tv, Twitch, Cruise, and Choosing Hard Problems, Kyle Vogt applies this to Cruise after seeing Google’s self-driving work and asking whether a lean startup version could exist.

The early Cruise wedge was not a full robotaxi. It was a retrofitted Audi with sensors and a highway lane-keeping button, narrow enough to build and demo while still pointing at a much larger autonomy market. The source therefore extends Janky MVP beyond software and marketplaces: a hard-tech MVP may validate engineering feasibility and narrative credibility before it validates a complete business model.

Key Claims

• A hard problem can become startup-sized only after the first version removes most of the domain and preserves one decisive learning question.
• The first wedge has to be technically credible enough to change the conversation, not merely a mockup or pitch artifact.
• The wedge can help fundraising by giving investors a concrete de-risking path, but it does not remove later capital, safety, regulatory, and scaling risk.
• Hard problem MVPs often need later pivots when the first product shape exposes liability, customer, or market-structure problems.

Connections

• Cruise and Kyle Vogt - source case.
• Janky MVP, Fast Product Validation, and Validated Learning - adjacent startup-learning concepts.
• Hard Tech Fundraising, Robotaxi Economics, and Autonomous Vehicle Safety Benchmark - constraints that appear after the first wedge.