Explain why the site must change now
A useful brief starts with business context. Describe the change that made the current site insufficient: a new market, a more focused offer, a longer sales cycle, weak lead quality, difficult content maintenance, or a product that the old structure cannot explain.
Avoid leading with visual preferences. Design direction matters later, but the team first needs to understand the decision the website should improve. This gives every page and component a reason to exist.
- What has changed in the business or audience?
- Which commercial or communication problem should improve?
- What must remain stable during migration?
Describe audiences through their questions
Job titles alone do not reveal what a visitor needs. For each priority audience, document their situation, what they already know, their main concern, the evidence they trust, and the next action they can realistically take.
This question-based view helps teams avoid generic pages that try to persuade everyone at once. It also reveals when one audience needs a dedicated journey, such as a service buyer, implementation partner, applicant, or existing customer.
Inventory content and proof before layout
Many redesigns stall because layouts are approved before the organization knows what it can truthfully say. List existing pages, useful material, outdated claims, evidence that can be published, and gaps that require interviews or subject-matter review.
Proof should be specific and verifiable. If client names or metrics cannot be disclosed, use process artifacts, representative examples with clear labeling, technical detail, or direct explanations of how decisions are made. Never turn anonymity into invented precision.
- Assign an owner and approver to every high-value page.
- Identify claims that require evidence or legal review.
- Plan original visuals instead of treating stock photography as proof.
Set experience requirements before visual design
The brief should state the journeys the site must support and the quality bar for those journeys. Include navigation expectations, forms, mobile behavior, content editing, accessibility, performance budgets, search metadata, analytics, and integrations.
These requirements shape the information architecture and component system. Adding them after design usually creates compromise: oversized imagery, unclear focus states, fragile page templates, or tracking that cannot answer the original business question.
Define success and post-launch ownership
Choose measures that match the site's purpose, such as qualified enquiries, completion of a priority journey, search visibility for relevant topics, or fewer content-maintenance bottlenecks. A traffic increase by itself may not indicate a better website.
Name the people responsible for content quality, technical maintenance, analytics review, and future releases. A website is an operating product. The redesign is complete only when the organization knows how it will keep the experience accurate and useful.
Editorial note
This article provides general product and engineering guidance. The appropriate decision depends on your users, systems, risk, evidence, and operating context.