Design Brief: Project name
Design brief – objective, constraints, mood
How to use: Briefing designers (internal or agency). "Anti-references" save a full revision round.
Preview
Design Brief: Project name
| Field | Value |
|---|---|
| Client / product | Name |
| Designer | @name |
| Date | YYYY-MM-DD |
| Deliverable due | YYYY-MM-DD |
Objective
One sentence: what this design must achieve – a business outcome, not a style preference.
Audience
Who experiences this design – personas, context of use, constraints (accessibility level, devices, literacy).
Scope
In scope
- Deliverable one (format, sizes)
- Deliverable two
Out of scope
- Explicit exclusions
Requirements
- Must: hard requirement
- Must: hard requirement
- Should: soft requirement
- Must not: banned approach
Brand & constraints
- Palette / type / voice references
- Technical constraints (file size, formats, dark mode)
- Accessibility target (WCAG level)
References & mood
- Link to inspiration with note on what specifically is liked
- Anti-references: what to avoid
Success criteria
How we will judge the design: stakeholder sign-off, test metric, review rubric.
Process
| Milestone | Date | Output |
|---|---|---|
| Concepts | YYYY-MM-DD | N directions |
| Review | YYYY-MM-DD | Selected direction |
| Final | YYYY-MM-DD | Deliverables |