Skip to content

Design Brief

beta  ·  Family discovery-docs  ·  Phase define  ·  Sizes lean, full  ·  ~4,050 tokens

The document that hands the chosen problem and the one concept chosen for design to the people who will design it, before anyone specifies how that concept works. Lean carries the challenge, who it is for and what was learned, the chosen concept and the handoff; full adds constraints on the design, open questions for design, and the handoff’s scope, time line and budget.

How to tell whether you need one, how to pick lean or full, and how to grade what comes back before it goes to the people who will design from it.

Before you start: is this the right document at all?

Section titled “Before you start: is this the right document at all?”

Write a design brief when you have one chosen problem and one concept chosen for design, and you need to hand both to the people who will design it, before anyone specifies how that concept works. The Design Council’s own page names this hand-off directly, placed at the close of Define: “The result is to create a design brief which clearly defines the challenge based on these insights.” This document’s whole job, per this library’s discovery-docs family contract, is to converge on one chosen problem and, at most, name the one concept chosen for design, never how that concept works, and it decides no investment.

Write something else if:

You actually need Because
a problem statement this library’s own problem-statement bundle already names the chosen problem; where one exists, point to it from The Challenge rather than reframing it here
a project brief a project brief asks a named approver for authority to start finding out whether and how to proceed; this document asks for no such authority, and names a concept already chosen
a business case no source read for this bundle orders the two against each other in either direction; treat that as open, at medium-low confidence, rather than as a settled sequence
a specification, a product design specification, or a PRD Ignitec draws the line directly, “The commercial considerations will come later when you write your product design specification,” and UXPin agrees that “A design brief outlines what designers must create, while the specifications define specific details”
a creative brief Figma’s own account orders the two: “In many design workflows, the creative brief informs the design brief, ensuring visual decisions support broader project goals.” Write the creative brief first if your team already writes one
the Shape Up pitch a pitch arrives shaped, where “the overall solution is spelled out,” and exists, in Basecamp’s own words, “to present a good potential bet”; this document hands over a concept and asks for no bet
a Design Sprint brief Google Ventures’ own page describes “a five-day process” and publishes no separately named Sprint Brief to write instead
a commissioning agreement between a client and a designer that is the commonest sense of the term in the literature this bundle’s research read, carried by Visser, the Design Commission for Wales, and Wikipedia; this bundle builds a different sense and says so throughout

Write nothing at all if no one distinct from the chosen problem’s own owner will design from this document. Visser’s own research found that “in many of the interviews the projects discussed started without a design brief,” and at least one named software design team, Intercom’s own, describes an iterative process with no brief-shaped kickoff document at all: “We’re continually iterating this process, figuring out ways in which we can design better things faster.” A document nobody reads before designing has not finished the job this bundle exists to do.

Lean carries The Challenge, Who It Is For and What We Learned, The Chosen Concept, and The Handoff: enough to hand a chosen problem, a chosen concept, and an approved start to the people who will design it. Full inserts Constraints on the Design and Open Questions for Design between The Chosen Concept and The Handoff, and The Handoff’s Scope, Time Line and Budget after it.

Use full when a separate design team needs limits on the design work, open questions, and a design-scoped time line and budget stated in writing, not only a chosen concept and a handoff. Use lean when a team’s own designers are already close to the work and need none of that written down on its own. The three added sections do not carry equal weight with the four lean ones: no source read for this bundle publishes a design-only constraints section or a time line and budget scoped to a design handoff alone, and the Open Questions field rests on one practitioner template, Heap’s own. The candidates list inside The Chosen Concept, which both sizes carry and row 5 scores, rests on that same template’s “Discarded Alternatives” field; the spec rated it low, and the research log proposes low to medium-low. Treat each as this library’s own construction, stated at its own confidence in the template’s own section comments, never as received practice.

Below 16 out of 22 on a full brief, the designers inheriting it cannot tell what altitude the concept is pitched at, what it leaves out, or who settles a disagreement once design starts, without coming back to ask you questions this document should have answered on its own. Below 12 out of 16 on a lean brief, the same gap opens with three fewer sections standing between a weak answer and the people who design from it.

# Criterion 0 1 2
1 Challenge stays a problem The section names a feature, a screen, or a channel to build, or already reads like the concept below A problem is named, but you cannot tell from the sentence what a good outcome would change for the people who have it You can point at the sentence, say what a good outcome changes, and no screen, button, or channel appears anywhere in it
2 Audience and insight “Users” or “the team,” with no insight stated A group is named, but you cannot point to the single research insight the challenge rests on You can name a group someone could go find a member of, and point to the one insight, in a sentence or two, that this challenge rests on
3 Concept held at altitude The chosen concept names a screen, a button, a flow, or how a feature works The concept is named at the level of a kind of answer, but a reader could reasonably mistake it for a solution already begun You can point at the concept sentence, and it names the kind of answer chosen, never what a screen shows, what a button does, or how a flow proceeds
4 What it leaves out Nothing is named as excluded, or the field says only that everything else is out of scope Something is named as excluded, but you cannot say who would have reasonably assumed it was included before this line You can name the specific thing excluded and say who would have assumed it was in, before this line said otherwise
5 Candidates genuinely weighed No other candidate is named, or the “candidates” are the chosen concept restated A candidate is named, but the reason it was set aside is missing, or is really the reason the chosen one was picked, said twice You can name a genuinely different candidate and the specific reason it was set aside, distinct from the reason the chosen one was picked
6 Approval recorded, not granted No named approver appears, or the section reads as granting the project its funding or its authorization to exist A named approver and a date appear, but you cannot tell from the sentence that only design beginning, not project funding, was approved You can point at the name and the date, and the sentence makes clear that what was approved is design beginning, never the project’s funding
7 Revision names its review No revision process is named, or the brief reads as fixed once written A revision process is named, but you cannot tell whether it means reviewing this document before it goes out, or reviewing the design as the work proceeds You can tell, from the sentence alone, which of the two reviews the team means, and roughly when it happens
8 Feedback has a decider No one is named as the person who settles disagreement in feedback on the design A decider is named, but only as part of a group, with no single name a designer could actually go to One named person settles a disagreement in design feedback, distinct from whoever approved the concept
9 Constraint is design-scoped (full only) A limit is named at the level of the whole project, such as a launch date or a total budget, or the row states a goal rather than a limit A limit on the design work is named, but you cannot tell why it binds design specifically rather than the whole project You can point at the limit and the same row says why it binds the design work itself, not a limit a project brief would already carry
10 Open question is unresolved (full only) The field restates a constraint already named above, or says only that there might be open questions A question is named, but you cannot tell whether anyone actually does not yet know the answer The question names something nobody yet knows, distinct from every constraint above, with an assumption held until it is answered
11 Scope, time, budget design-scoped (full only) The budget line carries a project figure, or neither the scope nor the deadline names a deliverable short of a finished screen or flow Scope and timing name the design work alone, but the budget line is silent where it should plainly say none exists Scope, timing, and budget each name the design work alone, and where no design-scoped budget exists, the row says so instead of carrying a project figure

Which rows apply to what. Full ships all eleven rows because a reader of the full variant can ask about design-only limits, open questions, and a design-scoped time line and budget, as well as the four sections every size must get right. Lean ships eight, every row the lean variant has a section to support.

Document Rows Maximum Score against
lean 1-8 16 12
full all 11 22 16

Specifying how the concept works, inside a document meant to name only what it is. Shape Up’s own description of a shaped concept, “It defines what the feature does, how it works, and where it fits into existing flows,” is exactly the content this document excludes. A sentence that reads like that description has crossed into a specification.

Treating Heap’s own template as proof this sense reaches into solution detail. Heap’s template is real and literal, including “Discarded Alternatives:” and “Open Questions,” but its own goal line names “your proposed design solution(s),” not a chosen concept. Cite its headings only with that solution-sense label attached, never as this document’s own structure confirmed.

Reading the no-solution camp as support for naming a concept. GANSW’s advisory note states “Focus on desired outcomes, but don’t prescribe a solution,” and Ignitec’s is “Say what and why, but not how.” Both forbid naming any solution at all. This library’s own chosen-concept rule departs from that camp; neither source argues for it.

Reusing Basecamp’s pitch line to describe this document’s own altitude. Shape Up’s “the overall solution is spelled out” and “The purpose of the pitch is to present a good potential bet” both describe the pitch, a rung above this document and a separate, unbuilt catalog candidate. Neither sentence argues that a design brief needs a worked solution.

Writing a budget section that actually holds a project’s budget. (full only) Every sourced budget question this research found scopes to the whole project: Kaninsky’s own template asks “What is your budget for this?” and Eleken’s asks “7. What are the project timeline and budget?” This section’s own figure, where one exists at all, is the design work’s alone, never a stand-in for the project’s.

Treating the sign-off recorded here as the decision that funds the project. The Eleven Lessons report describes what that sign-off actually buys: “the corporate and financial backing to the development of one or more concepts that have addressed the initial problem.” The Handoff may record that design was approved, by whom and when; it is never the record that grants the backing itself.

Setting the challenge too broad or too narrow. Visser warns that “design briefs could be too broad as well as too narrow.” Shape Up describes the too-broad failure from the inside: “You’re solving a problem with no context. You have to be a mind reader.” The too-narrow failure is the specification creep rows 1 and 3 are built to catch.

Importing creative-brief tone and voice guidance. Asana’s own tone discussion, “Think of your message as a person. It should have a voice (a personality) and a tone (a mood or attitude),” belongs to creative briefs specifically. This document carries no tone or voice section at any size.

Claiming a Google Ventures Sprint Brief, or Atlassian’s project poster, as evidence for this document. GV’s own page names “a five-day process” and publishes no separate Sprint Brief. Atlassian’s own poster is a living kickoff document whose text points toward a project plan, nearer this library’s project-brief than this one.

When the concept is named at the level of a kind of answer and nowhere crosses into how it works, when what it leaves out is specific enough that someone could say who would have assumed it was in, and when a named person has actually approved design to begin, by a real date, without that approval reading as the project’s funding.

Then delete every HTML comment. A brief nobody has approved, or one that quietly grants a project its backing instead of recording that design may start, has not finished the job it exists to do, whatever else it contains.

design-brief_template-lean.md · ~4,050 tokens

---
title: "{{concept_name}} Design Brief"
concept_name: "{{concept_name}}"
author: "{{author}}"
approver: "{{approver}}"
status: "{{status}}"
last_updated: "{{date}}"
doc_type: design-brief
size: lean
source_template: design-brief
source_template_version: 0.1.0
---
<!--
LEAN DESIGN BRIEF. The shortest form that still hands one chosen problem and one chosen concept to
the people who will design it: The Challenge, Who It Is For and What We Learned, The Chosen Concept,
and The Handoff, in that order. Use it when a team's own designers are already close to the work and
need no separate limits, open questions, or a design-scoped time and budget stated in writing. To
grow it into a form that also carries design constraints, open questions, and the design work's own
scope, time line and budget, see design-brief_template-full.md. ADD sections between The Chosen
Concept and The Handoff, and after The Handoff; never rename or reorder the sections below, because
the full variant is a strict ordered superset of this one.
WHAT A DESIGN BRIEF IS, AND IS NOT, IN THIS BUNDLE'S SENSE
The term has no settled meaning in the wider literature: "There is no clear or univocal definition
in the literature." At least four senses recur across the sources this bundle's research read: a
commissioning agreement between a client and a designer; a technical and visual specification; a
chosen problem framed for design; and a worked solution. THIS DOCUMENT BUILDS A CHOSEN PROBLEM PLUS
A CHOSEN CONCEPT: it hands a chosen problem and the one concept chosen for design to the people who
will design it, at Define's close, per the Design Council's own placement, "The result is to create
a design brief which clearly defines the challenge based on these insights." No single source
publishes exactly this shape; the composition is this library's own, and every section below says
so honestly rather than claiming received practice.
A CONCEPT NAMES THE KIND OF ANSWER, NEVER HOW IT WORKS. "Concept" is not shared vocabulary: Shape
Up's own description of a shaped concept reads, by this library's own line, as a specification
already, "It defines what the feature does, how it works, and where it fits into existing flows."
This document stops one altitude short of that: name the kind of answer the team will pursue, and
leave what a screen shows, what a button does, or how a flow proceeds to the document this brief
hands off to.
IT IS NOT a problem statement (this library's own `problem-statement` bundle already names the
chosen problem; where one exists, point to it rather than reframing it here). IT IS NOT a project
brief (which asks a named approver for authority to start finding out whether and how to proceed;
this document asks for no authority, and names a concept already chosen). IT IS NOT a business case
(no source read orders the two against each other; a brief may hand on a concept the case later
weighs as one option, at medium-low confidence). IT IS NOT a specification, a product design
specification, or the PRD (Ignitec's own line draws it cleanly, "The commercial considerations will
come later when you write your product design specification," and UXPin agrees, "A design brief
outlines what designers must create, while the specifications define specific details"). IT IS NOT
the Shape Up pitch (catalog entry 45, unbuilt): a pitch arrives shaped, "A problem without a
solution is unshaped work," and exists to be bet on, "The purpose of the pitch is to present a good
potential bet"; this document hands over a concept and asks for no bet. IT IS NOT a Design Sprint
brief (Google Ventures' own page names a five-day process and publishes no separate Sprint Brief).
IT PRECEDES a creative brief where a team already writes one: "In many design workflows, the
creative brief informs the design brief, ensuring visual decisions support broader project goals."
RECORDING APPROVAL IS NOT GRANTING INVESTMENT BACKING: The Handoff section may record that design
was approved, by whom and when; it is never the record that authorizes a project or its budget. And
MANY TEAMS WRITE NONE OF THIS AT ALL: "in many of the interviews the projects discussed started
without a design brief." See design-brief_companion.md sections 6 and 8.
THIS DOCUMENT IS REVISED WHILE DESIGN RUNS, UNLIKE MOST OF ITS `discovery-docs` SIBLINGS. "design
briefs are seldom fixed, static documents, but rather, they are often dynamic and evolve as the
project progresses," and a brief "should be used as a validation tool periodically throughout the
project when making key decisions." It is finished when the design work it hands off is done, not
on a standing cadence. See design-brief_companion.md section 2.
HOW TO FILL THIS IN
1. Read the comment under each heading: WHAT it wants, WHY it matters (with a pointer into
design-brief_companion.md), guiding questions to ASK, a GOOD and a WEAK example, and the TRAP to
avoid.
2. Replace each {{placeholder}} with your content. Name no screen, no flow, no requirement, and no
project budget or authorization anywhere in this document; those belong to a later document.
3. If a section does not apply, write "N/A" and one line of why, rather than deleting it.
4. Before you hand this to the people who will design from it: self-grade against
design-brief_guide.md, then DELETE every HTML comment. They are guidance, not content.
-->
# {{concept_name}} Design Brief
## The Challenge
<!-- WHAT The chosen problem, restated for the people who will design it, and what a good outcome
would change. Points to a problem statement and to success measures if either already
exists, rather than restating them.
WHY The Design Council's own phrase anchors this section: a brief "clearly defines the
challenge based on these insights." Jones and Askland describe the same job from the
reader's side: a brief exists "to help the designer to understand the problem by
defining the objectives and parameters of the project toward generating the most
appropriate solution." Kuse's own definition agrees: a brief "defines the problem a
design needs to solve, the context in which it exists, and the constraints that shape
the solution." Deep dive: design-brief_companion.md section 3 (Anatomy > The Challenge).
ASK What is the chosen problem, in the fewest words that still say it accurately? What would
a good outcome change for the people who have it? Does a problem statement already
exist for this problem? If measures of success already exist somewhere, where do they
live?
GOOD "Riders of the regional bus system have no way to see a delay until they are already
standing at the stop, and the October rider survey named this the top reason for missed
transfers. A good outcome lets a rider learn about a delay before they leave home.
Problem statement: see the Delay Visibility problem statement, dated 2026-03-02. Success
measures: see that document's success-measures section."
WEAK "Build a notification feature for delays." (names a solution instead of restating the
problem, and gives a designer nothing to design against)
TRAP Restating the problem in language that already describes a specific solution. If the
sentence names a screen, a button, or a channel, it has moved from the challenge into
the chosen concept, a section below. -->
{{challenge}}
- What a good outcome would change: {{good_outcome}}
- Problem statement already written, if one exists: {{problem_statement_reference}}
- Where success will be measured, if already defined elsewhere: {{success_measures_reference}}
## Who It Is For and What We Learned
<!-- WHAT Who the design serves, named specifically enough to design for, and the one research
insight the challenge above rests on.
WHY Kuse's guide gives users their own numbered step, "4. Describe Users and Real Use
Contexts." The Design Council frames the insight half of the job directly, closing on
"understanding how user needs and the problem align." Y Combinator asks the evidence
question plainly: "Have you done any user observations? If yes, will you be able to
share the process and the findings?" Deep dive: design-brief_companion.md section 3
(Anatomy > Who It Is For and What We Learned).
ASK Who does this design serve? Does an existing persona already describe this group? What
is the single research insight the challenge rests on?
GOOD "Commuters who board at an unstaffed stop, mostly during the morning and evening peak.
Insight: the October rider interviews found that riders check a transit app before
leaving home, but stop checking once they are already walking to the stop, so a delay
that appears only in-app after departure is invisible exactly when it matters most."
WEAK "Our riders." (no group named specifically enough to design for, no insight stated)
TRAP Re-running the whole research study in this section. One insight, stated in a sentence
or two, is enough; the rest belongs to the research itself, not to this brief. -->
- Who the design serves: {{who_it_serves}}
- Existing persona, if one already describes this group: {{persona_reference}}
- Research insight the challenge rests on: {{research_insight}}
## The Chosen Concept
<!-- WHAT The candidate concepts weighed, at the level of the kind of answer; the one chosen and
why; and what the chosen concept deliberately leaves out.
WHY The Eleven Lessons report places the moment: "the Define stage would end with final
sign-off of the concept." What the concept leaves out is this section's best-sourced
element: Heap's own template (cited here for its field name only, never for its
solution-level content) carries a dedicated field for it, "Not Doing," and Basecamp's
pitch carries the same move under a different name: "shaped work indicates what not to
do. It tells the team where to stop." Deep dive: design-brief_companion.md section 3
(Anatomy > The Chosen Concept), section 6.
ASK What candidate concepts did the team weigh, at the level of the kind of answer? Which
one was chosen, and why that one over the others? What does the chosen concept
deliberately leave out?
GOOD "Candidates weighed: a home-screen widget showing the next scheduled delay, set aside
because most riders do not add a transit widget and support calls showed riders check
inside the app already. Chosen: a notification triggered by a schedule deviation on the
rider's saved routes, delivered through the channel the rider already uses for the app.
Chosen because it reaches a rider before departure, the moment the insight above names
as the one that matters, and because it needs no new habit from the rider. Leaves out:
the exact wording, how far in advance it fires, and whether it appears on a lock screen
or inside the app alone; those are for the design work to resolve."
WEAK "A push notification that says 'Bus 14 delayed 6 minutes' and appears on the lock screen
with a snooze button." (names exact wording and a specific interface element, how the
concept works rather than what kind of answer it is)
TRAP Writing the chosen concept at the level of a shaped solution. If the sentence says what
a screen shows, what a button does, or how a flow proceeds, it has crossed from a
concept into a specification; that content belongs to the document this brief hands off
to, never here. -->
- Candidates weighed, and why each was set aside: {{concept_candidates}}
- Chosen concept: {{chosen_concept}}
- Why this one: {{why_chosen}}
- What this concept deliberately leaves out: {{concept_excludes}}
## The Handoff
<!-- WHAT Who will design from this brief and what they receive; who approved design to begin and
when; how the brief stays current while design runs; who decides when feedback on the
design conflicts; and which document takes over once the concept is specified.
WHY Kaninsky states the audience-alignment job directly: his brief exists "to get designers,
product managers and software engineers on the same page before any research and
design activities even start." Recording approval is this section's clearest sourced
content: Kaninsky's template asks "Who is the ultimate decision-maker (sign-off)?," and
the Eleven Lessons report places the moment this bundle's own record points back to,
"the Define stage would end with final sign-off of the concept." Recording approval is
not the same as granting it: the same report describes what the sign-off actually buys,
"the corporate and financial backing to the development of one or more concepts that
have addressed the initial problem." That backing is the investment decision the
`discovery-docs` family contract excludes from every `define` member; this section may
record that design was approved, by whom and when, and it is never the record that
grants the backing itself. Which document takes over is this bundle's own POSITION:
Ignitec names the boundary cleanly, "The commercial considerations will come later when
you write your product design specification," and UXPin agrees, "A design brief outlines
what designers must create, while the specifications define specific details." One named
team skips that step: at Heap, once its own review clears (its own solution sense, cited
for this one fact alone), "the design brief allows engineers to start scoping and
building at least the back end." Who settles a conflict in design feedback is supported
but unhomed in any single published template: Kuse's guide asks "Who approves final
designs" and "How conflicts will be resolved," and Figr names an "Approval path: Who
decides when feedback conflicts." Deep dive: design-brief_companion.md section 3
(Anatomy > The Handoff), section 6.
ASK Who will design from this brief, and what exactly do they receive? Who approved design
to begin, and when? How will this brief stay current while design runs, and does that
mean reviewing the brief itself or reviewing the design as it proceeds? Who decides when
feedback on the design disagrees? Which specific document takes over once the concept is
specified?
GOOD "The in-house design team designs from this brief, receiving this document plus the
October rider-interview notes. Approved by the Head of Product, 2026-03-10. This brief
is updated, not the design itself, whenever the challenge or the chosen concept
changes; design review happens separately, in the team's own weekly critique. The
design lead settles any disagreement in rider feedback. The design specification takes
over once the concept is designed."
WEAK "Design will figure it out, and we'll check in eventually." (no named team, no approver,
no date, no named decider, no named next document)
TRAP Treating the sign-off recorded here as the decision that funds or authorizes the
project. The brief may record that design was approved, by whom and when; it is never
the record that grants a project its backing. -->
- Who will design from this brief, and what they receive: {{design_team}}
- Approved by, and when: {{approver}}, {{approval_date}}
- How this brief stays current while design runs, and which review that means: {{revision_process}}
- Who decides when feedback on the design conflicts: {{feedback_decision_owner}}
- What takes over once the concept is specified: {{next_document}}

The reasoning, the history and every source, in the repository:

  • Companion - the long-form argument: why these sections, where the sources disagree, and what the bundle refuses to claim
  • History - what changed in this bundle, and when
  • Research log - every source consulted, with what each one actually supports
  • Catalog metadata - the machine-readable record this page is generated from

Catalog record: 7 sections across 1 format(s), methodology design thinking / design management, typically owned by PM / Design.