# TOOL 06. THE MINIMUM CREDIBLE LAUNCH

**Use when:** A launch is approaching and the team cannot agree what must be ready.

## Understand

- [ ] A relevant visitor can explain what this is.
- [ ] The primary audience is visible.
- [ ] The problem and value are clear.
- [ ] The main offer is stronger than the feature list.
- [ ] Pricing or access logic is understandable.

## Believe

- [ ] The product or service can be seen meaningfully.
- [ ] Claims have appropriate proof.
- [ ] Team, process, institution or pilots establish credibility.
- [ ] Limitations are handled honestly.
- [ ] The visual and verbal expression feels complete enough to trust.

## Act

- [ ] One primary next step is obvious.
- [ ] The action works on real devices.
- [ ] Confirmation is clear.
- [ ] A named team owns what happens next.
- [ ] Tracking is live.

## Triage the backlog

| Item | Needed to understand | Needed to believe | Needed to act | Learn after launch | Decision |
|---|---:|---:|---:|---:|---|
|  |  |  |  |  | Launch / Later |
|  |  |  |  |  | Launch / Later |
|  |  |  |  |  | Launch / Later |

**Launch Fast scope:** ..........................................................

**Build Forward scope:** .........................................................

**First post-launch review date:** ...............................................