Most bad design outcomes trace back to a bad brief, not a bad designer. A designer can only work with what they're told — and "make it pop" or "something modern" gives them almost nothing to work with. Here's what separates a brief a designer can actually execute from one they're left guessing at.
1. What the project is actually for
Not "we need a logo" — but what the logo needs to do. Is it launching a new product? Repositioning an existing one? Replacing something that tested badly with customers? The same visual brief can call for completely different design decisions depending on the underlying goal, and "what is this for" is the question most briefs skip entirely.
2. Who it's actually for
Not a vague "everyone" — a real audience. A brand identity aimed at enterprise procurement teams and one aimed at Gen Z consumers shouldn't look remotely similar, even if the underlying product is comparable. If you don't know your audience precisely, that's worth figuring out before the brief, not during it.
3. Real references — and what you actually like about them
"Something like Apple" tells a designer almost nothing on its own — is it the minimalism, the typography, the price positioning, the photography style? Naming references is useful; naming why a reference works for you is what actually transfers into someone else's decisions. It's just as useful to name what you dislike and why.
4. What already exists, and what's changing
If there's an existing brand, style guide, past approved work, or even just internal opinions from a previous rebrand attempt — say so. A designer working blind will often accidentally re-solve a problem that's already been settled, or contradict a decision made for a reason they weren't told about.
5. The constraints that aren't obviously "creative"
Budget, timeline, and what you already have (a logo, brand guidelines, product photography, footage) all directly shape what's realistic — and all three get left out of briefs far more often than they should. A designer who knows the real budget and timeline upfront can tell you honestly what's achievable; one who doesn't will either guess wrong or ask you to fill in the gaps later, costing time either way.
A good brief isn't longer — it's more specific. Five clear answers beat two paragraphs of vague enthusiasm every time.
The shape of a brief that actually works
In practice, that's rarely more than five or six direct answers:
- What are we making, and what's it for?
- Who is it actually for?
- What references do you like, and specifically why?
- What already exists that this needs to work with (or replace)?
- What's the real budget and timeline?
- Are you supplying any existing assets, or is everything being created new?
That's genuinely it. A brief this specific takes ten minutes to write and saves entire revision rounds later — because the designer isn't guessing at any of the decisions that actually determine whether the first draft lands.
Try it — Aoibh asks these questions for you
The brief flow walks through exactly this, then matches you with a designer based on the answers.
Start a brief