A creative brief should reduce uncertainty without pretending that every answer is known. It aligns the team around the problem and gives creative work a standard that is more useful than personal taste.
Name the decision
Start with the decision the organisation needs to make, not the asset it expects to receive. A new identity, campaign or site is usually a response to a deeper change.
Write the desired change in one sentence and identify who has authority to approve it.
Define the audience in context
Demographics rarely explain enough. Describe the situation, current behaviour, doubt and pressure surrounding the choice.
Use evidence from conversations, service data or research, and mark assumptions that still need testing.
Describe the problem precisely
Separate symptoms from the underlying communication or experience problem. “We need a new logo” is an output, not a diagnosis.
Explain what people currently misunderstand, overlook or find difficult to do.
Set the promise and proof
State the most important idea the audience should understand and the evidence that makes it credible.
Avoid stacking several equal claims; hierarchy is part of the brief.
Record constraints
Timing, budget, accessibility, technical platforms, legal requirements and existing assets all shape the solution.
A visible constraint supports better creativity than a surprise revealed after approval.
Choose representative deliverables
List the formats needed to test the idea, including ordinary and difficult use cases.
Do not use a long deliverable list as a substitute for the reason each output exists.
Define the review process
Name contributors, decision-makers, review rounds and the criteria for feedback.
Collect comments in one place and separate strategic concerns from small production corrections.
Plan the handoff
Decide who will own files, guidelines, publishing and future changes.
A brief is stronger when it considers the life of the work after launch.
Applied practice 1: Define the decision
Concentrate on the change the project must enable and the person responsible for approving it. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for confusing a deliverable with the underlying problem. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, write the decision, audience and test of success in one concise paragraph. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 2: Gather useful evidence
Concentrate on the conversations, service data and existing material that reveal the real constraint. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for collecting inspiration without learning anything about the situation. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, summarise observations and label assumptions that still require testing. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 3: Create a hierarchy
Concentrate on the one message that leads and the supporting ideas that provide proof. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for giving every claim and visual element equal weight. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, rank the content before judging typography, colour or composition. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 4: Explore meaningful routes
Concentrate on directions based on different principles rather than cosmetic variations. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for presenting several versions that all make the same decision. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, explain the strategic difference and the context in which each route works. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 5: Test ordinary content
Concentrate on long names, small screens, imperfect photography and routine production needs. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for approving a system that works only in a polished presentation. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, use representative content and the formats the team handles every week. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 6: Review against criteria
Concentrate on audience, clarity, recognition, accessibility and operational fit. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for turning feedback into an unstructured collection of personal preferences. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, ask reviewers to connect every comment to an agreed objective or constraint. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 7: Document flexible rules
Concentrate on the decisions that should repeat and the areas where variation is valuable. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for creating guidelines so rigid that teams work around them. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, show boundaries, examples and the reason behind each important rule. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 8: Prepare ownership
Concentrate on the people who control files, licences, publishing and future changes. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for handing over assets without a clear decision process. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, name owners, approval routes and the source of truth for current files. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 9: Launch coherently
Concentrate on the pages, channels and internal material that must change together. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for releasing one visible surface while contradictory versions remain active. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, use a short launch checklist and retire obsolete assets deliberately. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Applied practice 10: Learn from real use
Concentrate on the questions, production friction and audience behaviour that appear after launch. Put the real audience, content and production conditions on the table before the team judges a visual route. The aim is to make one useful decision visible, not to make the project sound more certain than it is.
Watch for treating the first release as proof that no adjustment is needed. It usually appears when a review has no agreed question, when representative content arrives too late or when a polished mock-up hides the behaviour of the wider system. Name the weakness precisely so the next iteration has a clear job.
In the next working session, schedule a focused review and improve the system without reopening its entire foundation. Record the decision, its owner and the format that will test it. That creates a practical bridge between creative intent and the everyday work the team will need to produce after handoff.
Creative decision framework
| Moment | What matters | Useful next move |
|---|---|---|
| Before you begin | Audience, objective and the decision the work must support | Write a brief with one priority and clear constraints |
| While choosing | Recognition, hierarchy, usefulness and consistency | Review against agreed criteria instead of taste alone |
| Afterwards | Handoff, ownership and the next live test | Document the system and assign the next decision |
Review checklist
- Name the audience
- Write the desired outcome
- Choose one primary message
- Separate constraints from preferences
- Compare a small set of directions
- Test the hierarchy at real size
- Check contrast and legibility
- Document repeatable rules
- Assign an owner to feedback
- End with a visible next step
Questions from the studio
Will one framework solve every project?
No. A framework creates shared criteria, but the audience, constraints and live feedback still shape the decision.
What if the details conflict?
Compare scope and date, then favour the source that applies to the exact product, project or situation.