Plan
Write a project brief
Agree what the project is trying to learn and for whom.
How to do it
- Write the problem in one or two sentences.
- List what you want to learn, not what you want to build.
- Set the scope: who is in, who is out.
Tip. A brief that names a measurable symptom (like "repeat orders drop after week three") makes every later step easier to judge.
What you need
Nothing: this is a starting point.
What you get: Brief
A brief template has these sections:
- Context
- Goals
- Scope
Where it fits
- Discover (Double Diamond): Learn what is really going on, before jumping to answers.
What to do next
- Frame research questions
- Write an interview script
- Compare competitors
- Scan the web
- Ideate concepts
- Build a prototype
- Build a survey
Templates that use it
- Evaluative study: Does this design work for the people who will use it?
- Exploratory study: We don’t know the problem well yet: why do people do what they do?
- Double Diamond: A whole project, from understanding a problem to a tested answer.
- Assumption-led (Lean UX): You already have an idea. What could sink it?
- Continuous discovery: A product team learning every week towards one outcome.
- Jobs to be done: Why do people start using, switch to or leave a product like yours?
- Design Thinking: Empathize, define, ideate, prototype and test, in the classic five modes.
- Design Sprint: Five days from a big question to a prototype tested with real people.