01
Start with what is frustrating the user
A full rebuild can be the right answer, but it should not be the automatic one. Many websites already have useful content, search history, familiar editing tools, and integrations that work. The real problem may live on one page or inside one task.
If visitors cannot find an event, check whether service is available in their area, send the right kind of inquiry, or understand what to do next, that specific frustration is the best place to begin.
02
Small features can make a big difference
A dynamic calendar can make changing information easier to manage. A ZIP-code selector can answer a service question before it turns into a phone call. A better form can connect a helpful guide with a serious lead. A clear careers page can improve hiring without changing the rest of the website.
- Identify the task that is not working.
- Confirm that the current platform can support the fix.
- Build the smallest complete solution.
- Check it on phones, tablets, and desktop screens.
- Explain how the client can maintain it.
03
Keep the parts that already work
A focused update requires restraint. Existing brand recognition, page addresses, analytics history, and editing habits all have value. A responsible improvement fixes the problem without creating unnecessary new ones around it.
04
Know when the smaller fix is no longer enough
A focused update should not become an excuse to avoid a rebuild that is truly needed. If the platform creates security issues, prevents accessible design, blocks important integrations, or makes normal updates unreasonably difficult, starting fresh may be the better long-term choice.
The right scope is the one that solves the real problem while respecting the client's time, budget, and ability to maintain the result.