Risk & Assumptions Mapping
5 min readLesson 1 of 3
Risk & Assumptions Mapping
Every solution is built on a mountain of unstated assumptions. If any of these assumptions are wrong, your solution will fail. Solution Validation is the process of testing these assumptions before building the final product.
The Four Categories of Risk
Marty Cagan, author of Inspired, categorizes product risks into four buckets:
- Value Risk: Will customers buy it or choose to use it?
- Usability Risk: Can users figure out how to use it?
- Feasibility Risk: Can we build it with the time, technology, and skills we have?
- Business Viability Risk: Does this solution work for our business (legal, financial, compliance, brand)?
The Assumptions Mapping Grid
To prioritize what to test, map your assumptions on a 2x2 grid:
- X-axis (Evidence): Known (lots of evidence) vs. Unknown (no evidence).
- Y-axis (Importance): Critical (business fails if wrong) vs. Marginal (nice-to-know).
Focus your validation experiments exclusively on the Critical + Unknown quadrant. These are your "Leap-of-Faith Assumptions" (LOFAs).
Interactive Assumptions Mapping Grid
Mapped Risks (3)
Users are willing to pay $10/month
ValueImp: 9 | Ev: 2
API response will be under 200ms
FeasibilityImp: 5 | Ev: 8
Users can complete checkout in under 30s
UsabilityImp: 7 | Ev: 4
Leap-of-Faith (Test First)
Safe (Build / Scale)
Defer / Monitor
Ignore / Archive
V
F
U
← Unknown (No Evidence)EvidenceKnown (Has Evidence) →
Vertical axis: Importance (Top: Critical, Bottom: Marginal)