A project brief should answer one question: what does success look like for this project? Too many briefs fail because they are long, vague, or written in design jargon. Clients skim them, designers guess at them, and the project drifts. A useful brief is short enough to read in one sitting, specific enough to guide decisions, and written in plain language that a non-designer can follow.
Ask Questions That Reveal Decisions
Start with the purpose of the project, not with colours or layouts. Ask what the website or brand must help people do, who it is for, and how the client will judge whether it worked. Ask what already exists, what must stay, and what has caused problems in the past. These questions surface decisions that would otherwise appear halfway through the project, when changes are expensive.
Keep the question list short. Ten focused questions beat thirty generic ones. If a client struggles to answer, offer simple options rather than leaving a blank box. For example, ask whether the main goal is enquiries, sales, bookings, or information, and let them pick one primary goal. It also strengthens writing proposals that win design work, because a brief built on real answers makes a proposal far more persuasive.
Turn Answers into a Short, Usable Document
Structure the brief around a few headings: goal, audience, scope, content, timeline, and success measures. Under each heading, write two or three sentences at most. Name what is included and, just as importantly, what is not included. List the content the client must supply, and the date it is needed, because missing content is one of the most common causes of delay. Share the brief and ask the client to confirm it in writing before design begins.
Use plain words for deliverables. Instead of promising a vague concept phase, say how many design directions will be shown, in what format, and how feedback will be collected. Avoid jargon that clients must translate. If a term matters, explain it in one line. A brief that clients actually read is one they can picture: they can see what they will receive, when they will see it, and what they need to do. Clarity at this stage saves hours of revision later.
Keep the Brief Alive
A brief should not be forgotten once work starts. If the project changes, update the brief and note the change, the reason, and any effect on time or cost. This habit protects both sides. It also helps with building a steady client pipeline, because a clear brief makes it easier to estimate future work and to explain your process to the next client.