WEBSITES
Website redesign or refresh: how to decide
Identify whether your website needs focused improvements or a deeper change in structure.
Separate taste from performance problems
A website can feel old without being the main reason enquiries are weak. It can also look polished while hiding basic problems. List specific issues such as unclear services, broken forms, difficult editing or poor mobile readability.
Collect examples from customer questions and staff experience. A precise problem statement gives the designer or developer something to investigate beyond a general request to make the site modern.
Audit the most important journeys
Try to find a service, understand the offer and make an enquiry. Repeat the journey on a phone and using a keyboard. Note where the customer needs to guess, scroll excessively or recover from an error.
Check whether the content is still accurate. New services, changed delivery areas and an outdated process can make the information architecture unsuitable even when individual pages work technically.
Choose a refresh when the foundation fits
A refresh may be enough when the structure is sound and the main issues are copy, imagery, spacing or a small number of broken components. Focus the scope on the parts that affect understanding and action.
Preserve working content and URLs wherever possible. Measure the specific journey before and after the change, while remembering that traffic mix and seasonality may influence results.
Choose a redesign when constraints are structural
A redesign may be appropriate when the site no longer represents the business, essential tasks require awkward workarounds or maintaining the current system is consistently difficult. Document which constraints a new system must remove.
Plan content migration, redirects, forms, analytics and editing workflows alongside the visual work. A new appearance is only one part of the project; the launch needs to preserve useful access and information.
Define what completion means
Agree on acceptance criteria before work begins. They might include successful enquiry delivery, editable service content, tested mobile layouts and an approved URL migration plan. Keep those criteria separate from subjective design preferences.
After launch, schedule a review of real use and operational questions. A website is easier to maintain when someone owns small corrections instead of waiting for another major redesign.
PUT IT INTO PRACTICE
Your action checklist
- List observable problems before visual preferences.
- Test enquiry journeys on mobile and keyboard.
- Preserve useful URLs or plan redirects.
- Set acceptance criteria and a post-launch owner.
CONNECT THE IDEA TO YOUR BUSINESS
Website Development
A better first impression. A clearer next step.
Explore how we can help
