Your website can function perfectly well and still represent the wrong version of your organisation. An outdated story, buried evidence, unsuitable enquiries or publishing difficulties are reasons to investigate. An isolated problem may need a focused fix; connected problems may justify a redesign or brand review. The site’s age does not make that decision for you.

The pages load. The logo is correct. The contact form sends emails. Yet a colleague keeps saying, “I’ll send you a presentation instead.” That gap deserves attention. Another service squeezed into the menu or another PDF doing a page’s job may reveal where the business has moved on. These seven signs are prompts for investigation, rather than a scoring system that automatically awards you a redesign.

The business has changed, but the introduction has not

Your homepage describes a previous version of the organisation. New services appear as additions around the edges, while the main message still gives prominence to work you no longer want to lead with. Ask someone unfamiliar with the business to explain what you do after reading a key page. Compare that with your current priorities. If the gap is substantial, investigate the proposition and content before discussing colours or layouts.

Your strongest evidence is difficult to find

The work that would give a buyer confidence exists, but it is buried in a news archive, scattered across PDFs or known only to the account team. Try following a service page to a relevant example. Can a visitor see the problem you solved, the work you contributed and an approved outcome? A general gallery may look attractive without answering those questions. You may need better links and case-study writing rather than a new platform. First establish what is missing and where it belongs.

Enquiry volume looks healthy, but the fit is poor

A busy inbox can disguise a website that attracts work you do not offer, budgets you cannot serve or customers looking for a different kind of provider. Review a sample of enquiries with sales. Look at how people arrived, what the landing page promised and which questions were answered before contact. Check campaign targeting and sales handling too. The website may contribute to the mismatch, but do not assume it is the only cause simply because the form is where the enquiry appeared.

The identity becomes less convincing on screen

The brand may work well on packaging or in a presentation, yet feel inconsistent across service pages, forms and small screens. Every new component needs another exception to the guidelines. Test the identity with real content and common tasks. A missing type hierarchy, limited functional colours or unclear imagery guidance may call for extending the brand system. That is different from deciding the entire identity has failed.

A simple update has become a project

Publishing a new service should not require several workarounds and a favour from someone who understands an old template. If editors avoid updates, the site can fall behind the business even when everyone knows what needs changing. Watch a colleague create, preview and publish a representative page. Record where the process slows down: permissions, approval, content preparation or the CMS itself. A training or workflow problem will not necessarily disappear with a new platform. Diagnose the whole task.

The site cannot support the next planned change

A new market, a recruitment drive, a merger or an additional language may require capabilities the current site cannot comfortably provide. Write down what the next move actually demands. Is it a new content type, a different audience journey, a clearer service structure or a substantial integration? “We need flexibility” is less useful than a concrete scenario. Then test whether the existing system can support it sensibly. Future plans justify investment when they are real enough to scope.

Colleagues have stopped trusting it to represent them

People apologise before sharing the link. Teams create their own landing pages or send private documents because the official site does not tell the story they need. Those workarounds are evidence of unmet needs, though they are not proof that every criticism is right. Ask what each alternative provides that the website does not. A collection of improvised solutions can reveal the brief for an improvement more clearly than a meeting about whether the site looks dated.

Find the cause before choosing the response

At Framework, we start with what the website prevents people doing or understanding. Appearance matters when it affects trust, readability or the organisation’s position. An older visual style that remains recognisable and useful may need careful evolution rather than replacement.

Bring customer conversations and sales feedback together with analytics, search data, publishing tasks and a technical review. Look for a repeated pattern rather than letting one striking statistic or one senior opinion settle the brief. Low visits to a service page, for example, could reflect limited demand, weak promotion or a page that is difficult to find. Customer evidence and the journey itself help distinguish those explanations.

Optimise where the foundations work and the issue is isolated, such as a confusing form, weak service copy or buried case studies. Consider a redesign when structure, templates and journeys repeatedly obstruct the work. Include brand work where positioning or identity no longer supports the organisation’s direction. These responses can overlap, but each part of the scope should have a clear purpose.

Urgent operational repairs need not wait while a redesign is debated. A technical review can distinguish what can be stabilised from what needs replacing, and whether a repair will have a useful life beyond the immediate patch. There is no universal replacement cycle: review the site regularly and make substantial changes when the business, audience or system has outgrown it.

Give the brief something you can test

Begin with a valuable customer journey: finding the right service, assessing proof and taking the next step. Then examine the publishing and technical work behind it. Describe what should become easier. A prospective customer should understand the offer without a follow-up presentation. An editor should be able to publish a service page with the agreed components. A buyer should find relevant evidence before enquiring.

Those outcomes give the project a test. “A website everyone loves” gives it a wish.

“A website everyone loves” gives it a wish.

For your next team meeting, ask sales, marketing and the people maintaining the site to bring one recent customer question or workaround. Record the difficulty, who experiences it and the supporting evidence. Group the findings into content, usability, brand and operational issues, then identify the most consequential problem and a practical next step. You may leave with a repair list or a discovery brief. Either is more useful than a predetermined redesign.