problem-solution-fit

Problem validation confirms a genuine customer pain point exists before building solutions. Use problem discovery techniques like Jobs-to-be-Done interviews to assess pain frequency and intensity, then rank problems by solvability and strategic fit to ensure you're solving high-value issues.

Solution hypothesis generation creates several competing approaches to the same problem, then evaluates each for technical feasibility, effort versus impact, and build/buy/partner trade-offs. This prevents premature commitment to a single solution and surfaces competitive advantages.

MVP definition isolates the absolute minimum feature set that solves the core customer problem, paired with clear success metrics and technical risk assessment. This approach avoids over-building and focuses development on validated problem-solution fit.

Yes. Problem-solution fit validation applies across discovery, definition, pivots, and product expansion stages. Re-validate customer problems and solution hypotheses before each pivot or expansion to confirm strategic fit in new contexts.

Alternative analysis catalogs how customers currently solve the problem through competing products or manual workarounds. This identifies unmet needs, reveals where your solution creates differentiation, and informs competitive positioning.

Validation produces a Validated Problem Stack Rank prioritizing which problems to solve, a Solution Hypothesis Evaluation comparing approaches, and clear decision criteria—solvability, strategic fit, and potential impact—to guide development investment.