Website Redesign & Conversions

Before a Website Redesign, Name the Problem You Need to Solve

Define the customer and business problem before choosing a new website style. Separate necessary changes from preferences and unrelated feature requests.

Desktop purple neon light
Illustrative photograph, not a client or team claim. Photo: Redd Angelo reddangelo16 via Wikimedia Commons · CC0. Resized and cropped.
In this guide
  1. Describe the difficult journey
  2. Prioritise the work
  3. Use an understandable success criterion
  4. Turn the brief into a reviewable plan

“The website looks old” is a reasonable concern, but it is not a complete redesign brief. The useful question is what the current website prevents customers or staff from doing.

Describe the difficult journey

Choose a real task: finding a service, comparing packages, requesting a quote or buying an item. Record where the current page becomes confusing, slow or unreliable. Distinguish a visual preference from a reproducible defect.

Prioritise the work

A redesign can include content, navigation, accessibility and functionality as well as appearance. Not every project needs all of those changed at once. Agree on the smallest coherent scope that addresses the important problem without discarding working systems unnecessarily.

  • Identify the main visitor and decision.
  • List the pages or templates affected.
  • Preserve useful content and functioning integrations.
  • Separate required features from later ideas.
  • Define how the finished journey will be tested.

Use an understandable success criterion

For a service business, a useful goal might be that a new visitor can identify the right package and submit an enquiry without guessing which fields are mandatory. That is a testable design objective. It is different from promising a percentage increase in sales.

Turn the brief into a reviewable plan

Ask for proposed page structure, content responsibilities, functional changes and acceptance checks. Keep the reasons attached to the changes. A redesign decision is easier to review when everyone understands the problem it is meant to solve, rather than choosing between screenshots on appearance alone.

Need help putting this into practice?

Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.

Request a website project review

Further reading from the official documentation