When a first draft misses the mark, the cause is usually a guess. The designer had a gap in the information, filled it with a reasonable assumption, and the assumption turned out to be wrong. When you work with a studio that runs on written briefs and no calls, the brief is the whole conversation, so every gap in it becomes a guess.
A good brief does not need to be long, and it does not need design vocabulary. It needs to describe your business plainly, say who the work is for, point to a few examples with a reason attached to each, and be honest about the limits you are working within. Half a page of specific answers is more useful than three pages of adjectives.
Below is the structure we suggest, with weak and stronger answers for a made-up business. Swap in your own details as you go.
Start with the job the design has to do
Before style, describe the situation. What is changing in your business that makes you need this now? Where will the work be used first? What should someone think or do after seeing it?
Weak: "We need a modern, clean logo."
Stronger: say you run a two-person bookkeeping practice that has grown through referrals and is about to launch its first website. A useful brief might read:
We are a two-person bookkeeping practice for restaurants and cafés. Until now all our clients came through referrals. We are launching a website next month and will start sending proposals by email. The logo needs to work small on invoices and in a browser tab, and it should feel calm and dependable rather than corporate.
Words like "modern" and "clean" appear in nearly every brief, so they do not help the designer choose between options. The stronger version gives a size constraint, the first places the logo will appear, and a tone defined against something to avoid.
Describe your audience in plain terms
"Everyone" is not an audience, even if anyone could buy from you. Describe the people who buy most often, or the ones you want more of, in a few lines:
- Who they are, in practical terms: age range, job, and what kind of business if you sell to businesses.
- How they usually find you.
- What they worry about before buying.
- Where they will see the design: a phone, a printed menu, a shop window, an app store listing.
For the bookkeeping example, that might be: "Restaurant owners, mostly 35 to 60, who find us through their accountant or through other owners. Their worry is that we will be one more supplier who does not understand how a kitchen runs. They will mostly see our name in an email on their phone."
That last sentence alone tells the designer to test the logo at small sizes on a phone screen before anything else.
Show references, and say what you like about each
References are the fastest way to show taste, but a folder of screenshots on its own is ambiguous. If you send a photo of some bakery packaging, do you like the colours, the illustration, the paper or the handwritten type? The designer cannot tell.
Pick three to five references and write one line for each:
- "This packaging: I like that it uses one strong colour and lots of empty space."
- "This website: I like the large photos and that there is very little text above the first button."
- "This logo: I like that the symbol still reads when it is tiny."
Then add one or two examples of what you do not want, with a reason. "Nothing that looks like a bank" is a useful line. References from outside your industry often help more than ones from inside it, because they show your taste without pulling the design towards what your field already does.
List the hard constraints
Constraints are not a nuisance for a designer. They narrow the options in a helpful way, and discovering them after the first draft is what causes rework. Include anything that is already fixed:
- Existing elements that must stay, such as a colour your customers already associate with you, a name or a mascot.
- Every place the work will appear: print, embroidery, signage, dark backgrounds, an app icon, a favicon.
- The platform your website runs on, if the work is for a website.
- Text that must appear, and every language it will appear in.
- Accessibility needs, such as minimum text sizes or strong colour contrast for readers with low vision.
- A fixed date, such as a print deadline or an event, and whether that date can move.
If you are not sure whether something counts as a constraint, include it. A line that turns out not to matter costs the designer a few seconds to read.
Separate what is decided from what is open
A brief that pretends everything is decided hides the questions you are still unsure about. A brief that leaves everything open gives the designer too many directions to choose from. The most useful version says which is which. A short table works well:
| Decided | Still open |
|---|---|
| The name stays as it is | Symbol plus wordmark, or wordmark only |
| Dark green is our main colour | The second colour |
| Must work in one colour for rubber stamps | Serif or sans serif lettering |
It is fine to write "I don't know" next to a question. The designer can make a call in the first draft and explain the reasoning, which gives you something concrete to react to instead of an abstract question to answer.
Write the content before the layout, where you can
For landing pages, websites and app screens, the content shapes the design. A headline of six words and a headline of twenty words need different layouts. If the first draft is designed around placeholder text, it often has to be reworked once the real text arrives.
You do not need finished copy. A list of sections with rough text under each is enough: what you offer, how it works, prices or how pricing works, frequent questions, and how to get in touch. Real photos, or at least a description of the photos you have, help too. A design built around large, bright photography will look very different with the dim phone pictures you actually own.
After you send it: use your revision rounds well
With a fixed number of revision rounds, the way you give feedback matters almost as much as the brief. A few habits help:
- Collect feedback from everyone who has a say before sending it, and send it in one message. Two partners sending separate, conflicting notes uses up a round and leaves the designer to pick a side.
- Say what is not working and why, and leave room for the fix. "The green feels too cold next to our photos" is more useful than naming an exact replacement colour, because the designer may solve it another way.
- Point back to the brief. If the draft misses something you wrote, quote it. If you have changed your mind since writing the brief, say so plainly, because otherwise the designer will keep following the original.
- Mention what is working, so it does not get changed by accident in the next version.
Vague notes like "make it pop" or "it's not quite there" are hard to act on. Try to finish the sentence: not there in what way?
None of this requires design knowledge. It requires knowing your business, which you already do.
If you want to put this into practice, Hyper Framez sells a brand identity kit at a fixed price that starts from a written brief like the one above.
