Map and test product assumptions

Surface and prioritize untested assumptions before development

Pre-build validation when a plan has multiple untested bets and you need to decide what to test first.

• · Product brief, PRD, or concept description
• · Stage (concept/discovery/pre-build/post-launch)

• · Assumption map across 4 categories (Desirability, Feasibility, Viability, Usability)
• · Ranked list with confidence and impact scores
• · Specific validation methods for each assumption
• · Top 3 assumptions to validate first

• · Brief or PRD provided (even rough notes work)
• · Awareness of product stage (affects which assumptions matter most)

• · Assumptions are too vague (e.g., 'users want this')
• · Missing entire category (no desirability or feasibility assumptions)
• · Validation methods are generic ('do research') not specific
• · Priority scoring inconsistent (not using Impact - Confidence formula)
• · Critical assumptions not flagged

• · Priority formula explicit (Impact - Confidence, higher = test first)
• · At least one assumption per DFRV category
• · All Impact 4+/Confidence 2- assumptions flagged as CRITICAL
• · Validation methods specific (sample size, method name, what result changes)
• · Example table provided with scoring logic