A new website is the most expensive way to not decide anything.
When the answer is "we need a new site", the answer is usually about a decision nobody has made. The rebuild makes the unresolved answer load faster.
Somewhere in most organisations there is a deck arguing for a website rebuild. The argument is usually about the current one: it is slow, it looks dated, it does not work on phones, the team fights with it every week.
All of that can be true, and the rebuild can still be the wrong decision.
Not because the site does not need replacing. It does. Because a website is not where the unresolved question lives, and rebuilding it will not surface the question — it will hide the question behind four months of production and a launch that everyone enjoys.
What a site is actually for
A website is a place where a company states what it is, to people who are deciding whether to take it seriously. Every page is a claim about positioning, priority and audience, written down in a form that cannot be argued with.
Which means the work is not really design. It is finding out what the company believes, from the people who believe it, and checking whether they all believe the same thing.
That discovery is uncomfortable, and it is the actual content of the project. The layout is the easy part, and the layout is what gets scheduled.
A new site cannot make an unclear answer clear. It can only make an unclear answer arrive faster and look more expensive.
The three decisions hiding in the brief
Every rebuild brief contains three decisions, written as though they were design requirements.
- What is the headline? Not the sentence on the hero — the one that decides what the company is when a stranger has four seconds. This is positioning, and it cannot be settled in a workshop with designers in the room.
- Who is it for? Most sites are written for the person who raised the money. The person buying is usually different, in what they care about and in what they will tolerate. Both are on the same homepage, arguing.
- What comes second, and what does not? A site that gives everything equal space has decided that nothing is important. This is a portfolio conversation wearing a navigation problem.
Notice that none of these are answered by choosing a template. They are answered by the business deciding, in words, what it is for. The template comes last, and it is the easy part.
The symptom that tells you which one it is
There is a useful diagnostic, and it is uncomfortable because the answer is often financial.
If the last rebuild was followed by a measurable change in enquiries, conversion or qualified traffic, you have a website problem. You have a site that is underperforming against a message that works, and the fix is genuinely technical: speed, structure, search, mobile.
If the last rebuild was followed by relief, and then the same internal argument about positioning resurfaced within two quarters, you have not had a website project. You have had a project that gave the argument somewhere to go while it was not happening.
The second pattern is far more common than anyone admits, partly because the first one is much better work.
When a rebuild is the right answer
It often is, and it is not a lesser choice. A site that is genuinely hard to use, slow on a phone, or impossible for the team to update will quietly cap everything else you do.
The order that works:
- Settle the positioning first, in a document nobody has to approve.
- Choose what the site must make a visitor do, and put that above the fold.
- Then rebuild, to a specification the positioning produced.
Steps one and two take weeks. Step three takes months. In practice teams do them in the opposite order, which is why so many launches are technically excellent and commercially stillborn.
The launch is worth doing for its own sake. It is worth the money only if the thing it is saying was decided before the designer opened a file.
