"We should really get a new website" — this sentence can come up about a genuinely outdated site untouched for five years, and it can just as easily come up about a perfectly well-functioning site, simply because someone's grown tired of the design. These are two very different problems, and they need very different solutions. Before starting a redesign project, it's worth clarifying what you're actually trying to solve.

Design fatigue alone isn't reason enough

If your team finds the site boring from the inside, that's understandable — you look at it every single day. The problem is that the vast majority of your visitors don't look at it daily — they might be seeing it for the first time, or coming back after weeks or months. To them, the site isn't "tired," it's simply what they see right now — and if it's performing well right now, meaning visitors find what they're looking for and take action (request a quote, buy), then design fatigue alone doesn't justify a full rebuild.

That doesn't mean you should never refresh the look — just that the decision should be based on measurable reasons, not a feeling. Before you start anything, look at the actual data: how long visitors stay on the site, how many make it to contact, where they bounce most often. If these numbers are healthy, a visual refresh — not a full rebuild — is often enough to give it a more modern feel while keeping the structure that's working.

The real reasons that actually justify the project

There are a few concrete signals that genuinely indicate a full redesign — not just a surface refresh — is justified. One is if the site technically blocks growth: it can't easily be extended with new features, every change requires a developer, or it's built on an outdated system that's getting harder to find specialists for. In that case, the problem isn't the surface, it's the foundation, and a new color palette won't fix that.

The other serious reason is if visitor behavior shows a real problem: the share of mobile users is growing, but the mobile experience is poor; visitors get stuck at a specific step before converting; or the site's structure no longer reflects what you actually offer, because your business has since expanded or changed direction. The latter is especially common — many companies' sites still show the service range that was relevant two or three years ago, while the real revenue now comes from somewhere else.

How to keep the project from slipping

The most common source of delay in redesign projects isn't development — it's content: the decision is made, the developer has started, but the copy and images are still built around the old structure, and no one thought through in advance what the new site's actual content structure should be. So the most effective order is for content planning — which pages there should be, what goes on each, what message they should carry — to precede visual design, not follow it.

A redesign isn't successful because it looks nicer — it's successful because the visitor reaches what they're looking for faster, and you see faster what works and what doesn't.

It's worth specifically flagging the old site's best-performing content — the subpages that bring in the most inquiries, or that rank best organically — and making sure they don't get lost in the new structure, and that their search rankings aren't wiped out by one forgotten redirect. A well-planned redesign is one where, afterward, both visitors and the search engine experience the site as a continuation, not as a completely new, unfamiliar entity.

If you're not sure whether your site needs a refresh or a full rebuild, let's go through the data together — it's much easier to decide after that.