A website project often begins with a feeling: the current site no longer reflects the business. Perhaps the services have changed, the content has become difficult to manage, or visitors cannot find a clear next step. That feeling is a good reason to start a conversation. It is not yet a direction for design.
The brief turns that starting point into something a team can work with. It should make the important questions visible without pretending that every answer is already known. You do not need a technical specification or perfectly polished copy. You do need a little honesty about the problem, the people and the practical limits around the work.
THE BRIEF
Start with the change, not the pages.
Before writing ‘Home, About, Services, Contact’, describe what the website should help the business do differently. A team entering a new market has a different problem from a team fielding too many unsuitable enquiries. Both may ask for a new website, but the content, navigation and calls to action should answer different needs.
Separate the reason for the project from the proposed solution. ‘People cannot understand our three service lines’ is a useful problem. ‘We need a carousel’ is an idea that still needs to earn its place. The first invites the team to investigate; the second can close the conversation too early.
For example, ‘Our buyers keep asking which service covers an existing website. We want them to compare the options and know who to contact about maintenance.’
THE BRIEF
Name the person on the other side.
‘Everyone’ is rarely a helpful audience. Think about who needs to make a decision and what they bring to the page. Are they comparing partners, checking a recommendation, looking for technical reassurance or returning to find a specific document? Those starting points change what deserves attention first.
Write down the questions that person needs answered. What do you do? Is it relevant to me? What evidence can I inspect? What happens if I get in touch? Use real questions from sales calls, support conversations or your team’s experience where possible. Treat the rest as assumptions to investigate, rather than facts to design around.
THE BRIEF
Put the project’s priorities in order.
A brief becomes more useful when it makes trade-offs visible. Distinguish the things that must work at launch from improvements that can follow. A clear service explanation and a dependable enquiry route may matter more than a complex animation. In another project, an interactive product experience may be central to the offer.
Keep the first list short enough to guide decisions. For each priority, say why it matters and who will judge whether it works. When a new idea appears, compare it with those priorities. This gives the team a way to discuss scope without reducing every conversation to personal taste.
- Essential: the site cannot do its job without it.
- Valuable: it improves the experience, but its timing is flexible.
- Exploratory: it needs evidence or a small test before a commitment.
THE BRIEF
Bring the content into the room early.
Design decisions depend on the content. Service names, product information, project images and company details all influence the shape of a page. If they arrive after the layouts are approved, the design may be solving a problem the real content does not have.
An inventory is enough to begin: what exists, what is current, what needs rewriting and what is missing. Give each item an owner. Flag anything that needs permission, legal review or a client’s approval. For visual references, explain what you like about them: the reading rhythm, the clarity of the navigation, or the way a product is demonstrated. A reference with a reason is more useful than a reference alone.
THE BRIEF
Put the practical constraints on the table.
A useful brief makes room for the unglamorous details. Existing domains, search traffic, content systems, payment tools and internal approval processes can shape the work as much as the visual direction. Name the systems the website must connect with and the people who can provide access or explain how they work.
Share the budget range and the reason behind a target date. A launch tied to an event is different from a preferred internal deadline. Be clear about accessibility needs, languages and who will maintain the site. These are not obstacles to creativity; they help the team choose an approach that can actually be delivered and looked after.
THE BRIEF
Decide what useful progress looks like.
Success should relate to the problem at the beginning of the brief. If visitors struggle to understand the offer, review whether the new structure answers their questions. If the team struggles to update content, include a realistic publishing task in the review. A business goal may need measurement after launch; a usability issue may be testable much earlier.
Avoid choosing a number simply because it looks precise. Record the current position where evidence exists, say what you intend to observe and agree how the findings will influence the next iteration. Leave room for external factors: a new website alone cannot control demand, seasonality or the quality of an offer.
THE BRIEF
Agree how decisions will be made.
A brief is also an agreement about working together. Identify who contributes, who approves and who brings feedback into one coherent response. Give the team access to the people closest to the problem, while keeping the route to a decision clear.
Review work against the brief before reviewing personal preferences. ‘This page does not explain the difference between our services’ gives a designer something to resolve. ‘Make it more premium’ needs a conversation about what that means. Specific feedback does not remove creative freedom. It gives that freedom a useful direction.
KEEP THIS CLOSE
Your website brief checklist.
Before sharing the brief, check that it covers these six points.
- The business change the website should support.
- The primary audience and the questions they need answered.
- Launch priorities, with a reason for each one.
- Available content, missing material and named owners.
- Budget, timing, systems and maintenance responsibilities.
- How progress will be reviewed and who makes decisions.
A brief can be short. Record what you know, flag the questions still open and decide who can answer them. That gives the team enough direction to start designing and a reference when the next decision comes up.