A redesign is most useful when it improves how the website supports the organization—not only how the pages look. Start by defining what has changed and what the new website must make easier.
01
Begin with the reason for change
Write down the business or communication problem before discussing visual direction. The trigger may be a new strategy, unclear services, difficult content management, poor mobile use, weak enquiries, or a brand that has moved on.
- What can users not do easily today?
- What has changed in the organization?
- Which outcomes should the new website support?
02
Audit the current experience
Review analytics, search terms, common enquiries, support questions, existing content, technical performance, and the pages teams struggle to maintain. Keep what remains useful instead of assuming every part needs replacement.
03
Align audiences, journeys, and content
List the priority audiences and the tasks each one arrives to complete. Use those tasks to shape navigation, page hierarchy, calls to action, and the content production plan.
- Name one owner for every required page.
- Approve structure before polishing every sentence.
- Plan redirects for URLs that will change.
04
Define success before build
Agree what the team will review after launch: task completion, qualified enquiries, content publishing time, performance, accessibility, search visibility, or another relevant measure. Avoid metrics the website cannot influence alone.