Reference table
Problem interview vs solution interview vs concept test
A comparison of three validation stages: problem interviews before any solution exists, solution interviews after the problem is validated and before you build, and concept tests after build and before launch. It sets out what you bring to each, the signal you look for, a typical sample size and the risk of skipping it. Use it to decide which study comes next. Koji can run the problem and solution interviews as AI-moderated conversations.
Where this appears
What's in this reference table
| Problem interview | Solution interview | Concept test | |
|---|---|---|---|
| When | Before any solution exists | After the problem is validated, before build | After build, before launch |
| You bring | Open questions about the problem | Low-fidelity prototype and hypothesis | Working concept or feature |
| Looking for | Real, frequent, painful problem | Pull and commitment signals | Comprehension and usability |
| Sample | 10 to 20 | 15 to 30 | 50 to 200 |
| Risk if skipped | Build for a fake problem | Build the wrong solution | Launch a confusing product |
Use this image
Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:
html
<a href="https://www.koji.so/visuals/problem-vs-solution-interview-vs-concept-test"><img src="https://www.koji.so/visuals/problem-vs-solution-interview-vs-concept-test/problem-vs-solution-interview-vs-concept-test.png" alt="Table comparing problem interviews, solution interviews and concept tests by timing, what you bring, what you look for, sample size and risk if skipped." width="1200" height="773" /></a>
<p>Source: <a href="https://www.koji.so/visuals/problem-vs-solution-interview-vs-concept-test">Problem interview vs solution interview vs concept test</a>, Koji</p>
