The Logo Design Brief I Actually Need

Most Briefs Are Not Briefs

The typical logo brief I receive from a new client contains: the business name, a rough description of what the business does, the client's personal aesthetic preferences, and a reference image board of logos they like from unrelated industries.

This is not a brief. It's notes. A brief tells me what problem the design needs to solve. Notes tell me what the client is thinking about today.

Getting from notes to a real brief is part of my discovery process, and it's not optional. Working from insufficient information produces work that has to be redone.

What a Real Brief Contains

A genuine logo brief answers these questions:

What does the business do and for whom? Not just the category — the specific value and the specific audience. "We're a wealth management firm serving first-generation wealth builders who feel underserved by traditional banks" is a brief. "We're a financial services company" is a category description.

What do you want people to feel when they encounter this brand? Specific emotional descriptors. Not "professional" — every business wants to feel professional. The three adjectives that make this brand distinct from its nearest competitors.

Who are your key competitors, and what do you want to communicate that's different from them? This question often surfaces the most useful strategic information. What is the visual and positioning landscape, and where is there space?

Where will this logo be used? Physical signage, embroidery, digital only, vehicle graphics? The application context shapes what will work.

What are the constraints? Timeline, budget, any non-negotiable elements (existing marks to retain, specific colors required).

How I Extract the Brief

When clients can't fill out a written brief — and many can't, because articulating brand strategy isn't their job — I run a structured discovery conversation. I ask the questions above, listen carefully, and reflect back what I hear to confirm understanding.

Often the most useful answers come not from direct questions but from indirect ones. "Show me three competitors you admire and tell me why" reveals more than "what aesthetic do you prefer?" "Describe your best customer" tells me more than "who is your target market?"

When I Push Back

If a client's brief contains contradictions — they want to feel "approachable and fun" but also "premium and exclusive" — I don't just accept it and design for the conflict. I push back and help them resolve it. Trying to design for contradictory requirements produces work that satisfies neither requirement.

This conversation sometimes takes an entire session. It's worth it. A clear strategic position, even if it requires difficult tradeoffs to arrive at, produces cleaner design briefs and better work.

The Brief Is a Document

I write up the brief after the discovery conversation and send it to the client for sign-off before starting design. This protects both of us. It ensures we're aligned before I invest time in development, and it gives us a reference document when feedback arrives that asks the work to do something the brief never specified.

The brief is a contract about what problem we're solving. I take it seriously.