Back to Blog

A Practical Website Redesign Brief for Your Business

Super Admin · 2 min read · November 2, 2026

Original website planning and interface illustration by OPEN CODE

Define the problem, content and customer journeys before choosing a new visual direction.

Start with the problem, rather than a page count

A redesign brief is most useful when it explains what the current website makes difficult. Perhaps visitors cannot distinguish your services, the product catalog is difficult to maintain, or enquiries arrive without enough context. Describe the situation in plain language. Then identify the people affected and the action you want to make easier. A clear problem gives design decisions something concrete to answer.

Choose a small set of priority journeys

List the tasks that matter most: finding a service, comparing a product, making an enquiry or joining a platform. For each journey, write down where someone begins, the questions they need answered and the point at which the task is complete. This is more useful than listing attractive reference websites without explaining what you like about them.

Inventory the content you already have

Gather existing page copy, brand assets, approved project photography, product information and business contact details. Mark what can be reused, what needs rewriting and what does not yet exist. Assign an owner to each missing item. Content readiness affects the work because page layouts depend on real headings, images and descriptions, rather than idealized placeholders.

Explain your requirements and constraints

Record the CMS tasks your team must perform, the systems that need to connect and any existing URLs that should remain usable. Separate requirements from ideas that would simply be helpful. If a booking flow or payment integration is essential, describe the expected behavior. Include the people who will review the work and the decisions they can approve.

Agree what a useful review looks like

Review a design by walking through the priority journeys. Can someone understand the offer? Is the next action clear? Does the content answer practical questions? Keep feedback tied to the brief, and distinguish a business requirement from a personal visual preference. Agree how feedback will be collected so the team receives a coherent set of decisions.

Include a content and launch checklist

Before launch, review the important pages, enquiry routes, navigation, image descriptions and page titles. Google recommends clear, concise titles that accurately describe a page; a title is part of the content work, not a final decoration. Add content ownership and future update responsibilities to the handover. The result should be a website your team can use and maintain, with a documented list of any remaining work.

Further reading

Explore our web design service or talk to OPEN CODE about your project.