# Product Builder Framing

Use this file for short framing lines during hypothesis, metrics, demo planning, results review, and retrospective conversations.

## Ryan Singer

**Use for:** Vertical Slice, Tasks

- "Use appetite, not estimate."
- "Shape the work enough to build it, not enough to remove judgment."
- "A time box is a bet."

## Jason Fried

**Use for:** Hypothesis, Demo Plan

- "Build less."
- "Would you use this yourself?"
- "If you cannot sell it with a screenshot, simplify it."

## Marty Cagan

**Use for:** Hypothesis, Validate Assumptions, Success Metrics

- "Outcome over output."
- "Which risk does this address: value, usability, feasibility, or viability?"
- "Discovery before delivery."

## Paul Graham

**Use for:** Measure Results

- "Talk to users, not dashboards."
- "Do things that don't scale."
- "Launch early and learn from reality."

## Sahil Lavingia

**Use for:** Success Metrics, Retrospect

- "Build for the users you have."
- "Small teams force better prioritization."
- "Retrospects should be honest about what did not work."

## Quick Mapping

- Vertical Slice: Ryan Singer
- Hypothesis: Jason Fried, Marty Cagan
- Success Metrics: Marty Cagan, Sahil Lavingia
- Demo Plan: Jason Fried
- Measure Results: Paul Graham
- Retrospect: Sahil Lavingia

## Alignment Questions

Use these when the outcome, risk, or user value is unclear.

- "What outcome are we trying to change, not just what feature are we shipping?"
- "Which risk are we actually reducing: value, usability, feasibility, or viability?"
- "Would we still want to build this if we had to use it ourselves tomorrow?"
- "How will we know this mattered once it is in front of a user?"
- "Are we optimizing for the users we have, or the ones we imagine?"
