Design Brief Template 1
Design brief: Problem [ ]; Audience [ ]; Objective [ ]; Evidence [ ]; Deliverables [ ]; Constraints [ ]; Out of scope [ ]; Success measure [ ]; Owner/approver [ ].
Start with structure, then replace every placeholder with information that is true, relevant, and natural for your context. These templates are intentionally skeletal so your final writing does not sound mass-produced.
A useful design brief aligns stakeholders before execution. It separates the underlying user or business problem from a predetermined visual solution, gives the designer concrete constraints and success criteria, and records who will approve what.
Design brief: Problem [ ]; Audience [ ]; Objective [ ]; Evidence [ ]; Deliverables [ ]; Constraints [ ]; Out of scope [ ]; Success measure [ ]; Owner/approver [ ].
Problem statement: [User] cannot [task] because [barrier], resulting in [cost/outcome]. The design should enable [desired behavior].
Constraint table: Requirement → [hard rule]; Source → [brand/legal/technical/user]; Consequence → [what design must account for].
Decision plan: Discovery review [date/owner]; concept review [ ]; validation [ ]; final approval [ ]; launch measurement [ ].
Source-ledger and revision-history audit for Design Brief: claim / recommendation / example → [ ]; source or project record ID → [ ]; source status active / superseded / corrected / retracted / retired → [ ]; claim-level last verified date/version → [ ]; event that triggered recheck → [ ]; correction / withdrawal action → [ ]; reader-facing disclosure needed? → [ ]; what changed and why → [ ]; prior wording/version retained at → [ ].
Claim/source status audit: Item [claim/source/example] | Status [active / review due / stale / corrected / retracted / superseded] | Controlling source/version [x] | Last verified [date/version] | Stale trigger [x] | Correction severity [0–3] | Reader disclosure [none / note / correction / withdrawal] | Changelog entry [what changed + why].
Dependency and propagation audit: Claim / example / recommendation [x] | Controlling source / project record [x] | Dependency strength [direct / shared / advisory / independent] | Review trigger / reason code [x] | Needs-review scope [local / direct dependents / cluster] | Replacement source requirements [x] | Carry-forward decision [x] | Propagation targets [x] | Reader disclosure / changelog action [x].
Persistent editorial registry audit: Topic slug → [ ]; claim UID/key → [ ]; source UID/key → [ ]; dependency UID + strength → [ ]; source status/version → [ ]; open review UID/reason/priority → [ ]; replacement source if any → [ ]; reviewer + resolution → [ ].