What is a problem interview?
A problem interview tests whether a problem is real, frequent, and painful enough to act on, and it happens before any solution is described.
A solution interview, by contrast, tests whether your specific proposed answer addresses that problem.
The distinction comes from lean startup practice. The two have opposite rules. In a problem interview you must not describe what you're building, because doing so gives the participant a frame to be polite about. In a solution interview you must, because the whole point is their reaction to it.
Why it matters
Combining them is the most common interview mistake. Once the participant knows what you want to hear, everything they say about the problem is shaped by it, and you leave with what feels like validation for a problem you may have just described into existence.
Example
Problem interview: "How do you handle this today?" Solution interview: "Here's a prototype. Show me how you'd complete this task." The first should happen across a dozen people before the second happens with anyone.
In UpSight
Both go into the same evidence base. A project in UpSight has an interview mode (exploratory, validation, or user testing), and there is a User Testing lens for the solution side next to the Customer Discovery lens for the problem side. There is no per-interview "problem" or "solution" tag yet. If you run both kinds in one project, the lens you apply is what tells them apart.
Related terms
FAQ
- Can you run a problem and solution interview in the same session?
- You can, but sequence matters absolutely: all problem questions first, and once the solution is shown, you cannot go back to unbiased problem questions.
- How many problem interviews before moving to solution?
- Enough that the problem's shape repeats across unrelated people, commonly 10 to 15 within one segment.
- What if they love the problem but hate the solution?
- That's a good outcome and a cheap one. The expensive version is finding out after you built it.