Do we need a new website, or should we improve the one we have?
The website isn’t quite right. It no longer explains the business properly, enquiries are disappointing, or the team finds it difficult to make changes. A new website feels like a sensible answer. But how much of the existing one actually needs replacing?
There are several decisions hiding inside “we need a new website”. You might need different content, a clearer structure, a different design or a technical platform that lets you do something the current one cannot. Sometimes you need all of those. Sometimes you need one.
They don’t have to come as a package.
The useful starting point is to describe what needs to become better for the business and its customers. Then work out which parts of the website stand in the way, and which parts are still doing a useful job.
Separate the problem from the proposed project
“The website looks old” tells you something about its appearance. It doesn’t yet tell you what that appearance is costing the business.
“We keep explaining our current services on calls because the site describes an older offer” is more useful. You can investigate what people misunderstand, which pages contribute to it and whether the structure still fits.
“The marketing team can’t create a new solution page without developer help” describes a different constraint. Better homepage copy won’t remove it.
Before comparing options, establish what the website needs to do and what is actually stopping it. Otherwise, you can end up comparing three different ways to solve a problem you haven’t defined.
Improving what’s there
Improvement makes sense when the existing foundations can support the outcome you need, but particular parts of the experience fall short.
That might mean rewriting a service page, bringing stronger evidence forward, changing the navigation, removing outdated material or making the enquiry route easier to use. It could also involve technical work: fixing a form, improving page performance or giving the team a more useful way to manage content.
These changes can be substantial without requiring a whole new website.
The advantage is that you can concentrate effort around a known problem, retain what works and learn from the result. The limitation is that local changes can only take you so far if the underlying structure or platform keeps getting in the way.
If every useful improvement requires another workaround, the apparent economy of keeping the existing site deserves questioning too.
When a redesign is justified
A redesign becomes useful when the experience needs to change across the site, rather than in a few isolated places.
Perhaps the navigation no longer fits the offer. Different audiences struggle to find what’s relevant. The visual hierarchy makes everything equally prominent. Or the way the business presents itself creates an impression that no longer matches its work.
The design should follow decisions about those things. A different visual style won’t decide which services matter most or resolve competing explanations of the business.
With Errol Donald, we first clarified how his broad creative practice should be understood and shaped three clear service areas. That informed the website structure, content and an interactive prototype before the site was rebuilt.
The rebuild was part of carrying a clearer proposition into practice. Beginning with the visual design would have left some of the important questions unanswered.
That distinction matters particularly when the business has outgrown its website. You need to bring the site back into line with the business, whichever delivery option you choose.
When the technical foundation needs to change
A rebuild is worth considering when the current implementation cannot sensibly support what you need it to do.
Perhaps the team cannot manage the content it needs. Important customer journeys depend on fragile workarounds. Integrations are unreliable. Or the cost and difficulty of making ordinary changes have become a continuing constraint.
These are questions to investigate with the people responsible for the technology. A frustrating editing experience doesn’t automatically mean the whole platform is unsuitable; sometimes the problem is how it has been configured or built.
Equally, keeping a familiar platform is not a useful goal if it keeps making the business’s work harder.
The work with Locale included a website rebuild and a more flexible component-based platform, followed by ongoing improvements to content, search visibility and customer journeys. The value extended beyond the launch: the marketing team had a foundation it could continue working with as the product and its needs evolved.
A better foundation can make later improvement easier. It still needs someone to decide which improvements matter.
Compare the options against the same outcome
A small change is not automatically the best choice. Neither is a complete rebuild. Each option needs to explain how it addresses the problem and what it leaves unresolved.
For each option, ask:
- What would this actually improve? Name the customer task or business outcome, rather than the deliverable.
- What evidence makes us think it will help? Separate observations from preferences and assumptions.
- What could we retain? Useful content, customer routes, search visibility and working systems all deserve consideration.
- What would still get in the way? Include constraints the proposed work doesn’t address.
- What does the change require from us? Content decisions, staff time, integrations, testing and ongoing ownership are part of the work.
- How will we know whether it helped? Decide what to observe before changing the site.
You might find that a focused change would answer the question well enough. You might find that several changes belong together because they depend on the same structural decision. Or you might have a clear reason to replace the existing foundations.
The point is to make those reasons visible before choosing the project.
Keep what is already useful
Replacing the website doesn’t mean everything on it has failed. There may be pages customers rely on, material that answers useful questions, or journeys that work well.
Find out what those are before deciding what to remove. If URLs need to change, plan how people and search engines will reach the replacement pages. Check important enquiries, bookings and integrations before launch. Record a baseline so you have something meaningful to compare afterwards.
Those considerations apply to a large restructure as well as a new technical build. The disruption depends on what you change, not what the project is called.
Choose the work, then keep paying attention
Once the problem and direction are clear, the next step can be a defined piece of work. It might be a few connected improvements, a redesign or a rebuild. You don’t need a separate strategic investigation if you already have enough evidence to make the decision.
If important questions remain open, answer those before committing to the larger project. The short website diagnostic can help you work through where the uncertainty sits.
Whichever route you take, decide who will keep paying attention after launch. Replacing a website can address today’s problem. Keeping it aligned with the business requires somebody to notice tomorrow’s.