How to Plan a Website Redesign Without Losing Momentum

Most redesigns don’t fail because of bad design. They fail because of bad sequencing — content isn’t ready when development starts, stakeholders review the wrong thing at the wrong time, and by launch day everyone is negotiating instead of shipping.

Start with the sitemap, not the mockups

Before anyone opens a design tool, agree on what pages exist and why. A sitemap review takes an afternoon and prevents weeks of rework once your team realizes mid-project that “Solutions” and “Services” were supposed to be the same section.

Write copy before you design

Design decisions — hero layout, card counts, navigation depth — are really content decisions in disguise. Draft real copy first, even in a plain document. Lorem ipsum mockups get approved and then quietly redesigned once real sentences don’t fit the boxes.

Build the design system before the pages

Define your type scale, spacing, color tokens, and component states once. Every page after that is assembly, not invention. This is the difference between a redesign that takes six weeks and one that takes six months.

Decoupling content from launch

Content collections (the pattern this site is built on) let marketing and engineering work in parallel. Copy lives in version-controlled files, structure is enforced by schema, and a new blog post or service page ships without anyone touching a template.

Keep one owner for final calls

Redesigns stall when every stakeholder has veto power at every stage. Name one decision-maker for design, one for copy, and let them make calls quickly. You can always course-correct after launch — you can’t get back the weeks lost to consensus-seeking.