Problem-to-outcome project brief template
By Kivrelune Studio

Problem-to-outcome project brief
Give a small product project a precise problem, a user scenario and a success test.
Problem framing
Who experiences [friction], in what moment? [recent case]. Why address it now? [cost or opportunity]. What is already known and what is still assumed?
User scenario
Today [user] does [action] and hits [problem]. After the change, they can [result]. Describe the smallest version worth testing and one explicit exclusion.
Evidence of success
Target [behavioral signal] from [baseline] to [target]. Validate with [test or feedback]. Project lead: [name]. Review after [period].
Using this template
Anchor the brief in a recent example of a user problem and describe the smallest project that could change that experience. Use the success signal and explicit exclusion to keep first-round planning focused on a testable outcome.
Questions & answers
Looking for more help? Visit the Help center.
What should we do when the smallest useful version is unclear?
Write the first moment at which a user receives value, then work backward to its prerequisites. Test that slice against the original scenario with a representative user.
What is included in this template?
Problem framing · User scenario · Evidence of success. Each section includes prompts you can adapt to your team.
How can the project team keep this current?
Give each open decision an owner and a due date. At the next checkpoint, update the milestone and record the work that changed since the last review.
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.
