# Solution Validation

Evidence-based testing of whether a proposed solution helps target users and can satisfy important product constraints.

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

## What it means

Solution validation investigates whether a proposed experience, capability, or service solves a real need well enough for people to use it and for the product to sustain it. It follows or accompanies problem understanding and does not mean checking only whether software matches a specification.

## Why it matters

Validating a solution before scaling delivery reduces the risk of building something technically correct that users cannot understand, do not value, or cannot adopt.

## When to use it

Use prototypes, usability studies, pilots, technical spikes, or market tests when solution uncertainty is material. Use lighter validation for low-risk, reversible changes.

## How it works

1. State the problem, target users, and solution hypothesis.
2. Choose a realistic fidelity and test method.
3. Observe behavior and capture comprehension, value, and friction.
4. Check feasibility, viability, accessibility, and operational constraints.
5. Decide whether to adapt, continue, or stop.

## A practical example

A budgeting team tests a clickable recurring-expense flow with customers and support staff, finding that the proposed category model fails for irregular income before implementation.

## Where it breaks

Prototype behavior is not the same as sustained use, and positive usability cannot establish business viability or long-term retention.

## Common mistakes

- Testing opinions instead of behavior.
- Validating a polished interface with only friendly participants.
- Skipping the underlying problem because the solution looks plausible.

## Visualization

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

## Sources

1. [1\. Understand users and their needs](<https://www.gov.uk/service-manual/service-standard/point-1-understand-user-needs>) — GOV.UK Service Manual · Government service standard
2. [ISO 9241-210:2019](<https://www.iso.org/standard/77520.html>) — ISO · International standard

## Related topics

- [Problem Validation](<https://wiki.soroush.uk/topic/problem-validation/>)
- [Usability Testing](<https://wiki.soroush.uk/topic/usability-testing/>)
- [Product Hypothesis](<https://wiki.soroush.uk/topic/product-hypothesis/>)
