A bad brief costs more than a bad designer
Every senior designer has the same scar tissue: a project that ran four weeks late, ate three rounds of revision, and ended in a result the client wasn't excited about — even though every individual deliverable was technically correct. Almost every time, the post-mortem traces back to the brief. The designer was solving the wrong problem from day one because the brief never made the right problem visible.
A good brief is not long. The best ones we have ever received fit on a single page. What makes them good is not the volume of information but the precision of it. The brief should let the designer skip the parts where they would have to guess.
The seven-question template
We send this template to every new client before kickoff. The questions are designed to surface assumptions early, not to produce a polished document. Bullet points are fine. Voice notes are fine. The quality of the answers matters; the quality of the formatting does not.
1. What outcome are you trying to create, and how will you know it worked? This is the single most important question. "More signups" is too vague. "Convert paid traffic from our LinkedIn campaign at over 3 percent on the new pricing page" is something a designer can solve. Outcome plus a measurement equals a brief that has a finish line.
2. Who is the audience, in one paragraph? Not a persona deck — a single paragraph. We need to know what they already believe, what they're suspicious of, what alternatives they're considering, and what they would say if a friend asked them what your product does.
3. What does success look like aesthetically? Three to five reference links — competitors, sites you envy, brands you admire across categories. We are not going to copy them, but we want to triangulate the aesthetic neighborhood you live in.
4. What does failure look like aesthetically? Equally important. "Anything that looks like a 2018 SaaS site." "Nothing pastel." "We hate skeumorphism." The negative space is often more useful than the positive one.
5. What is the constraint you are most embarrassed to mention? This is the gold question. The answer is usually a deadline, a stakeholder, a budget, or a previous failed attempt. Whatever you bury here will surface in week three and blow up the timeline. Surface it now.
6. Who has to approve, and what do they care about? A design that ships requires sign-off from the people who can stop it. Tell us their names and their priorities. If the CFO will kill anything that looks too "expensive", we need to know in week one, not week four.
7. What does the next six months look like? Are you raising? Launching a new market? Hiring a CMO? The work we ship today is going to be lived in by your team for the next half-year, and decisions like "build a system" vs. "ship a one-off" depend entirely on this answer.
Anti-patterns that quietly waste weeks
There are five briefing patterns that look fine but produce projects that never quite land. Watch for them.
The committee brief. Five stakeholders co-authored the document, every sentence is a compromise, and no single person owns it. Designers can feel this immediately — every direction we propose gets a different objection from a different person. Pick one DRI for the brief, even if many people contribute. Without one, you are paying for a project to manage internal politics, not to design.
The "you're the experts" brief. It sounds generous but it puts the entire interpretive burden on us. We are experts, but we are not experts in your business. The best briefs combine our craft expertise with your domain expertise. Hand off too little context and the work becomes guesswork.
The pinterest brief. Forty references with no commentary. We don't know what you like about each one. Are you here for the typography? The layout? The vibe? Two annotated references beat forty silent ones.
The deferred brief. "We'll figure it out as we go." The result is always the same: heavy revisions, missed deadlines, and a final product that everyone agrees is fine. Defining the brief is hard, and most teams underestimate how much time it should take. Two days of brief writing saves four weeks of design rework.
The "we already started" brief. A previous designer or in-house team has produced 60% of the work and now wants us to "polish it". Almost always, the framework is broken in subtle ways and we end up restarting from scratch — but with the awkward politics of having to argue against the existing direction. If you bring previous work, bring it with the explicit understanding that we may need to start over.
What a great brief looks like
A great brief leaves the designer with one clear question: how. Not what, not why, not who — just how. When the designer reads the brief and immediately starts sketching, you have done your job. When they spend a week on follow-up calls trying to understand what you actually want, the brief was incomplete and you are paying for that gap with their time.
Briefing is a craft. It deserves more respect than it gets. The ten or twenty hours you spend writing a precise brief are the highest-leverage hours in the entire project — they make every later hour from the design team count two or three times over. Bad briefs are expensive long after they're written.