mediumConceptScenarioMidSenior
How do you know a problem is real before you build anything to solve it?
5 min readUpdated 2026-08-15
Answer
Short answer
You look for evidence of the behaviour, not enthusiasm for your idea: interviews about past specific episodes rather than hypothetical futures, triangulated against what usage data, support tickets and lost deals show people already do.
Was this answer helpful?
Likely follow-ups
- You have eight interviews and six say the problem is painful. How much does that move you?
- How would you find people to talk to when the product does not exist yet?
- What do you do when sales insists three accounts need this and research says otherwise?
- Which of your assumptions would you test with a fake door rather than a conversation?
Related questions
- Your A/B test came back not significant. What do you do next?hardAlso on assumption-testing and discovery5 min
- A churn model scores 0.94 AUC offline and barely beats the baseline in production. One of its strongest features is populated by a process that runs after the customer has already churned. Explain what happened and how you would fix it.mediumAlso on validation5 min
- This form marks invalid fields with red text and a red border. What has to change?mediumAlso on validation4 min
- Your endpoint takes a typed request body and it still crashed on a missing field. How is that possible when it compiled?mediumAlso on validation4 min