The relaunch checks teams remember too late
A relaunch is planned for months and judged in its first week. The checks that decide that week are often the ones left until the end.
In this article
Teams spend most of a relaunch on design and build. Testing gets squeezed into the last days, and it usually focuses on whether templates work, not on whether the journeys that bring in revenue still make sense.
What teams remember too late
- Journeys: the paths that matter most, from landing page to conversion.
- Content: copy, prices and legal texts carried over from the old site.
- Redirects: old links, campaigns and bookmarks that still need a destination.
- Forms: validation, error messages and confirmation emails.
Compare old and new, journey by journey
The most useful baseline is the site you’re replacing. Run the same key journeys on the old site and on staging, and compare where the new version makes people hesitate. Regressions are much cheaper to fix before launch than after.
The best relaunch week is the one where nothing surprising happens.
Keep watching after go-live
Launch day isn’t the finish line. Re-run the key journeys in the first weeks, while the team is still iterating, and catch new friction before support tickets do.
More opinions
Make something beautiful, now
AI puts a factory in everyone’s hands. The web we know will have to become like clay.
Why your website backlog needs ranking, not more findings
A practical argument for prioritising friction by customer and business impact.
The hidden places checkout trust breaks
Shipping, variants, returns and payment copy often disagree at exactly the wrong moment.
Check your relaunch before visitors do.
We’ll walk you through a report on your staging site: the regressions, the evidence, and the fixes Remy would ship first.
