Start with the problem, not the screens
Many briefs begin with a list of screens or a reference to an app the writer likes. That is useful context, but it fixes a solution before the problem is clear. Write one paragraph that answers three questions: what goes wrong today, who notices it, and what it costs in time, errors or missed work. If you cannot answer the last question yet, say so; finding out is part of analysis.
Then list what is out of scope. A short out-of-scope list prevents more misunderstandings than a long feature list.
Name the people, not only the departments
Write down the roles that will use the software and what each one is trying to achieve. A warehouse lead and a buyer may work in the same team but need very different screens. Note who decides when two roles want different things.
Write stories with a goal
The GOV.UK Service Manual describes user stories as three parts: the actor, the need and the goal, often written as As a… I need… so that… (GOV.UK). The goal is the part most often skipped and the one that matters most, because it shows whether a feature really solves the problem.
Bill Wake's INVEST checklist is a quick quality test: a good story is independent, negotiable, valuable, estimable, small and testable (xp123.com). If a story fails the testable check, add acceptance criteria.
Add acceptance criteria
Acceptance criteria are a checklist phrased as it is done when…. They turn opinions into something that can be shown. Three to five criteria per story are usually enough to start a conversation; the developer will ask for more where needed.
Vague The system should be fast and easy to use.
Checkable It is done when a member can book a free room from the grid in one step, using keyboard only.
List constraints separately
Constraints are not features. Keep them in their own list: laws and contracts that apply (for example the Singapore PDPA if you handle personal data), systems the software must connect to, where it may be hosted, accessibility targets and who will operate it afterwards. The GOV.UK discovery guidance separates hard constraints, such as legislation, from soft constraints, such as processes that can be changed (GOV.UK).
Bring evidence, not volume
Attach the spreadsheets, paper forms, e-mail templates and exports people use today. They show real data and real edge cases. A ten-page document of assumptions is less useful than one real form with handwritten corrections on it.
A short checklist for your brief
- One paragraph on the problem and its cost.
- Roles that will use the software and who decides.
- Three to ten user stories with goals.
- Acceptance criteria for the most important stories.
- Constraints: legal, technical, hosting, accessibility.
- What is out of scope.
- Examples of current forms, files and exports.
Sources
- GOV.UK Service Manual, Writing user stories (updated 23 May 2016)
- Bill Wake, INVEST in Good Stories, and SMART Tasks (2003)
- GOV.UK Service Manual, How the discovery phase works (updated 21 June 2021)
Sources checked on 17 November 2026.