Problem Validation Test

1/10. Define the problem hypothesis clearly.

A precise hypothesis focuses validation efforts. This sets clear testing parameters.

Sub-actions:

1.1 Write a one-sentence problem statement

1.2 List assumed causes and impacts

1.3 Share with team for alignment

Pitfalls:

Vague hypotheses lead to scattered testing.
No sharing causes misalignment.

2/10. Identify target user personas.

Detailed personas ensure testing with the right people. This improves insight relevance.

Sub-actions:

2.1 Create 2-3 personas based on demographics, behaviors, and pain points

2.2 Validate if the problem affects them significantly

Pitfalls:

Generic personas yield broad, useless data.
Wrong personas validate false problems.

3/10. Recruit 20-30 participants matching personas.

Sufficient sample size provides reliable data. This reduces individual bias impact.

Sub-actions:

3.1 Use neutral channels like ads or forums

3.2 Screen for fit with survey

Pitfalls:

Too few participants make findings anecdotal.
Biased recruitment confirms assumptions.

4/10. Conduct problem-focused interviews.

Open discussions reveal if the problem resonates. This uncovers nuances.

Sub-actions:

4.1 Ask about past experiences

4.2 Probe for frequency and severity

Pitfalls:

Solution talk biases responses.
Shallow probing misses depth.

5/10. Run quantitative surveys.

Surveys provide measurable validation. This complements qualitative insights.

Sub-actions:

5.1 Ask ranking and rating questions

5.2 Target 100+ responses

Pitfalls:

Poor questions yield garbage data.
Low responses limit statistical power.

6/10. Observe user behavior if possible.

Direct observation shows real actions. This validates beyond self-reports.

Sub-actions:

6.1 Use usability tests or shadowing

6.2 Note workarounds

Pitfalls:

No observation misses behavioral truths.
Hawthorne effect alters behavior.

7/10. Analyze competitor solutions.

Reviewing alternatives shows market validation. This reveals gaps or saturations.

Sub-actions:

7.1 Review competitor websites, reviews, and forums

7.2 Note gaps in their solutions

Pitfalls:

Ignoring competitors leads to reinvention.
Copying misses differentiation.

8/10. Analyze data for validation thresholds.

Objective criteria determine problem validity. This enables clear decisions.

Sub-actions:

8.1 Calculate percentages for key metrics

8.2 Document if thresholds met

Pitfalls:

No thresholds make validation subjective.
Cherry-picking data misleads.

9/10. Synthesize findings into a report.

A comprehensive report communicates results. This informs stakeholders.

Sub-actions:

9.1 Include quotes, metrics, and conclusions

9.2 Share with stakeholders

Pitfalls:

Incomplete reports lose credibility.
No sharing limits impact.

10/10. Decide on next actions based on validation.

Clear decisions guide resource allocation. This prevents sunk cost fallacies.

Sub-actions:

10.1 If validated, move to solution ideation

10.2 If not, pivot or abandon

Pitfalls:

Proceeding without validation wastes time.
Abandoning too soon misses opportunities.

Problem Validation
Test

This test confirms if a suspected problem is real and worth solving. Rigorous validation prevents building solutions for non-existent issues.

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

Sub-actions:

Pitfalls:

How to Use

Expected Outcomes