A good brief does not need to be long. It needs to help everyone understand what you are trying to achieve and what a useful result would look like.
Start with the outcome
Instead of beginning with a list of features, describe the change you want. For example: “Help customers understand our services and send an enquiry.” That gives a team something to design around.
Explain who it is for
Tell the team about the people who will use the result. What do they already know? What should be easy for them? Are they likely to use a phone, a laptop or both?
Separate the essentials from the extras
List what must be included for the first version. Keep useful additions in a separate list. This makes it easier to agree a scope and discuss trade-offs.
- Your goal and intended audience.
- The work or files you expect to receive.
- Examples that help explain your preferences.
- Your preferred timing and available materials.
- A budget, if you have one, or a request for guidance.
Agree the next step
Before work starts, confirm the deliverables, review process and any payment terms with the team. A preferred date is a starting point for discussion, not a confirmed delivery promise.
The Obisuj Digital project planner can help you organise these details into a brief you can download or send to our admin team for review.