Top of page
Skip to content
orlo.
Design / 5 min read

Clarity before pixels: writing a useful website brief

A useful brief gives a project direction without trying to solve every design decision in advance.

Maya Ellis · Co-founder & Design Director

· 5 min read

Blank sheets, a notebook, and pencils on a sunlit desk

A website project often starts with a list of pages, a few reference sites, and a deadline. Those are useful details, but they don’t yet explain what the website needs to do.

A good brief connects the business, the audience, and the decisions ahead. It gives the team enough context to ask better questions and make purposeful choices. You don’t need a polished presentation. A few clear answers are a better starting point.

What should this website change?

Start with the reason for the project. Perhaps your offer has changed, the current site is difficult to update, or visitors don’t understand what you do. Describe the situation in plain language before writing down the solution.

Choose one primary outcome. “Help prospective clients understand our services and make an enquiry” gives the team more direction than “make the site feel modern.” Supporting goals can sit underneath it.

A useful brief defines the problem. It leaves room to discover the answer.

Be specific about who it is for.

“Everyone” is difficult to design for. Describe the people most likely to use the site, what brings them there, and what they need to understand before taking the next step.

Think about the questions they arrive with. Are they checking your experience, comparing services, looking for pricing, or trying to complete a task? The answers help establish the hierarchy of the page.

Describe what the site needs to do.

List the important journeys before listing features. A portfolio may need visitors to find relevant work and understand your role. A product site may need to explain a workflow and help someone request a demo.

  • The main actions visitors should be able to take
  • The information they need before taking those actions
  • Forms, booking tools, or integrations involved
  • Who will manage content after the site is live

This is also the place to mention technical constraints. Existing systems, accessibility needs, content ownership, and an agreed launch environment can affect the scope well before development begins.

Separate what matters now from what can wait.

A first launch does not need every future idea. Split requirements into essentials for launch, useful additions, and later possibilities. A smaller coherent experience is easier to review than a larger collection of unfinished parts.

Be open about timing and budget. They help the team propose a realistic approach, identify tradeoffs, and decide whether the work should happen in stages.

Geometric blocks arranged into a modular structure
A clear structure gives each piece a useful place in the whole.

Know what you already have.

Design depends on content. Share your current copy, brand assets, photography, product information, and case studies—even if they need work. Make the gaps visible rather than treating them as a problem for later.

Agree who will create, approve, and supply each part. That simple conversation can prevent a beautifully designed layout from waiting weeks for the words and images it needs.

Make feedback part of the plan.

Identify the people making decisions, the person coordinating feedback, and the points where approval is needed. Consolidated feedback helps the team understand the direction instead of reconciling conflicting comments.

A useful brief is a shared starting point, not a rigid contract with every pixel. Revisit it when the scope changes, and keep the agreed goal visible as the work develops.

Your brief can start with five answers.

  • What are we trying to achieve?
  • Who does the website need to help?
  • What must be included at launch?
  • What content and constraints already exist?
  • Who is involved, and how will we decide?

If you can answer those questions, you have enough to begin a useful conversation. The rest can be shaped together.

KEEP READING

A few more ideas to take into your next project.

LET’S BUILD TOGETHER

Have something in mind? Let’s make it happen.

Tell us about your idea, your goals, and where you want to go. We’ll help you work out the next step.