Skip to content

Problem-Solution Fit

The lean-startup gate that demands cheap, need-side evidence — a real, important problem for an identified user, and a solution preferred over their current workaround — before committing to build at scale, guarding against 'build it and they will come.'

Core Idea

Problem-solution fit is the lean-startup milestone at which a team has gathered evidence — through customer interviews and cheap prototype tests — that a proposed solution addresses a real, important problem for an identified user, before committing to build at scale. Its structural commitment is that the gate before scaling is need-side, not supply-side: the goal is to kill bad hypotheses cheaply, guarding against "build it and they will come."

Scope of Application

Lives within the lean-startup and product-and-innovation methodology family.

  • Lean startup / customer development — the origin: Blank's customer-development cycle and Ries's lean loop.
  • Product-discovery practice — Cagan's discovery and Torres's opportunity-solution trees.
  • Seed-stage venture and angel due diligence — asking for fit evidence before product-market-fit evidence.
  • Corporate-innovation stage-gates — Amazon's Working Backwards embedding a need-validation gate.
  • Social enterprise and human-centered design — IDEO-style need-validation before a social product is built.

Clarity

Naming problem-solution fit makes the order of validation legible and separates two questions a founder collapses: is there a problem worth solving, and will a viable market adopt this? It localizes a breakdown as upstream (no validated problem) or downstream (no scalable market), and it sharpens engineering quality versus demand — so "we shipped it and it works" is no longer an answer to "have you validated the need?"

Manages Complexity

A founder faces an overwhelming space of features, channels, pricing, and pivots entangled with sizing and competition. Problem-solution fit rules that before scaling only the need side is decisive, and reduces it to three ordered checks: does the problem exist, does it matter enough to act on, is the solution preferred over the current workaround? Market-size and pricing questions are deferred downstream, leaving a short checklist and a defensible default of no.

Abstract Reasoning

The concept licenses a diagnostic move (read demand from what the user already does — a workaround is the signature of a real problem — not from stated enthusiasm), an interventionist move (raise the cost of a fake yes with concierge MVPs and pre-sales, and withhold any build not tracing to a validated problem), boundary-drawing (which gate is this, and is small-n qualitative the right instrument), and an order-of-events prediction (out-of-order investment is wasted).

Knowledge Transfer

Across the lean-startup and product-discovery family, problem-solution fit transfers as mechanism with only the setting swapped — the gate, the qualitative small-n test, and the workaround-as-signature heuristic carry from customer development through venture due diligence to corporate stage-gates. For distant domains the named milestone does not travel; its content factors cleanly into substrate-general parents — validation, sequenced stage-gate logic, and user-centered design — which carry the "validate the need before building" lesson everywhere. The customer-development apparatus stays home as domain accent.

Relationships to Other Abstractions

Local relationship map for Problem-Solution FitParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Problem-Solution FitDOMAINDomain-specific abstraction: Smoke Test — is part of, conditionalSmoke TestDOMAINPrime abstraction: Validation — is a decomposition ofValidationPRIME

Current abstraction Problem-Solution Fit Domain-specific

Parents (2) — more general patterns this builds on

  • Problem-Solution Fit is part of, conditional Smoke Test Domain-specific

    A fake door, pre-order, or landing-page Smoke Test can be one cheap need-side instrument inside a Problem–Solution Fit gate before the product is built.

  • Problem-Solution Fit is a decomposition of Validation Prime

    The milestone asks whether the proposed remedy solves the intended user's real, important problem in context, not merely whether the team can build it correctly.

Hierarchy paths (6) — routes to 6 parentless roots

Neighborhood in Abstraction Space

Problem-Solution Fit sits in a sparse region of the domain-specific corpus (65th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Lean Validation & Startup Signal Theater (8 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12