Foldwren

How to write a web design brief

What to include in a web design brief, examples of useful versus vague instructions, and a short outline you can copy and fill in.

A web design brief is a short document that tells a designer what your business does, who the website is for and what you need it to achieve. Two pages is plenty. It doesn't need design language, and it doesn't need to describe what the site should look like.

A decent brief gets you more accurate quotes, fewer rounds of revisions and a site that suits the business. A missing brief gets you a designer's best guess.

What a brief is for

The brief does three jobs. It gives designers enough information to quote properly, so you can compare like with like. It forces you to make decisions early, when changing your mind is free. And it becomes the reference point later, when someone asks "should we add this?" and the brief can answer.

Notice what isn't on that list: telling the designer how to design. Your job is to describe the problem. Their job is to propose the solution.

What to include

About the business

What you do, where, and for how long. Two or three paragraphs. Include what sets you apart, in plain terms. "We're the only mobile dog groomer covering the peninsula" is useful. "We're passionate about quality" is not.

Why now

What prompted this? A new business, a tired old site, a change of direction, enquiries drying up. The reason shapes the whole project.

Who the customers are

Describe two or three typical customers. Their age, what they are looking for, what worries them, whether they are likely to be on a phone. A builder's brief might say: "Homeowners in their forties planning a first major renovation, anxious about cost blowouts and unreliable trades."

What the site must achieve

One or two measurable goals. More quote requests, online bookings instead of phone calls, fewer calls asking about hours and parking.

Pages and features

Your best guess at the page list, plus anything the site must do: online booking, payments, a gallery, an enquiry form, a map. Mark each feature as essential or nice to have.

Content

Who is writing the words? Who is supplying photos? Be honest. Content is the most common cause of late projects, so a designer needs to know if you have it ready, need help, or haven't thought about it.

Likes and dislikes

Three or four websites you find easy to use, with a sentence on what you like about each. They don't have to be in your industry. One or two you dislike is just as helpful.

Practical details

Budget range, deadline and the reason for it, who makes the final decision, what brand material exists (logo files, colours, fonts), and what you have now (domain name, hosting, email).

Useful versus vague

The difference between a brief that helps and one that doesn't is nearly always how specific it is. Some comparisons:

Goals

  • Vague: "We want a modern website that stands out."
  • Useful: "We want more enquiries for bathroom renovations and fewer for small repair jobs."

Audience

  • Vague: "Our customers are everyone."
  • Useful: "Mostly women aged 30 to 55 booking for themselves or a parent, usually on a phone, usually in the evening."

Style

  • Vague: "Clean and professional, but with a wow factor."
  • Useful: "Calm and uncluttered. Our clients are often in pain or stressed. Nothing flashy. We like how the example clinic site puts booking at the top of every page."

Features

  • Vague: "We might want a shop at some point, and maybe a blog."
  • Useful: "No shop at launch. We plan to sell gift vouchers within a year, so please allow for that."

Budget

  • Vague: "Not sure, just give us a price."
  • Useful: A range. Any range. A designer can tell you what is realistic within it, and you avoid quotes that are three times what you can spend.

People often hold back the budget for fear of being charged the maximum. In our experience, sharing it gets you better advice. A good designer will tell you what the money can sensibly buy, and what to leave for later.

Common mistakes

  • Designing in the brief. "The logo should be top left with a blue bar and three boxes underneath." Describe what you need and why, and let the designer propose the layout.
  • Writing by committee. A brief that tries to satisfy five people's wishes ends up contradicting itself. Have one person write it and one person approve it.
  • Leaving out the awkward parts. If your business partner hates green, or the last web project ended badly, say so.
  • Listing every feature you have ever seen. Each one adds cost. Rank them.

A short outline to copy

Fill this in with a few sentences under each heading and you will have a better brief than most designers ever receive.

  1. The business. What we do, where, and what makes us different.
  2. Why we need this now. What prompted the project.
  3. Our customers. Two or three typical people and what they want.
  4. Goals. The one or two results that would make this a success.
  5. Pages. Our draft page list.
  6. Features. Essential, and nice to have.
  7. Content. What exists, what needs writing or photographing, and who will do it.
  8. Sites we like and dislike. With a sentence on why.
  9. Brand material. Logo files, colours, fonts, existing print material.
  10. What we have now. Current site, domain, hosting, email, and who controls each.
  11. Budget range.
  12. Timing. Ideal launch date and any fixed deadlines.
  13. Decision maker. One name.

Send the same brief to each designer you are considering. Pay attention to the questions that come back. A designer who asks sharp questions about your customers and goals is usually a better bet than one who replies with a price and nothing else.

Your order