Problem-Solution Fit
Problem-solution fit is the point at which a team has evidence that a specific group of customers cares about a problem, and has designed a solution that credibly addresses it. Strategyzer describes it as the first of three kinds of fit, before product-market fit and business model fit. At this stage the solution often exists only on paper or as a prototype.
How Problem-Solution Fit Works
In Strategyzer's Value Proposition Design approach, fit is about matching two sides. On the customer side are the jobs people are trying to get done, the pains they experience, and the gains they want. On the product side are the pain relievers and gain creators your offer provides. Problem-solution fit means two things are true:
- You have evidence, not just belief, that customers care about particular jobs, pains, and gains.
- You have designed a value proposition that addresses the ones that matter most.
Evidence usually comes from customer interviews, observation, support and search data, and low-cost tests such as landing pages, mockups, or manual pilots. Behavior counts for more than opinion: customers describing recent attempts to solve the problem, spending time or money on workarounds, or committing to try something.
Teams rarely reach problem-solution fit in a single moment. They get there by testing their riskiest assumptions and revising both the problem framing and the proposed solution until the two line up.
Why Problem-Solution Fit Matters
It is the cheapest place to be wrong. Before problem-solution fit, a team can change its target customer, reframe the problem, or drop the idea at the cost of some interviews and sketches. After a full build, the same changes cost months.
Checking it first also helps teams avoid two common traps: solving a problem that is real but not important enough for people to act on, and building a good solution to a problem nobody prioritizes. A team that has evidence of problem-solution fit can give its minimum viable product a much sharper target. For a stage-by-stage view of testing assumptions before development, see how to validate a SaaS idea before you build it.
Problem-Solution Fit Example
A founder wants to build scheduling software for independent physiotherapy clinics. Interviews with clinic owners show that no-shows are their most painful issue: each missed appointment is lost revenue, and front-desk staff spend time phoning patients the day before. Several owners already pay for generic text-message tools and still chase confirmations by phone.
The founder designs a value proposition around automated two-way confirmations that fill cancelled slots from a waitlist. She shows mockups to clinic owners and asks for a paid pilot, and several agree. A validated, painful problem plus customers committing to a specific proposed solution is evidence of problem-solution fit. Whether the product keeps clinics paying once it is live and used at scale is a later question.
Problem-Solution Fit vs. Product-Market Fit
| Problem-solution fit | Product-market fit | |
|---|---|---|
| What is proven | Customers care about the problem, and the proposed solution addresses it | The product creates real value for customers in a market |
| Typical evidence | Interviews, prototype reactions, pre-commitments | Retention, usage, revenue, referrals |
| Product state | Often not yet built | Live, with real users |
Product-market fit requires a working product and market evidence such as retention. Problem-solution fit can be reached with a value proposition that has not been built yet.