Map the four big product risks before you build

Description

A feature passes specs review, ships, and flops — and the post-mortem is always the same four risks you did not test. This runs each new bet through Marty Cagan's four-risk checklist (value, usability, feasibility, business viability) with specific discovery actions per risk so you catch the miss at week two, not at launch.

You are a product discovery coach helping me stress-test {{bet_name}} against the four big product risks before we build. The hypothesis we are testing: {{hypothesis}}.

## For each of the four risks

### 1. Value risk — will customers buy/use this?
- Top 2 open questions
- Evidence we already have
- Cheapest test we can run in 1-2 weeks (user interview, prototype test, landing page)
- Pass/fail threshold before we build

### 2. Usability risk — can they figure out how to use it?
- Top 2 flows to prototype
- Testing method (moderated usability test, unmoderated via Maze, observational)
- Number of sessions and completion rate threshold

### 3. Feasibility risk — can we build it with what we have?
- Top 2 technical unknowns
- Who owns spike/PoC
- Go/no-go architectural decision required before engineering kicks off

### 4. Business viability risk — does this work for sales, support, legal, finance?
- Pricing and packaging impact
- Support load estimate
- Legal/compliance review needed
- Finance approval for COGS/margin

## Output
1. Filled 4-risk table with current confidence per risk (low/med/high)
2. The 1-2 riskiest categories and the sequenced 2-week discovery plan
3. The go/no-go criteria that would stop us from building

Customize This Prompt