Start with the problem, not the solution
“We need a new website” often means “our website is making something difficult.” Before discussing designs or platforms, name the difficulty. Perhaps people cannot find opening hours, complete an enquiry, understand your services or read the site comfortably on a phone. Those problems call for different fixes. A confusing navigation menu may be repairable; a platform that cannot support essential services may not be.
Write down the organization’s most important website goals and the tasks visitors come to complete. For a community group, those might be finding an event, checking accessibility information and volunteering. For a small service provider, they might be understanding an offer and getting in touch. Ask the staff who answer questions what visitors regularly misunderstand. Keep the list short enough to guide decisions rather than becoming a catalogue of every preference.
Walk through the site as a visitor would
Choose a few common tasks and try to complete them on both a phone and a larger screen. Start from the homepage, but also begin on an internal page: visitors may arrive through a search result or a shared link. Note where you hesitate, encounter outdated information or reach a dead end. Check whether headings explain the page, links describe their destination, text is readable and forms are straightforward to use. Try navigating with a keyboard, too.
Record each issue alongside the task it affects. “The volunteer form is hard to find” is more useful than “the site feels old.” If you have existing site reports, enquiry records or feedback, use them to add context, but do not assume that a low-traffic page is unimportant. A directions page used by a small number of first-time visitors could still be essential. This review gives you a working list of problems to solve, regardless of whether you eventually rebuild.
Separate fixable issues from structural limits
Many visible problems can be addressed without replacing the site. You may be able to rewrite unclear service pages, simplify the menu, improve image descriptions, update contact details or remove obsolete content within the current system. A focused round of improvements is especially attractive when the site’s underlying structure works and staff can maintain it. It also lets you test whether clearer content and paths solve the original problem before committing to a larger project.
A rebuild becomes more plausible when the system repeatedly blocks necessary changes. Examples include a layout that cannot adapt adequately to small screens, forms that cannot support a required workflow, or a content setup that makes routine updates unreasonably difficult. Do not treat every inconvenience as a platform limit: first check what the current system can do, what access your team has and whether a modest configuration change would help. The decision should rest on constraints you can describe, not simply on the age of the design.
Compare the work behind each option
List what an improvement project would involve and what a rebuild would involve. Improvements might include a content review, revised navigation, a small number of page templates and testing. A rebuild adds decisions about platform, page structure, content migration, redirects from old pages, training and ongoing maintenance. Both options need someone to make decisions, write or approve content and check the finished work. A new design will not resolve unclear ownership or information that no one has time to keep current.
For example, suppose visitors struggle to find workshop dates, but staff can edit the current site easily. Creating a clear events page and linking to it consistently may be the sensible first step. If workshop information is scattered because the system cannot display or update events reliably, a broader change may be justified. Estimate effort using the actual pages and workflows involved, and leave room to test the result before declaring the problem solved.
Make a decision you can revisit
Create a simple decision note with three parts: the visitor problems you found, the limits of the current site and the smallest credible way to address them. Choose targeted improvements when they can remove the main obstacles without creating fragile workarounds. Choose a rebuild when essential goals remain blocked after reasonable fixes, or when maintaining the current site demands more effort than your team can sustain. If the answer is uncertain, start with a contained improvement that will teach you something.
Set a review point based on a meaningful activity, such as the next event cycle or a period of handling enquiries. Check whether visitors can complete the tasks you identified and whether staff can keep information accurate. You do not need a perfect website to make progress. You need a site that supports real visitors, fits your organization’s capacity and can be improved as your needs become clearer.
