Briefing a Designer: Communicate Vision Without Being Creative Yourself

Briefing a Designer: Communicate Vision Without Being Creative Yourself

Most bad design outcomes are not caused by bad designers. They are caused by bad briefs. When a client cannot articulate what they want with precision, the designer produces work based on their own interpretation — which may have nothing to do with what the client wanted. The resulting revision cycle is expensive, frustrating, and entirely preventable.

The Anatomy of an Effective Brief

A brief that produces the right work first has seven components:

1. The Project in one sentence: What is being made, for what purpose, for which audience. "A series of three Instagram feed posts promoting the launch of our new membership tier to existing customers who follow our account."

2. The Audience: Who sees this work? Not demographics in the abstract but the specific person who will encounter this design. What do they know about the brand? What do they care about? What is their state of mind when they encounter this piece?

3. The Objective: What specific behavior or belief change should this design produce? "After seeing this, the viewer should feel that this membership tier is exclusive and worth paying for" is an objective. "Make it look nice" is not.

4. The Message hierarchy: The single most important thing the viewer should take away, and the supporting information. Not six equally important messages — one primary, two supporting maximum.

5. Mandatories: Non-negotiable constraints. Brand colors. The logo must be present. The URL must appear. Legal disclaimer required. Mandatories define the fence within which the creative operates.

6. Visual references: Five to ten images, not of the design itself but of the feeling, mood, composition style, or color direction you want. Moodboarding in a Figma frame or Pinterest board communicates in seconds what a page of adjectives approximates.

7. Deliverables and format: Exactly what files will be produced, at what sizes, in what formats, by when. "Some social posts" is not a deliverable spec. "Three PNG files at 1080×1350px and three Story-formatted JPEGs at 1080×1920px, delivered by Thursday 5PM" is a deliverable spec.

Writing Feedback That Designers Can Use

Most clients instinctively give solution-feedback: "make the headline smaller," "change the blue to green," "move the logo to the top right." This is understandable — you know what you want to change; it seems efficient to say exactly what to change. But solution-feedback removes the designer from their professional role and often produces worse outcomes than problem-feedback, because designers have access to solutions the client would not think of.

Instead, use this structure:

• Observation: "The headline currently reads as very aggressive."
• Problem: "I need this piece to feel premium and calm."
• Outcome intent: "Can you explore how to make the headline carry authority without loudness?"

This gives the designer a problem to solve and a desired outcome to work toward — not an instruction to execute. The result is typically better work than the client would have specified.

Visual References as a Design Tool

When describing a visual direction verbally, every adjective is ambiguous. "Modern" means five completely different things to five different designers. "Clean" means something different to a Scandinavian minimalist and a brand designer who came up through editorial.

Visual references collapse this ambiguity. Show three or four reference images representing the direction you want, and annotate them: "I like the way this image uses negative space" — "I want this kind of type treatment" — "This lighting mood is exactly what I am after." The annotations prevent the designer from interpreting the reference too literally or too abstractly.

Visual references should represent direction, not the destination. "I want something that looks like the Apple website" is not a useful reference — it tells the designer to copy rather than design. "I like the way Apple uses white space and restrained typography" is a useful reference — it identifies a principle that can be applied to your specific project.

Managing Revision Cycles

Revisions are not a sign that the first attempt was wrong. Iteration is normal in design. What is abnormal — and expensive — is unlimited iteration without structure.

The professional standard is to consolidate all feedback into one cohesive round before responding. This means: collect feedback from all stakeholders, resolve internal disagreements before sending to the designer, and send one clear, prioritized feedback document. Sending feedback in multiple emails over multiple days is a revision round multiplier — each exchange triggers a revision even though individually they are minor notes.

Brief clearly. Consolidate feedback. Trust the designer's professional judgment on solutions. These three practices produce better work faster and cheaper than any alternative.