principleStrategy & discovery

Problem-Solution Fit

Early evidence that a specific customer problem matters and that a proposed value proposition plausibly addresses it better than relevant alternatives.

Download Markdown (.md)

01What it means

Problem-solution fit is an early learning milestone: a team has credible evidence that a defined group experiences an important job, pain, or unmet need and that a proposed solution direction could address it. It precedes product-market fit because the value proposition may still exist mainly as concepts, prototypes, concierge services, or limited experiments rather than repeatable market behavior.[1][2]

Problem evidence connected to a plausible response Show that an important need exists before claiming repeatable market traction
  1. 01Defined segment + contextJobs, pains, behavior, alternatives
  2. 02Problem evidenceObservation, interviews, support, market signals
  3. 03Value propositionProposed response to jobs, pains, gains
  4. 04Risk testsPrototype, simulation, concierge, commitment
  5. 05Revise fit hypothesisChange problem, segment, or solution direction

Problem–solution fit precedes product–market fit; prototypes, concierge services, and limited experiments may supply the evidence.

02Why it matters

Teams often fall in love with a solution before confirming that the underlying problem is real, frequent, severe, and worth changing behavior for. Testing problem-solution fit reduces premature building, exposes weak assumptions, and gives later product experiments a clearer target.

03When to use it

Seek it when exploring a new product, customer segment, workflow, or substantial solution direction. Return to the problem when tests show weak engagement, when customers solve a different problem than expected, or when market conditions change the importance of the need.

04How it works

  1. Define the customer segment, context, problem, current behavior, and existing alternatives.
  2. Gather evidence from observed behavior, interviews, support data, market signals, and domain experts.
  3. Separate the problem evidence from opinions about a preferred solution.
  4. Describe a value proposition that connects customer jobs, pains, and gains to a proposed response.
  5. Test the riskiest assumptions with prototypes, simulations, concierge delivery, or commitment signals.
  6. Revise the problem framing, segment, or solution direction when evidence contradicts the hypothesis.

05A practical example

Example

A team assumes restaurant managers need an AI demand forecast. Interviews and shift observations show that the costly problem is not prediction accuracy but late supplier substitutions. A manual alert prototype helps managers act earlier, and several agree to pilot it. The evidence supports a narrower problem-solution direction, not yet a scalable product or market fit claim.

06Where it breaks

The term has no single industry-wide test. Interview interest can overstate real demand, and a persuasive prototype may hide delivery cost, usability, compliance, or adoption barriers. Even strong problem-solution evidence does not prove retention, scalable acquisition, defensibility, or a viable business model.

Common mistakes

  • Asking whether customers like an idea instead of investigating real behavior and alternatives.
  • Changing the target problem to rationalize a solution already selected.
  • Calling early problem evidence product-market fit before customers repeatedly receive value.

07Sources

  1. Survival of the FittestStrategyzer · Creator-authored framework articleSurvival of the Fittest
  2. Achieve Product-Market Fit with the Value Proposition CanvasStrategyzer · Creator-authored method guideAchieve Product-Market Fit with the Value Proposition Canvas
View saved topics

Start typing to search titles, definitions, categories, and frameworks.