You probably don’t need a new website

A surprising number of organisations asking about a “new website” do not actually need one.

They may need their existing site simplified, modernised, sped up or restructured. They may need clearer content, more intuitive navigation, improved accessibility or some neglected parts brought back under control.

That is very different from rebuilding everything from scratch.

Complete rebuilds are sometimes necessary. A website may be running on unsupported technology, fundamentally inaccessible, difficult to secure or no longer capable of supporting what the organisation needs to do.

But rebuilding a website is expensive, disruptive and time-consuming. It also creates a substantial amount of work for the organisation commissioning it, including reviewing content, making decisions, gathering images, testing functionality and agreeing a new structure.

Before beginning that process, it is worth establishing whether the website itself is really the problem.

What does “we need a new website” actually mean?

When someone says that a website feels old or no longer works properly, they may mean:

• important information is difficult to find
• the navigation has become confusing
• pages are slow or unreliable
• the site does not work well on mobile devices
• staff find it difficult to update
• the visual design feels inconsistent
• content has accumulated without a clear structure
• essential functionality is missing
• nobody is sure how the website is being maintained

Each of these is a genuine problem, but not every one requires a complete rebuild.

Some can be resolved by reorganising the content. Others may require a design refresh, improvements to the underlying templates, better hosting or replacement of a particular piece of functionality.

Sometimes the website simply needs proper attention.

As I discussed in [Why good support matters], websites often become fragile gradually. Maintenance is overlooked, responsibilities become unclear and inconsistent changes accumulate over time.

Starting again may temporarily hide those problems, but it will not prevent them from returning.

Old does not necessarily mean ineffective

There is a tendency within the web industry to treat redesigns as the default solution.

Visual trends change quickly, and websites can begin to look dated long before they stop being useful. But a website does not need to follow every new design fashion to work well.

The more important questions are whether visitors can understand it, find what they need and complete the tasks they came to do.

That does not mean design should stand still forever. Organisations change, expectations evolve and websites need to develop alongside them.

But established websites often benefit more from thoughtful iteration than from regularly starting again.

Websites can evolve

One of the strengths of WordPress is that websites can often be improved gradually.

Navigation can be simplified. Key pages can be redesigned. Accessibility can be improved. Outdated functionality can be replaced. Content can be reorganised. Performance can be addressed. New features can be introduced without discarding everything that already works.

This approach is not always possible, and it is not always the cheapest option. A badly constructed or heavily compromised website may genuinely be easier to replace.

But that decision should follow an assessment of the existing site, not precede it.

Start with the problem, not the solution

Before commissioning a new website, it is useful to identify:

• what is currently working
• what is causing difficulty
• who is affected by those problems
• what the organisation now needs the website to do
• whether the existing platform can support those needs
• which improvements would make the greatest difference

The answer may still be a complete rebuild.

But it might instead be a focused programme of technical, structural and design improvements that costs less, causes less disruption and preserves the useful work already invested in the site.

The best question is often not:

“Do we need a new website?”

It is:

“What is actually stopping our current website from working properly?”