A website redesign can quickly become a conversation about visual taste. That conversation matters, but it should follow a clearer one: what does the site need to help people understand, decide and do?
Map the jobs the site performs
List the audience’s main reasons for visiting. A prospective client may want to understand the offer, assess credibility, compare approaches or make contact. An existing client may need a different route. Each job suggests a small set of pages, questions and actions worth examining.
Review search queries, top landing pages, navigation paths and inquiries alongside interviews or sales conversations. Analytics can show where people go; human context helps explain why.
Find friction, not just low numbers
A high exit rate may be expected on a page that answers a question. A low conversion rate may reflect the wrong audience arriving. Look for patterns such as unclear service language, repeated objections, hidden proof, slow mobile journeys or contact paths that demand too much too soon.
Record the current baseline for the outcomes you care about. Depending on the site, that might include qualified inquiries, task completion, engagement with key service content, organic visibility for relevant topics, accessibility issues and page performance.
Write the redesign hypothesis
Translate the evidence into specific changes and expected effects. For example: a clearer service structure should help visitors identify the right offer; more precise proof should improve confidence; a simpler inquiry path should reduce avoidable friction.
After launch, compare the same measures over a sensible period and account for changes in traffic, campaigns and seasonality. A redesign succeeds when it makes the experience more useful and the business more effective, not simply when it looks new.