Start with the decisions the site must support
A useful redesign brief identifies the customer decisions that matter: whether the offer is relevant, whether the company can be trusted and what to do next. Audit those decisions across priority journeys before discussing visual style.
Pair experience evidence with commercial signals. Low conversion, weak qualified traffic, sales objections, slow publishing and technical maintenance are all more actionable than the idea that the website simply feels old.
Separate symptoms from structural problems
A visual refresh cannot repair unclear positioning, fragmented content ownership or an inflexible platform. Group findings into strategy, content, experience, technology and measurement so stakeholders can see which problems share a cause.
This also makes scope easier to manage. The team can protect high-impact work and avoid spending the budget on surface changes that leave the core constraint untouched.
Define success before the sitemap
Choose a small set of measures tied to the redesign purpose: stronger qualified enquiries, faster content publishing, better organic landing performance or fewer support contacts. Establish a baseline and decide how each signal will be measured.
The result is a redesign program that can make tradeoffs with confidence. Every major decision can be tested against the same question: will this make the priority customer journey clearer and more effective?
