What it is
A short document capturing the project’s purpose, audience, goals, scope, constraints, timeline, and definition of success. It is the shared agreement the team designs against.
When to use it
At project kickoff, during Initiate, once there is enough context to state intent but before design work begins.
Why (value)
Reduces churn and scope creep by making expectations explicit up front. Gives new contributors instant context and gives the team a reference for saying no.
How to run it
- Collect goals, audience, constraints, and success measures from stakeholders.
- Draft the brief on a single page: background, objectives, scope, out-of-scope, constraints, success metrics.
- Review with stakeholders and resolve disagreements now, not later.
- Circulate and keep it accessible throughout the project.
Inputs and outputs
- Inputs: Stakeholder goals, business context, constraints, any prior research.
- Outputs: An agreed, concise design brief.
Time and effort
Low. A few hours plus a review cycle.
Evidence and limitations
A planning artifact, not evidence. Its claims about user needs should be flagged as assumptions until validated. See Evidence and limitations.
Tips and pitfalls
- Keep it to a page, longer briefs go unread.
- Be explicit about what is out of scope.
- State how success will be measured, not just what the goal is.
Variations
Creative briefs, project one-pagers, PRDs (heavier), lean canvases (leaner).
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- Problem statements — A crisp, shared articulation of the problem worth solving, before anyone jumps to solutions.
- Design principles — A short set of shared values that guide decisions and resolve trade-offs consistently.
- Roadmapping — Sequence outcomes and work over time to align the team on where things are heading and why.
