Writing business requirements
Purpose: Define what you need to measure.
Who this page is for
| Audience | Why it matters to you |
|---|---|
| Product managers | Drive the conversation |
| Analysts | Translate to metrics |
Writing Business Requirements
Good requirements make everything downstream easier.
What makes a good requirement?
Clear:
- "Measure complaint form submissions"
- Not: "Track the form"
Measurable:
- "Count unique visitors who complete form"
- Not: "Track form usage"
Actionable:
- "Know drop-off rate by step"
- Not: "Understand the form"
Scoped:
- "Mobile visitors only"
- Not: "All traffic"
Requirement template
Business Question:
"How many members submit a complaint?"
Success Metric:
- Count: Form submissions
- Dimension: Form type (contact vs complaint)
- Segment: Device type
Decision Impact:
If complaint volume > 5% of visitors, prioritize form UX
Deadline: Q4 2026---
Next: The measurement plan