A concise document that frames the scope, objectives, constraints, and success criteria for a design project before work begins. A strong design brief is a contract of shared understanding — not a prescriptive solution — that gives designers enough direction to be effective without eliminating the creative space needed to find the best answer.
Common contexts
- Writing a brief at the start of a checkout redesign to align product, design, and engineering on success metrics
- Using a brief to formally document scope constraints before a sprint so stakeholder requests mid-sprint have a reference point
- Sharing a brief with a freelance designer to communicate the problem without prescribing the solution
Use when
Write a design brief before any project where more than two people need to agree on the direction — it forces the team to resolve scope, ownership, and success criteria as explicit decisions rather than informal assumptions. The act of writing it is as valuable as the document itself.
Avoid when
A design brief becomes counterproductive when it is written after the solution is already decided — a brief that documents conclusions rather than framing the problem is a justification document, not a design tool. If the solution is already prescribed, the brief is theater.
A design brief that everyone on the team interprets differently hasn't done its job — the real test of a brief isn't whether everyone signed off on it, but whether everyone made the same design decisions when working independently from it.
Real-world examples
- IDEO's project engagements begin with a co-created design brief developed alongside clients, documenting the problem statement, audience, constraints, and success criteria before any design work begins.
- Google's internal design teams use a one-page brief format that captures the user problem, business goal, and key metrics before a project enters the sprint cycle.
- The UK's Design Council publishes brief templates used in public-sector design challenges, ensuring teams define the problem space rather than jumping directly to solutions.