# Problem Validation

Evidence-based investigation of whether a meaningful problem exists for a defined group and is worth addressing.

- Type: practice
- Domain: Research & behavior
- Level: Intermediate
- Last reviewed: 2026-09-23
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/problem-validation/>)

## What it means

Problem validation tests the existence, frequency, severity, context, and consequences of a user or customer problem before a team commits to a solution. It distinguishes observed unmet needs from opinions, requests, or symptoms.

## Why it matters

Teams save delivery effort when they learn that a problem is rare, already solved, low priority, or misunderstood before designing a product response.

## When to use it

Use it early in discovery and whenever evidence for the problem is weak or conditions have changed. It is less useful when a mandatory obligation already establishes the problem but still cannot replace solution and risk analysis.

## How it works

1. Define the affected population and context.
2. Gather behavioral, qualitative, operational, and market evidence.
3. Look for frequency, severity, workarounds, and consequences.
4. Compare competing explanations and existing alternatives.
5. State what evidence is sufficient to pursue, narrow, or stop.

## A practical example

Before building a returns chatbot, a retailer studies contact reasons and observes agents, discovering that the main problem is unclear policy eligibility rather than lack of automated conversation.

## Where it breaks

Research samples and reported pain can be biased; a real problem does not guarantee willingness to switch, viable economics, or a feasible solution.

## Common mistakes

- Treating a feature request as problem evidence.
- Asking leading questions about a proposed solution.
- Generalizing from one loud customer.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/problem-validation/#visualization-problem-validation>)

## Sources

1. [Learning about users and their needs](<https://www.gov.uk/service-manual/user-research/start-by-learning-user-needs>) — GOV.UK Service Manual · Government service guidance
2. [How the discovery phase works](<https://www.gov.uk/service-manual/agile-delivery/how-the-discovery-phase-works>) — GOV.UK Service Manual · Government service guidance

## Related topics

- [Opportunity](<https://wiki.soroush.uk/topic/opportunity/>)
- [Solution Validation](<https://wiki.soroush.uk/topic/solution-validation/>)
- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
