Design brief template: the eight questions that prevent rework

Most design briefs aren't too short — they're answering the wrong questions. This template has eight. They're ordered deliberately: each one only makes sense once the previous is answered.

The eight questions

1. What business outcome is this design buying?

Not "a new look." Pick something checkable: more trial signups, better shelf standout, fewer support tickets about the confusing checkout. If the client can't answer this, the project isn't ready to start — and you'll feel that in every round of feedback.

2. Who sees it, in what moment?

"Women 25–40" is demographics, not context. The useful answer is situational: scrolling a feed with sound off, comparing three boxes on a shelf, staring at a pricing page at 11pm. Design decisions change completely with context.

3. What must they feel in five seconds?

Trustworthy? Cheaper than the alternative? Premium? Choose one primary feeling. Two is a compromise; three is a mess.

4. What is the one thing it must communicate?

The equivalent of an ad's single-minded proposition. If the viewer remembers one thing, what is it? Write it as a sentence.

5. Where does it physically live?

List every real placement: the favicon, the van, the Instagram grid next to six other posts, the packaging on a shelf beside competitors. Screenshots of the actual environments are worth a thousand words of adjectives.

6. What are the genuine constraints?

Brand colours that can't move, print method, regulatory lines, the CMS the site must live in. Separate the real constraints from preferences dressed up as rules — designers will push back on the latter, and they're usually right to.

7. What does "done" look like, and by when?

Deliverable list, file formats, and the date. Plus the review checkpoints — when does the client see round one, and what specifically will they be judging at that point (direction, not polish)?

8. Who signs off, and who just comments?

Name the approver. One person, in writing. Everyone else gives feedback; only this person's "yes" counts. This single line prevents the classic death spiral where a stakeholder who never appeared in the process reopens round three.

Copy-paste skeleton

PROJECT:      [name]
OUTCOME:      [measurable business result]
AUDIENCE:     [who, in what moment]
FEELING:      [one primary feeling in 5 seconds]
ONE MESSAGE:  [the single sentence it must communicate]
PLACEMENTS:   [every real environment it appears in]
CONSTRAINTS:  [hard constraints only]
DEFINITION OF DONE: [deliverables, formats, dates]
APPROVER:     [one named person; everyone else advises]

Why question 8 changes everything

In our guide to client approval workflows, the pattern is consistent: rework isn't caused by bad design, it's caused by unowned approvals. When the approver is named in the brief, feedback consolidates. When it isn't, every stakeholder's opinion becomes a version.

That's exactly the gap CreativeBoard closes — the brief, every version and the named sign-off live in one object, so "which version was approved?" has one answer. It's built for small agencies and lean marketing teams, and early access is free: