Start with the job the website needs to do
A redesign often begins with a visual frustration: the site feels dated, competitors look sharper, or the brand has evolved. Those are useful signals, but they are not a complete brief. Define the action the website should help someone take and what currently gets in the way. A service business may need more qualified conversations. A product company may need clearer evaluation paths. Those objectives lead to different design decisions.
Inventory the content before drawing the pages
List the pages, downloads, forms, and integrations you already have. Identify what is current, what is redundant, and what needs an owner. Include pages that receive organic traffic or support sales conversations. Content work usually takes longer than expected, so assigning responsibilities early is one of the most useful things a team can do.
Look at the whole customer journey
A visitor might arrive from an ad, a search result, a referral, or a salesperson’s email. Each route comes with a different level of familiarity. Map the questions that person needs answered, the evidence they need to see, and the next step that makes sense. Navigation and page hierarchy should follow those needs.
Agree on practical constraints
Discuss editing access, integrations, accessibility, hosting, ongoing support, and the approval process before selecting a platform. These operational details shape the project as much as the visual direction. A beautiful site that is difficult to update can quickly become a business bottleneck.
Protect the launch
Plan redirects for URLs that change. Check forms, phone links, metadata, mobile layouts, and analytics. Assign someone to review the production site after launch. A redesign is complete when the business can confidently use and maintain it—not simply when the new homepage is published.
← All perspectives