Skip to main content Scroll Top

Write a Useful Website Brief for a January Project

Photo: UX Indonesia / Unsplash

A January website project can start more clearly if December’s brief describes the problem before the preferred solution. A request for a modern homepage is difficult to evaluate. A request to help customers distinguish two services and complete the correct inquiry gives the team something concrete to investigate.

Gather a small set of examples from the current site. Record the public pages, the confusing wording and the customer tasks affected. Use approved, anonymized inquiry patterns rather than copying personal messages into the brief. Distinguish an observed problem from a theory about what caused it.

Advertisement

Define what a successful change would let a person do. Include operational limits such as who maintains the content, which systems must remain connected and when reviewers are available. If photography or copy needs to be created, say so. A design brief should not quietly assume that a new image library or complete service description already exists.

End with the decisions the first project meeting needs to make. Those might include scope, priorities, content ownership and how the work will be checked. Keep aspirational references as references, not instructions to copy another company. A clear brief gives specialists room to solve the real problem while making it easier for the business to judge whether the solution is useful.

A practical review

A before-and-after comparison can be valuable when the context is explained. Use comparable views and identify what changed in the content or interaction. Do not crop the earlier version unfairly to make the new one look better. If the project included several phases, state which phase the example shows. A customer’s approval of a screenshot does not automatically cover every commercial detail in the surrounding story, so review both together. Keep the approved case-study text with the project record. When the live site changes later, the historical example can remain useful if its date and scope are clear. The reader should understand a particular piece of work, not be invited to infer a sweeping result from a polished image.

Before you finish

  • Describe the customer problem before specifying a visual treatment.
  • Separate observations from assumptions about their cause.
  • Name content owners and existing-system constraints.
  • List the decisions needed to start the project responsibly.

Quick check

How much did you catch? Tap a question to see the answer.

1. What belongs at the start of a January website brief?

Answer: Describe the customer problem before specifying a visual treatment.

Advertisement
2. How should the brief distinguish evidence from guesses?

Answer: Separate observations from assumptions about their cause.

3. Which people and constraints should the brief identify?

Answer: Name content owners and existing-system constraints.

A Brief Structure That Keeps the Problem in Front

A useful brief can fit on two pages. It does not need polish; it needs clarity. The following headings work for most small-business website projects:

  1. The problem in one paragraph. What customers are struggling to do, and how the business knows.
  2. Examples. A short list of pages, links or screenshots showing the problem, with a sentence on each.
  3. Who is affected. The type of visitor or customer task, described by what they need rather than who they are.
  4. What success would allow. Written as actions: “A visitor can tell which of our two services fits them and reach the right form.”
  5. Constraints. Systems that must stay connected, people who will maintain the content, reviewer availability, any fixed dates.
  6. Existing materials. What copy, images and brand guidance already exist, and what will need to be created.
  7. Open questions. Anything the business has not yet decided.

A worked example

Consider a home-services company whose December brief begins: “We want a fresh, modern homepage.” After rewriting, it begins: “Callers often book our standard inspection when they actually need our repair assessment, and staff spend time rebooking them. We think the two services look too similar on the site.” The examples section then lists the two service pages, the shared form and a few anonymized descriptions of misdirected requests. Success is defined as visitors choosing the right service before they call. The constraint section notes that the booking system cannot be changed this quarter. That brief gives the designer and writer a real problem to solve, and it gives the owner a clear way to judge the result.

Separating Observations From Theories

One of the most valuable habits in a brief is labeling the difference between what someone has seen and what they think it means. Observations are things like “Three people this month asked whether we serve their town, which is listed on the page.” Theories are explanations: “The service area is too far down the page.” Both belong in the brief, but under separate labels. Specialists can then test the theory instead of assuming it, and may find a different cause entirely.

Mistakes That Weaken a January Brief

  • Prescribing the solution. “Add a slider to the homepage” closes off better options before anyone has studied the problem.
  • Copying private messages. Summarize patterns from inquiries rather than pasting customer emails, names or contact details.
  • Hidden content assumptions. If the new pages will need new photographs, service descriptions or pricing explanations, the brief must say who will produce them.
  • Reference sites as specifications. Sharing a site you admire can explain a feeling or a structure, but the brief should say what you like about it rather than asking for a copy.
  • No decision maker. Name the person who can approve scope and settle disagreements.

Questions for the first meeting

  • Which problem matters most if only one can be solved first?
  • What will be measured or checked to show the change helped?
  • Who writes and maintains each piece of content after launch?
  • When are reviewers realistically available in January?
  • What is explicitly out of scope for this project?

Why write it in December?

The weeks before a holiday break are often when the problems are freshest. Staff have just handled a busy season and remember which questions came up again and again. Writing the brief now, even roughly, captures that knowledge before it fades over the break. In January, the brief only needs to be checked and refined rather than reconstructed from memory, and the first project meeting can begin with real examples on the table instead of a blank page.

Fenway Web is coming to iPhone

Client news, portfolio work and the Fenway Journal in one app for iPhone, iPad and Apple Watch.

See Fenway Web

Latest stories

View all
Our clients