Most unhappy design projects were decided before any work started. The brief was thin, the designer filled the gaps with assumptions, and the first draft revealed that the two parties had different projects in mind.
I write this as the person on the other side of it. A good brief makes my job easier and yours cheaper, and almost nobody has been taught what one contains.
What a brief is actually for
It is not a specification of what to make. If you could specify that, you would not need a designer.
It is a description of the problem, the constraints, and how you will judge success. The designer’s job is to propose solutions within those boundaries. If you supply the solution, you have hired an operator rather than a designer, and you will get what you asked for rather than what you needed.
That distinction matters because a common failure is a business owner arriving with a fully formed picture in their head and a brief that describes it incompletely, then being disappointed that the result does not match a picture nobody else could see.
What to include
What the thing is for. Not “we need a new logo.” What is the actual problem? Are you being underestimated by prospects? Do your materials look inconsistent? Did the business change? The underlying problem often points to a different solution than the one you came in asking for, and a good designer should tell you so.
Who it is for. Specifically. Not “everyone” and not “adults 25 to 65.” Describe an actual customer. What they worry about, what they are comparing you against, what would make them hesitate.
Where it will be used. Every application you can think of. A logo that works on a website and fails on a van is a solved problem if somebody mentions the van at the start, and an expensive rework if they mention it at the end.
What already exists and is fixed. Colours you cannot change, a name, a typeface used elsewhere, brand elements from a parent company. Constraints given up front are useful. Constraints revealed at revision three are costly.
Examples of things you like, with reasons. The reasons matter more than the examples. “I like this because it feels calm and uncluttered” is usable. “I like this” is not, because I cannot tell whether you mean the colour, the type, the photography or the layout.
Examples of things you dislike, with reasons. Equally valuable and more rarely supplied. Knowing what is out of bounds saves everybody a round.
The real deadline. Not a padded one. If the actual date is the trade show in six weeks, say so, because it changes what is sensible to attempt.
The budget. More on this below.
Who approves it. If there is a business partner or a spouse whose opinion will decide this, they need to be involved at the start rather than appearing at the end with a different view. This single item prevents more wasted work than anything else on the list.
Say the budget
Business owners often withhold budget believing it prevents being charged the maximum. What it actually does is make it impossible to propose the right scope.
The same brief can be a two week job or a three month one. Without a figure, a designer is guessing which project you are describing, and a guess wrong in either direction wastes the conversation.
You do not need to name an exact number. A range is enough. “We are thinking somewhere in this region, tell us what is realistic” is a productive sentence and it usually produces an honest answer about what fits.
What to leave out
Solutions. “Make the logo blue with a swoosh.” If you know exactly what you want, you want production, not design, and you should say so and pay accordingly.
Adjectives with no anchor. Modern, clean, professional, fresh, elegant. Everybody uses these words and no two people mean the same thing. Show me an example instead.
Design instructions you do not have a reason for. “Make it bigger” is a solution. “It is not standing out enough against the competitors’ signs” is a problem, and it might be solved by size, contrast, or position.
Giving feedback that helps
The revision round is where most projects go wrong, and it is fixable with one habit.
Describe the problem, not the fix. “It feels too corporate for us” gives me something to work with. “Change the font to Helvetica” does not, because if the fix does not work we are both stuck.
Be concrete about what is wrong. “I do not like it” is honest and unusable. “It looks like a law firm and we are a bike shop” is immediately actionable.
Consolidate. Collect all feedback, from everyone whose opinion matters, into one message. Drip feeding contradictory notes over four days produces confusion and costs hours.
Separate taste from function. “I personally prefer green” is different from “green will not read against our building.” Both are legitimate, and knowing which one you are expressing helps enormously.
Say what is working. Not politeness. If I do not know which parts you want kept, I risk changing them in the next round.
The realistic expectation
The first draft is a proposal, not an attempt at the final thing. It exists to establish direction. Reacting to it as a failed final version creates unnecessary tension in a normal process.
Two or three rounds is typical. More than that usually means the brief was unclear or the approvers were not aligned at the start.
Some things you ask for will get pushed back on. A designer who agrees to everything is not doing the job. If I think a request will hurt the result I should say so once, clearly, and then do what you decide.
The short version
If you write nothing else, write these five things:
What problem are we solving. Who is it for. Where will it be used. What is fixed and cannot change. Who signs it off.
That is a usable brief in five sentences and it prevents most of what goes wrong.
The projects that disappoint people are almost never failures of skill. They are failures of shared understanding, decided in the first conversation, and discovered three weeks later.
Supplying the raw material
One practical thing that delays projects more than anything else: the content.
A designer cannot finish a website without your words and your photographs. Not placeholder text and stock images, the real ones. Projects routinely stall for weeks at this point because both sides assumed the other was handling it.
Decide explicitly, before work starts, who is writing the copy and who is supplying photography. If it is you, block time for it, because it will take longer than you think. If it is them, it should be in the quote.
The same applies to logins, brand assets, and access to your domain and hosting. Gather them at the start. Hunting for a hosting password three weeks in is a genuinely common cause of delay.
What to ask before you sign
Five questions that prevent most disputes.
What exactly is delivered? File formats, how many variations, whether source files are included. “A logo” means different things to different people.
How many revision rounds are included, and what happens after? So nobody is surprised by an additional invoice.
Who owns the work when it is done? Should be you, on final payment. Get it in writing.
What is the timeline, and what does it depend on? Most timelines assume you respond within a few days. Say so if you cannot.
What happens if I want a change in six months? Rates, availability, whether they retain your files.
None of these are adversarial. A professional will have ready answers and will be glad you asked, because these are exactly the questions whose absence causes trouble later.
The relationship worth having
The best design outcomes I have been part of came from clients who treated it as a collaboration rather than a transaction.
That means being honest about budget, responsive with feedback, clear about who decides, and willing to be pushed back on occasionally. It also means expecting the same in return: honest advice about what will and will not work, including when that costs the designer a bigger project.
If you find somebody who tells you that you do not need what you came in asking for, keep them. That advice is worth more than the work you were about to buy.
Briefing for smaller jobs
Not every project needs the full treatment. If you are asking for a flyer, a social template or a single page, the brief can be four lines and still prevent most problems.
What is it for and who sees it. Where and how it gets used, including the finished size and whether it is printed or on screen. What has to be on it, listed. When you need it.
That is enough for a small job. The failure on small jobs is almost never an inadequate brief in the sense of being too short. It is a missing constraint that only surfaces at the end, usually the final dimensions or the fact that it needs to work in black and white.
State the boring practical constraints first. They are the ones that cause rework.
This article contains no statistics and no pricing claims. Where numbers appear elsewhere on this site, they are measured with free public tools or cited to a named source.









