Define exactly what you're building before you open any tool. A team that builds without a blueprint wastes hours. Fill this in together — it takes 20 minutes and saves you 2 hours.
⏱ 20 min
👥 Whole team
📐 Do this BEFORE touching any tool
🎯 Outcome: clarity on what to build
Step 1 — The 3 Non-Negotiable Questions
👤 Who is the ONE user?
Give them a name. One specific person, not a segment.
🎯 What is the ONE problem?
The single most painful moment in their day. From your W2 test results.
⚡ What is the ONE core action your MVP enables?
If your user can do only ONE thing in your MVP, what is it?
Step 2 — Success Definition
How will you know the MVP works?
Write one measurable signal. Before you build, define what 'success' looks like today.
Step 3 — The Feature Boundary
✅ MUST HAVE — Version 1.0
Without this, the MVP doesn't work.
💛 NICE TO HAVE — Version 1.1
Improves experience but not essential for testing.
❌ CUT IT — Not now
Ideas that will distract you. Write them here so you don't forget them.