/euxlab-design-brief
Insights into the design assignment, agreed before the first frame exists.
When you reach for it
Synthesis is done and someone is about to start designing. This is the red test of the loop: everything before it produces understanding, this produces the assignment design gets measured against, and the assignment is agreed with the stakeholder first.
Input, output, writes
- Input
- Cited insights from `research/insights/`, the personas, and a stakeholder willing to sign.
- Output
- One file a designer can start from: scope, requirements, the insight IDs each requirement serves, and the observable with today’s number.
- Writes
- docs/design-brief.md
Completion criterion
Every requirement is solution-free, carries at least one insight ID that resolves to a file in research/insights/, and states an observable with a baseline or a stated way to get one. Every persona named in a requirement exists in research/personas/. The out-of-scope section is not empty. The tracing section tells the designer to label every screen with its insight ID. The stakeholder has confirmed the brief with a name and a date. A requirement whose observable cannot be checked is sent back, not carried forward.
Checkable, and demanding. A skill that cannot say whether it is finished is a prompt.
Anti-patterns
- A requirement that names the solution. If only one design could satisfy it, it is a spec.
- An observable written as an adjective. "Faster" is not a number.
- No cut list. If nothing was cut, nothing was decided.