A website can look dated and still be useful. It can also look polished while making essential tasks frustrating. Before investing in a redesign, look at the experience from three perspectives: your visitors, your business goals, and your internal team.
Start with the jobs people need to do.
Can a new visitor quickly understand what you offer and who it is for? Can they find relevant examples, compare services, and reach the right contact route? Ask someone unfamiliar with the website to complete a few realistic tasks. Watch where they hesitate rather than explain where to click.
Repeated confusion around the same pages is a stronger signal than a personal preference for a new visual style. It may reveal weak information architecture, unclear language, competing calls to action, or a mobile layout that hides what matters.
Compare the website with the business you are today.
Your services, customers, positioning, or operating model may have changed since the website was created. If the site still describes an earlier version of the business, prospective clients may leave with the wrong impression.
Review the core pages alongside your current offering. Look for outdated claims, missing services, irrelevant content, weak project descriptions, and contact paths that no longer match how your team works. These problems often require content and structure decisions before design decisions.
Look at the cost of maintaining it.
Everyday updates should not become a technical project. If a small content change breaks the layout, or your team avoids publishing because the process is confusing, the website may be creating operational friction.
Consider whether the existing platform can support a better editing experience. A rebuild may help, but so can improved templates, clearer content models, documentation, and training. The best recommendation addresses the real constraint.
Separate symptoms from foundations.
Slow pages, poor responsiveness, fragile plugins, inaccessible interactions, and difficult integrations may have different causes. Some can be improved within the current website. Others point to deeper structural or technical debt.
Establish a useful baseline.
Before making substantial changes, document the pages, content, and journeys that already work. Where data exists, review relevant search traffic, important landing pages, enquiry paths, and technical measurements. If measurement is missing, acknowledge the gap and plan how to improve it.
This baseline helps protect existing value and makes later evaluation more meaningful. Without it, a new design can feel like progress without showing whether essential tasks became easier.
Choose the right level of change.
A focused improvement is often suitable when the platform remains sound and the problems are contained. A more complete redevelopment becomes useful when content, structure, design, technology, and maintenance difficulties reinforce each other.
Your first step should be a clear assessment, not an assumption that everything must be replaced. A strong plan identifies what to retain, improve, rebuild, or retire—and explains why.
If your website no longer reflects your business or creates recurring friction, bring those observations to a redevelopment conversation. You do not need a finished specification. A clear account of what is not working is a useful place to begin.