A website redesign rarely fails because a team picked the wrong shade of blue. It fails because the project begins with broad instructions such as “make it more modern” or “improve the user experience,” without agreement on what the business needs the new site to achieve. Knowing how to brief website redesign work properly gives your agency, internal stakeholders, and technical team a shared basis for decisions before time and budget are committed.
A useful brief is not a long document written for its own sake. It is a practical plan that explains the commercial problem, identifies priorities, defines the scope, and clarifies who can make decisions. The clearer the starting point, the faster a redesign can move from strategy to design, build, testing, and launch.
Start With the Business Reason for the Redesign
Before discussing page layouts or visual references, state why the current website needs to change. A redesign may be needed because the website no longer reflects the brand, is difficult to update, performs poorly on mobile, generates weak leads, or cannot support online sales. These are different problems and may require different solutions.
Be specific about the evidence behind the decision. For example, a property business may find that mobile visitors cannot easily browse available developments. A retailer may need better product filtering and a simpler checkout flow. A professional services firm may need to present its expertise more clearly and give prospective clients an easier way to request a consultation.
This context prevents the redesign from becoming a subjective exercise. It also helps the project team distinguish between issues that need a new website and issues that may be solved through content changes, performance improvements, or ongoing digital marketing.
How to Brief a Website Redesign Around Results
A strong redesign brief connects each major requirement to a measurable business outcome. Set one primary goal, then identify supporting goals. Trying to make every outcome equally important usually leads to a crowded website and slower decision-making.
Your primary goal could be lead generation, e-commerce revenue, booking requests, brand credibility, recruitment, or customer self-service. Supporting goals may include improving search visibility, reducing manual inquiries, increasing newsletter sign-ups, or making campaign landing pages easier to launch.
Define how success will be assessed after launch. This does not need to be overly technical. Useful measures may include qualified form submissions, conversion rate, average order value, calls from mobile users, completed booking requests, or the time required for staff to publish a new page. If traffic is currently low, improving conversion alone may not create the sales result you expect. The redesign and marketing plan may need to work together.
Identify Your Priority Audiences and Their Tasks
A website cannot speak to every visitor in the same way. Brief the main audience groups, what they need, and what action you want each group to take. Include practical details such as their level of product knowledge, the device they are likely to use, and the questions that may stop them from converting.
For a healthcare provider, new patients may need to find services, doctor profiles, locations, and appointment information quickly. Existing patients may need access to forms or contact details. For a business-to-business company, procurement teams may want capability information and certifications, while decision-makers may look for case studies, service benefits, and proof of experience.
Mapping these journeys helps determine navigation, calls to action, page hierarchy, and content requirements. It is more useful than simply requesting a homepage that “looks premium.”
Audit What Exists Before Defining What Is New
Include an honest assessment of the current website. List pages that perform well, content that must be retained, pages that are outdated, and technical or usability issues that have caused problems. Analytics, search data, customer feedback, sales-team input, and support inquiries can all inform this review.
Do not assume every existing page should be moved to the new site. Redesigns are a good opportunity to remove duplicated, inaccurate, or low-value content. At the same time, deleting established pages without checking their search performance can reduce organic traffic. The right approach depends on the value of those pages and whether their content can be improved, consolidated, or redirected.
Define Scope Before Design Begins
Scope is where many redesign projects lose control. A brief should clearly state the expected deliverables and separate essential requirements from items that would be useful but are not required for launch.
Describe the anticipated page types rather than only giving a total number of pages. A corporate site may need a homepage, service pages, industry pages, case studies, news, careers, contact pages, and legal pages. An e-commerce website may also require category pages, product pages, account areas, cart and checkout flows, delivery information, and returns content.
State the functionality required. This could include inquiry forms, booking tools, store locators, multilingual content, membership access, product filters, payment gateways, CRM connections, marketing pixels, or email platform integrations. Mention whether each system already exists, who owns it, and whether API access or technical documentation is available.
Content ownership should be equally clear. Decide whether your team will supply final copy, product data, photography, videos, and translations, or whether these services are part of the project. A website cannot launch on schedule if essential content is still being drafted after development is complete.
Give Direction Without Designing the Site Yourself
Brand guidelines, approved logos, typefaces, colors, photography standards, and campaign materials should be included in the brief. Share a small number of reference websites and explain what you like about them. Is it the navigation, the way services are explained, the product presentation, or the use of whitespace? A folder of unrelated visual examples gives less direction than a few relevant comments.
Avoid treating reference sites as templates to copy. Your organization may have a different audience, brand position, content volume, or technology requirement. Good design direction provides context while giving the design team room to solve the actual problem.
Set Realistic Budget, Timeline, and Approval Rules
A budget range allows the agency to recommend an appropriate level of design, functionality, content support, and technical setup. Without one, proposals can be based on assumptions that do not match the available investment. It is better to prioritize a focused first release than to include every possible feature and compromise the quality of the essentials.
Share any fixed dates early, such as a product launch, campaign, event, lease opening, or rebrand announcement. Then work backward to allow time for discovery, design approval, development, content entry, quality assurance, user acceptance testing, and staff training. The visible launch date is only one part of the schedule.
Clarify the approval process as well. Name the project owner, the people providing feedback, and the final decision-maker. Agree on how feedback will be consolidated and how many revision rounds are expected. Conflicting comments from multiple departments can delay a project more than any technical issue.
Put the Brief Into a Working Document
The final brief should be easy for both business and delivery teams to use. It does not need corporate jargon or a large presentation deck. A practical document normally covers these areas:
- Business background, the reason for the redesign, and the primary success goal.
- Target audiences, key user journeys, and the actions each visitor should take.
- Current-site issues, existing content to retain, and pages to remove or consolidate.
- Required page types, functionality, integrations, content responsibilities, and technical constraints.
- Brand assets, reference examples, budget range, launch timing, and approval contacts.
Review the brief with all key stakeholders before requesting final proposals or starting work. This is the point to resolve assumptions, not halfway through design. If a requirement remains uncertain, label it clearly as a decision to be made during discovery rather than leaving it open to interpretation.
Keep the Brief Useful After Kickoff
A redesign brief should guide the project throughout delivery, not disappear after the first meeting. Revisit it when new requests arise. Ask whether the request supports a stated goal, fits the agreed scope, and can be delivered without affecting the timeline or budget.
Some changes will be worthwhile. A new integration may become necessary, or customer research may reveal a better user journey. The goal is not to prevent change. It is to make the trade-off visible, so decisions are based on impact rather than urgency alone.
The best brief gives your chosen web partner enough clarity to move quickly while leaving room for informed recommendations. When goals, ownership, content, and approvals are clear from the start, the redesign has a better chance of becoming a website your team can operate confidently long after launch.
English 
Chinese