What this article is about
Why the brief matters more than most owners realise, what a working brief actually contains, the difference between briefing for one-off work and briefing for template work specifically, the role of references, the common briefing failures, how briefing adapts to different working relationships, and a practical structure for writing a brief in a focused hour. Written for owners commissioning design work and wanting to make the experience produce useful outputs first time.
The brief is the most under-attended document in the design relationship. Owners commission work, send a few lines of email, expect the designer to produce something usable, and are quietly surprised when the first round comes back not quite right. The same pattern recurs across freelancer engagements, agency projects, and in-house design requests. The work begins; revisions accumulate; the schedule slips; the final templates are usable but feel as if they were arrived at by negotiation rather than designed with intent. The diagnosis, in almost every case, is that the brief did not do its job.
The honest reframe is that a well-written brief is the single biggest determinant of design outcome, more so than the designer’s skill in many small business engagements. A skilled designer with a vague brief produces work that drifts toward generic competence. A reasonably skilled designer with a clear brief produces work that actually fits the business. The leverage of an hour spent on the brief shows up in fewer revisions, faster delivery, and templates the business actually uses. The investment is small. The cost of skipping it is hidden in every revision round that could have been avoided.
Why the Brief Is the Most Consequential Part of Any Design Engagement
The brief is what the designer uses to understand what they are being asked to make. Everything that follows — the conceptual approach, the visual direction, the specific decisions inside the work — is shaped by what the brief did or did not say.
A clear brief is not a constraint on the designer. It is a starting point that lets the designer focus their attention on the design problem rather than on guessing what the business actually wants. The designer can now think about how to solve the problem instead of what the problem is. The work moves faster, and the result is more aligned with the business’s needs.
A vague brief produces the opposite. The designer guesses at the unstated answers. Some of the guesses are correct. Others are not. The first round of work reveals which is which, and the revision rounds begin. Each round corrects the misaligned guesses. The schedule slips. The designer’s enthusiasm fades. The business’s confidence in the engagement fades with it. The final work is usable but worse than it could have been, because the design conversation never actually got past the initial mismatch.
The honest reframe is that revision rounds are not a sign of careful collaboration. They are usually a sign of inadequate briefing at the start. A small business that has had multiple disappointing design engagements is usually a small business that has not yet learned to brief well. The fix is upstream of the work itself.
What a Working Brief Actually Contains
A working brief contains a small number of components, written clearly. The form can be a single document, a shared workspace, a structured email — what matters is the substance.
Context. What the business is, what it does, who its customers are, what stage it is at. The designer needs enough context to make decisions that fit the business. A brief that assumes context the designer does not have is a brief that will produce work disconnected from the business.
Purpose. What this design work is for. Why it is being commissioned. What outcome it is meant to support. “We need new social templates because our current ones do not work in grid view and we have been growing our Instagram presence” is a purpose. “We need new social templates” is a request without context.
Audience. Who the design will be seen by. The specific audience whose attention the design needs to earn. This is one of the most-skipped sections of most briefs, and one of the most consequential. A design that works for one audience may not work for another; the designer needs to know which audience matters.
Scope. What is included in the engagement, and — more importantly — what is not. The number of templates. The number of variants. The platforms covered. The deliverables expected. The rounds of revision included. Vague scope produces scope creep, which produces frustration on both sides.
Constraints. Brand colours, typefaces, voice, style requirements, technical requirements, accessibility requirements, platform specifications. The constraints the designer needs to work within. Constraints are not limitations on creativity; they are the boundaries within which the design has to be useful.
References. Examples of design work that the business finds relevant — including what they like, what they do not like, and what they want to feel similar to. References give the designer a calibration point. Used well, they accelerate the work. Used badly, they pre-design the outcome, which is a different problem (more on this below).
Success criteria. What will tell the business that the work is good. How they will evaluate it. The kinds of feedback they will give. This is rarely written down and almost always useful — it forces the business to articulate what “good” means before the work begins, rather than recognising it (or not) afterwards.
Practical logistics. Timeline, budget, point of contact, approval process, file format requirements, where the assets will live. The administrative substrate that makes the engagement run.
A brief with these components, kept to a few pages or a single well-organised document, is a working brief. Most briefs are missing two or three of them — usually purpose, audience, or success criteria — and the missing components are what produces the misalignment.
Why “Make It Look Nice” Is Not a Brief
The most common version of brief failure is the brief that consists almost entirely of taste signals and almost no substance. “Make it look nice.” “Modern but not too modern.” “Clean and professional.” “Like our brand but elevated.”
Each of these phrases is true in the sense that the business does want the work to be nice, modern, clean, and brand-appropriate. None of them is specific enough to guide a single design decision. The designer reading them learns nothing about who the audience is, what the work is for, what success looks like, or what constraints the design needs to honour. The brief has communicated the existence of standards without naming any of them.
The cost of taste-only briefing is paid in revision rounds. The first round of work comes back; the business does not quite like it; the feedback is also taste-shaped (“it feels too cold,” “can we try something more vibrant”); the second round goes the other direction; the third round tries to find a middle ground. The work eventually arrives, after enough rounds, at a place the business finds acceptable — but the process has been more expensive and slower than it needed to be, and the result is shaped by negotiation rather than by design.
The fix is to spend the brief-writing hour articulating the substance that the taste signals were standing in for. What does “modern” mean for this business? What audience needs the work to read as modern? What references would communicate the kind of modern intended? What constraints would prevent the design from being too modern? The substance produces the alignment that the taste signals were trying to gesture at.
The Role of References
References are one of the most useful and most easily mishandled parts of a brief. Used well, they communicate aesthetic intent and aesthetic boundaries faster than words. Used badly, they pre-design the outcome and constrain the designer to the point where the brief is no longer a brief — it is an instruction to copy.
A few principles for using references well.
Include references that capture qualities rather than specific solutions. A reference is useful when it communicates “we want something that feels confident and direct, like this” — not when it communicates “we want a design that looks exactly like this.” The first allows the designer to interpret; the second tells them what to produce.
Include negative references as well as positive ones. Examples of design work that the business specifically does not want. The contrast is often more informative than the positive examples alone. Two designers shown only positive references may diverge in their interpretation; two designers shown both positive and negative references converge faster.
Annotate the references. A reference without annotation tells the designer that the business likes something about the example but not what. A reference with two sentences of annotation — “we like the way the type does most of the work here” — tells the designer which aspect of the example matters.
Resist the temptation to over-reference. Five well-chosen and annotated references are more useful than fifty unstructured ones. Long reference decks tend to communicate uncertainty rather than direction, and the designer ends up trying to honour too many influences at once.
References are best understood as a calibration tool — they help the designer locate the work in design space — rather than as a specification. The brief is what specifies; the references help the designer understand what the specification means.
The Difference Between Briefing for One-Off Work and Template Work
Most briefs are written as if the design work is a one-off. For template work, this framing produces predictable problems. Templates are not one-off artefacts; they are reusable systems that will be used many times by many people. Briefing for templates needs to account for the system, not just the look.
A few things that change when briefing for templates specifically.
The brief should describe the use cases the templates will need to serve. What content types will fill them. How often they will be used. Who will fill them in. Whether the users are designers or non-designers. The templates need to work for the actual use, not just to look good in the brief presentation.
The brief should specify how flexible the templates need to be. How many variants. Which decisions should be locked. Which should be available. The discipline of constraint that produces consistent templates needs to be flagged early; designers asked vaguely to “make templates flexible” tend to produce templates with too many choices, which then produces drift.
The brief should describe the wider system the templates are part of. The brand’s design system, if it exists. The other templates the new work needs to coexist with. The visual language the templates need to live inside. Templates designed in isolation from this context tend to drift from the rest of the business’s design work.
The brief should describe the handoff. How will the templates be used after delivery? Who will maintain them? What format do they need to be in? Templates that are perfect in the designer’s tool but unusable in the team’s actual workflow are a familiar disappointment.
The brief should describe the success criteria specific to templates. Not “does it look nice” but “will a non-designer be able to produce on-brand work using this template under time pressure.” Template success looks different from one-off design success.
A template brief that addresses these specifics produces templates that work in the conditions they will actually be used in. A template brief written as if for a one-off produces templates that work in the presentation but not in the workflow.
Outcomes, Not Solutions
A useful principle: the brief should describe what the design needs to accomplish, not what the design should look like.
The reason is straightforward. The designer’s job is to produce the design that accomplishes the outcome. A brief that specifies the outcome and leaves the design to the designer makes the engagement an actual design engagement. A brief that specifies the design tells the designer what to do and reduces them to a production resource — which produces predictable disappointment, because the business is now choosing the design without the designer’s expertise.
In practice, this means writing the brief in terms of what the templates need to do, not what they should look like. “Templates that produce on-brand social posts when filled in by our marketing coordinator, without their needing to make design decisions about colour, type, or layout” is an outcome. “Templates with a navy background, white headlines in Inter Bold at 64pt, and our logo in the top-left corner” is a solution masquerading as a brief.
This is harder than it sounds, because the temptation to specify the design is strong. Most owners know what they think they want at the level of solution. The discipline is to translate that intuition back into outcomes — what is the solution trying to achieve — and let the designer decide whether the imagined solution is the best one or whether a different solution would do the job better.
The outcome-led brief is also more durable. When the design needs to evolve, the brief still describes what the design is for. The solution-led brief, by contrast, becomes obsolete as soon as the specific design changes — and the underlying outcome has to be reconstructed.
The Common Briefing Failures
A few patterns recur across briefs that produce disappointing outcomes.
Too vague. The brief consists of taste signals and aspirational adjectives. The designer has nothing concrete to design against. Revision rounds accumulate as the alignment gets discovered through iteration rather than through specification.
Too prescriptive. The brief specifies the design at the level of solution. The designer has no creative latitude. The work that comes back is technically what was asked for and disappointing in the way that work without design judgement usually is.
No audience definition. The brief assumes the designer understands who the work is for. The designer makes assumptions; the assumptions do not match the business’s actual audience; the work misses the mark.
No success criteria. The brief never specifies what success looks like. Evaluation happens at the end, by gut feel, with feedback shaped by whatever the business notices first. The designer has no way to evaluate their own work against a shared standard.
Missing constraints. The brief omits the constraints the design needs to honour. Brand colours, typefaces, technical requirements, accessibility, voice. The designer produces work that violates the constraints because they were not told about them.
References without context. The brief includes references but does not annotate them. The designer guesses at which qualities matter. The guesses produce a design that the business finds disappointing in ways that are hard to articulate.
No scope. The brief does not say what is included or excluded. Scope creep follows. By round three, the engagement has expanded beyond what was budgeted.
Verbal-only briefing. The brief was discussed in a meeting and never written down. Everyone left the meeting with a slightly different understanding of what was agreed. The work begins from divergent starting points.
Each of these failures is fixable. The most useful starting point is to look at a brief you have written and ask which of the components in this article it includes and which it omits.
How Briefing Adapts to Different Working Relationships
The components of a good brief are consistent across working relationships. The form adapts.
In-house designer. The brief can be lighter on context — the designer already knows the business — but more specific on scope and timeline. Internal briefs sometimes get treated as informal, which produces the same misalignment as poorly-briefed external work. The brief should still be written down.
Agency. The brief usually needs more context, especially if the agency is new to the business. The brief should also include the practical logistics — points of contact, approval process, file formats — at higher fidelity than internal briefs require. Agencies are running multiple projects; the brief helps them prioritise.
Freelancer. The brief is the freelancer’s most important alignment tool. Freelancers are often working solo, without the buffer of an agency’s account management. A clear brief helps them deliver on time and on point. A vague brief produces revision rounds that the freelancer often absorbs at their own cost.
Marketplace contractor or fixed-scope platform. The brief needs to be especially clear about scope and deliverables, because the engagement is structured around defined outputs rather than ongoing dialogue. Ambiguity that would be resolved through conversation in a higher-touch engagement turns into misalignment here.
Across all of these, the underlying brief content is the same. The presentation, the level of context, and the practical logistics adapt to the relationship.
A Practical Structure for Writing a Template Brief in an Hour
For an owner sitting down to write a brief, a workable sequence.
Block out a focused hour. The brief deserves more attention than the fifteen-minute version most owners default to.
Start with context. A paragraph or two that explains what the business is, who it serves, where it is in its development, and what is relevant about its current state for this engagement.
Write the purpose. A few sentences on why this work is being commissioned, what outcome it supports, and what is at stake in getting it right.
Define the audience. The specific audience whose attention the templates need to earn. Be concrete. If there are multiple audiences, name them and indicate which matters most.
Specify the scope. What templates, in what variants, for what platforms. What is included; what is explicitly not. Approximate quantities, even if exact numbers can wait.
List the constraints. Brand colours, typefaces, voice, technical requirements, accessibility, anything the design needs to honour. Be exhaustive about the constraints; under-specifying them invites violations.
Choose three to five references. Annotate each one with a sentence or two on what aspect matters and why. Include one or two negative references if useful.
Write the success criteria. Two or three sentences on how the business will evaluate the work. What “good” looks like. What feedback will likely be given.
Add the practical logistics. Timeline, budget (if appropriate to share), point of contact, approval process, deliverable format, where assets will live.
Read it through. Cut anything that is not useful. Add anything that a careful designer would still need to ask about. The brief should be specific enough that an experienced designer could begin work without needing a kickoff meeting — though a kickoff meeting will still help.
Share it. Discuss any questions. Confirm alignment before the work begins. Adjust if the conversation reveals gaps.
The whole sequence takes about an hour. The cost of skipping it is paid, on average, across two or three additional revision rounds. The math, in retrospect, is almost always in favour of writing the brief.
Key Takeaways
- The brief is the most consequential part of any design engagement — more determinative of outcome than the designer’s skill in many cases.
- A working brief contains context, purpose, audience, scope, constraints, references, success criteria, and practical logistics.
- “Make it look nice” is not a brief; taste-only briefing produces revision rounds because the substance was never articulated.
- References should communicate qualities rather than solutions, include both positive and negative examples, be annotated, and stay limited in number.
- Briefing for templates is different from briefing for one-off work — the brief needs to describe use cases, flexibility requirements, the wider system, the handoff, and template-specific success criteria.
- The brief should describe outcomes, not solutions; the designer’s job is to produce the design that accomplishes the outcome.
- Common failures include vagueness, over-prescription, no audience definition, no success criteria, missing constraints, references without context, no scope, and verbal-only briefing.
- The components of a good brief are consistent across working relationships; the form adapts to in-house, agency, freelancer, or marketplace engagements.
- A focused hour spent on the brief typically saves two or three revision rounds across the engagement.
A note from SWL
Pull up the most recent design brief you sent — by email, by message, by document — and check it against the components in this article. If two or three of them are missing, the engagement that brief produced was probably more expensive than it needed to be. Briefing is one of the highest-leverage hours a business owner can invest in design work. If you are about to commission template work and want a calm review of whether the brief is doing its job, we are happy to take that look with you.