Product requirements brief template
By Kivrelune Studio

Product requirements brief
Align a team on the problem, required behavior and evidence of success before development.
Problem and goal
For [user], [situation] makes [task] difficult. Evidence: [observations]. Desired result: [measure and target]. Exclude [adjacent problem] from this release.
Requirements
Requirement [ID]: when [condition], the user can [behavior]. Priority: [level]. Acceptance evidence: [observable example]. Identify accessibility, reliability or permission constraints that affect the user.
Open decisions
Unresolved question: [question]. Owner and deadline: [details]. Dependencies: [teams]. Approval means [requirements baseline], with changes logged at [location].
Using this template
Start with the user problem and agree on a measurable outcome before committing to requirements. Write each requirement as observable behavior, capture the necessary constraints and give unresolved decisions owners before the development team accepts the baseline.
Questions & answers
Looking for more help? Visit the Help center.
How do we keep a requirement independent of a favored solution?
Describe what the user needs to accomplish and what evidence will demonstrate success. Record an implementation choice separately unless the choice itself is a genuine constraint.
What is included in this template?
Problem and goal · Requirements · Open decisions. Each section includes prompts you can adapt to your team.
How do we handle a change in scope?
Record the new evidence, identify the affected decision and name the person who will settle it. Keep the previous reasoning available to the next reader.
How do I use my own copy?
Choose “Start with this doc” to open an editable copy on this device. You can also copy the Markdown or download the file and use it in your own editor.


