top of page
What’s inside
- TL;DR. Three sentences: what it is, who it is for, why now.
- Problem and users. The user problem, not the feature, and who hits it in what context.
- Success criteria and scope. Measurable targets, including the threshold that means it did not work, and an explicit out-of-scope list.
- Requirements. Numbered, testable REQ lines, plus open questions with owners and dates.
- Constraints and rollout. Technical, legal and business limits, and how the change reaches users.
How to use it
- Write the TL;DR last and put it first.
- State the problem before any solution, with evidence.
- Fill Out of scope as carefully as In scope.
- Make every requirement testable, atomic and necessary.
- Give every open question an owner and a date.
bottom of page