Redesign or repair? A practical brief for your next website decision
Find the visitor problem before choosing a redesign. Use a practical repair, refocus or rebuild map and a concise website brief that protects ownership and priorities.
Something about your website is bothering you. Perhaps it looks tired. Perhaps customers keep asking questions the site should answer. Perhaps editing a small detail has become a task you put off.
It is tempting to begin with “We need a new website.” Sometimes that is the right conclusion. Sometimes a focused repair or a clearer content structure would address the immediate problem with less disruption. A useful brief begins by finding out which situation you are in.
Describe what happens, rather than what you dislike
“The site feels old” is a starting feeling. “A customer cannot find which service applies to their situation” is a problem you can investigate. “We cannot update the opening hours without outside help” points to an ownership or editing issue.
Gather a few real examples. Use questions you receive, pages you struggle to update and journeys that end at the wrong destination. If you have reliable analytics, add relevant observations with their dates and limits. If you do not, say that plainly. A few specific observations still give the conversation a useful starting point.
“We offer three different services, but the home page treats them as one. People often ask which one they need. We want each service to be easier to understand and the next step to be clear.”
This note describes a useful problem without deciding the entire design solution in advance.
Use a repair, refocus or rebuild map
These are discussion routes, not an automated diagnosis. A technical inspection may change the recommendation, especially where access, reliability or security is involved.
A bounded issue is getting in the way while the wider structure still serves the business. Examples include a broken route, an unclear button destination or an isolated editing problem. Confirm the cause and scope before treating it as a small fix.
The business has changed or the page story is confusing, while the underlying site may still be useful. Reorganise services, rewrite important explanations and improve the journey around the reader’s questions.
The existing structure or implementation cannot reasonably support the agreed needs. The work may include a new information architecture, design system and implementation, with content, access and migration decisions planned together.
Several routes can be relevant at once. A rebuild may still preserve strong content and familiar customer paths. A refocus may reveal technical work that needs attention. The point is to choose deliberately, rather than make a large commitment because a visual trend looks attractive.
Write a keep list before a wish list
Identify the parts that should survive the change. That might include useful explanations, an established domain, recognisable brand elements, a practical editing workflow or a page that customers already rely on.
Existing URLs and important content need an explicit migration decision. When an address must change, agree how the appropriate redirect will be handled and checked. A new design should not silently discard the paths people use to reach your business.
Separate essential needs from preferences. “A person can understand and compare our three services” describes a priority. “We want the same animation as another site” describes a possible design choice. Both can be discussed, but they should not have equal weight in the brief.
Know what you own and what you can access
Before a project begins, confirm who controls the domain, hosting, website administration and important business accounts. Do not send passwords in an ordinary project document. Record the account owner and agree an appropriate way to grant the access the work actually needs.
Include any current content, brand files, image permissions and integrations. If a contact form needs to deliver enquiries, identify the real destination and the people responsible for handling them. A button that looks finished is not a working enquiry process.
Ask how routine content changes will be managed after handover. Clarify what is included in the project and what would need a separate maintenance or support agreement. You should be able to ask these questions without feeling that you need to know the technical vocabulary first.
A brief you can take into the conversation
Use the following prompts in your own document. A few honest sentences for each are more useful than a long list of features copied from another business.
My next website decision
- 1. The business and audience
- What do we do, who do we need to reach and what do those people need to understand?
- 2. The problem we can describe
- What is happening now? Include real examples and distinguish observations from assumptions.
- 3. What we should keep
- Which content, addresses, brand elements and working processes should be preserved?
- 4. The essential outcome
- What must a visitor or content owner be able to do when the work is complete?
- 5. Content, access and dependencies
- Who owns the necessary accounts? What content and permissions exist? What still needs to be supplied?
- 6. Boundaries and decisions
- What investment range, timing constraints, review roles and commercial scope can we discuss?
- 7. How we will review the work
- What journeys, content, functionality and handover evidence should the agreed review cover?
Before you ask for a proposal
Use these local checkboxes to organise your thinking. They do not score your website or send information anywhere, and they are not saved when you reload.
You do not need a perfect brief before asking for help. You need enough shared understanding to make the next conversation honest and useful. Good planning should give you more clarity about your business, not make you feel further away from it.
For the work behind a considered website project, explore our Website Design service. To understand the conversation and review stages, read Our Approach.
Related official reading: Google’s SEO Starter Guide. The repair, refocus and rebuild map and brief prompts are original Sun Drive Digital editorial guidance, not a technical assessment of your site or a guarantee of cost, timing or results.