Discovery brief
A one-page brief filled in with your sponsors before kickoff, covering context, users, goals, outcomes and who decides.

- Time
- 30–45 min, self-paced
- People
- 2–5, core team
Overview
The first artifact of a discovery and the one everything else is measured against. One page, filled in with the project sponsor before anyone gathers, covering what the business thinks the problem is, who it is for, what success looks like, and who gets to decide. The board is blunt about why it exists: lack of shared understanding from the start is one of the key causes of projects going off course, because everyone at the table has a different mental image and each assumes the person next to them shares it.
When to use it.
Before any kickoff. Write it before research starts, so later you can see which of these assumptions survived.
Who to involve.
The sponsor, plus everyone who will be closely involved — especially while the problem statement is being formed. Two to five people. Circulate it for comment rather than presenting it.
Effort.
Medium prep Medium engagement Allow 2–4 days of lead time for comments, then book the pre-framing session at least a day ahead and budget 1.5 to 2 hours for it.
Outcomes.
A shared understanding of the problem context, goals, constraints and expectations — and, critically, named decision-makers with their level of involvement recorded. The Discovery Introduction lists seven outcomes pre-framing should deliver, and this brief carries most of them.
Recommendations.
Write the problem as the business sees it, in their words, not yours: you are recording a starting position, not correcting it. Be specific about constraints — a release date, a platform, a regulatory review — because vague ones resurface late and expensively. And ask people to disagree with it. Silence is not agreement; a marked-up brief is.
How to run it
Take a first pass, 2–4 days before kickoff
Draft it yourself rather than waiting for a meeting. You may already have something similar in hand; this gives you one page instead of several.
Share the draft for reaction
Share it with the product team so they can answer any missing questions and review what you have written, rather than you commenting on it alone.
Answer the four groups of questions
Work through the board’s four groups — project background and business context, the user and customer context, business goals, and expected outcomes — in order.
Name the steering committee
Ask the product manager to draft this as a first pass: the head of the steering committee, each core stakeholder and each core team member, with name, role and department, and whether they should be involved. The head of the steering committee is the key decision-maker, and the board is explicit about why that matters — it is what lets you move forward when a design conflict arises.
If the product manager cannot name it yet, uncover it instead through a Stakeholder mapping exercise as part of the pre-framing session.
Gather the insight artefacts
Alongside the brief itself, pull together a third input before the pre-framing session: a concise view of what the team already knows — key problems, user pain points, early patterns, data signals, and the gaps still to validate.
Schedule the pre-framing session, at least a day ahead
Put the completed brief and the Discovery Introduction in the invite so people can read them beforehand.


