
Adrian Jordan
-
2 min Read
Overview
A good brief does not need to be long. It needs to answer a few honest questions: who the product is for, what problem it solves, what success looks like and what cannot change. When those answers are written down and agreed, design decisions stop being a matter of taste and become a matter of fit.
I usually draft the brief together with the client in a short workshop. We cover goals, audience, constraints, existing assets, deadlines and the people who will approve the work. The result fits on one page, and it becomes the reference point every time a new idea comes up.
A clear brief turns opinions into decisions everyone can agree on
Who the product is really for.
The one problem it must solve first.
How success will be measured.
What is fixed and what is flexible.
Adrian Jordan
Questions worth asking early
Some questions feel awkward at the start, such as who has the final say or what the budget really allows. Asking them early is kinder than discovering the answers halfway through. A clear decision maker and a realistic scope protect both the timeline and the quality of the final work.


Using the brief every week
A brief is only useful if it is used. I bring it to every review and check new ideas against it before discussing details.
When a request does not fit the brief, we either update the brief together or park the idea for later.
Write it once, refer to it often.



