Product requirements

• Translating discovery into implementation-ready scope.
• Aligning engineering and design on what must be true at launch.
• Reviewing tradeoffs before development starts.

Strong requirements reduce rework, avoid scope churn, and make handoffs faster across product, design, and engineering.

Capture requirements in user-facing terms first, then add constraints, non-goals, and measurable outcomes. Link each requirement to a problem statement or decision.

Requirement: users can resume onboarding from the last completed step within 30 days with no data loss.

• Writing technical implementation details as user requirements.
• Missing non-goals, creating endless scope expansion.
• Not tying requirements to measurable outcomes.