Solution Validation
Evidence-based testing of whether a proposed solution helps target users and can satisfy important product constraints.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/solution-validation/
01What 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.[1][2]
- Problem foundation
- Defined users, context, need, and consequencesEvidence remains separate from reactions to the concept
- Solution evidence
- Observed comprehension, use, value, and frictionAlso test technical, operational, commercial, and accessibility constraints
Solution validation follows or accompanies problem understanding; it is not merely checking that software matches a specification.
02Why 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.
03When 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.
04How it works
- State the problem, target users, and solution hypothesis.
- Choose a realistic fidelity and test method.
- Observe behavior and capture comprehension, value, and friction.
- Check feasibility, viability, accessibility, and operational constraints.
- Decide whether to adapt, continue, or stop.
05A 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.
06Where 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.
07Sources
- 1. Understand users and their needsGOV.UK Service Manual · Government service standard1. Understand users and their needs
- ISO 9241-210:2019ISO · International standardISO 9241-210:2019