Library / discover STAGE

Build Evidence Before Features: The Problem Discovery Playbook

Why the biggest risk in early-stage startups is not technical feasibility, but building something nobody wants. How to systematically gather customer evidence before touching a codebase.

7 min read Article

The single most expensive error an early-stage team can make is shipping software that solves an unverified problem. When code is written prematurely, founders fall in love with their solution rather than the customer’s pain.

The Evidence Hierarchy

Before prioritizing a single roadmap feature, establish evidence across three vectors:

  • Problem Intensity: Is this friction causing acute pain, financial loss, or wasted hours weekly?
  • Existing Workarounds: How are users solving this today? If they aren’t actively seeking a workaround, the problem is not urgent enough.
  • Willingness to Commit: Are customers willing to exchange time, data, or money before the product is built?

Curiosity Over Certainty

Great founders do not enter customer interviews to validate their brilliant idea. They enter with genuine curiosity to uncover how their mental model is flawed.

Related in Discover