An outdated appearance can justify a redesign, but it is not always the website’s main problem. Visitors may misunderstand the offer, struggle to find information or abandon a form. A new visual style cannot, by itself, explain the cause of those difficulties or ensure they disappear.

Research is especially useful when teams interpret the problem differently. Sales may want more enquiries, editors easier publishing and visitors clearer prices. Record these needs separately so the project does not become an undefined request for a more modern-looking website.

Review existing analytics, content and support feedback. Look for repeated questions and points where user journeys become difficult. Treat the data as clues to investigate, not automatic proof that a particular screen should be removed or that every low-traffic page lacks value.

Give users real tasks in interviews and short usability sessions. Ask them to find a service, compare an offer or send an enquiry. Observe their process without steering them towards the expected answer; an unexpected choice often reveals an important barrier in the current structure.

Turn findings into redesign priorities. Separate content, navigation and functionality issues from visual inconsistencies. Describe who each problem affects and what needs to improve, allowing the team to check whether a proposed concept actually addresses it instead of merely changing its appearance.

Only then decide the scale of the redesign. Sometimes clearer messages and an improved key journey are enough; sometimes new architecture and a CMS are needed. Research helps choose a justified intervention while preserving parts of the website that already serve visitors well.