A new website is supposed to be strictly better than the old one.
It is one of the least examined assumptions in digital marketing, and it is wrong often enough that it should not be an assumption at all.
New sites regularly launch converting worse than the site they replaced, not because the new design was ugly, but because the redesign process prioritized how the site looked over the specific elements, page flows, and calls to action that were already quietly doing the work of converting visitors.
Most websites, in our own experience, do not fail at launch. They fail six months later, once the gap between how the site looks and how it actually performs has had time to show up in the numbers.
This is one of the more consistent findings in post-launch performance data: a business redesigns its site expecting an improvement and instead watches conversion drop, sometimes by thirty to forty percent in the first month, because visitors who had built a mental map of the old layout are suddenly asked to relearn where everything is, while the elements that were actually driving conversions get quietly redesigned into something less effective without anyone noticing until the numbers come in.
| TROPICANA, 2009
A $35 million packaging redesign replaced Tropicana’s recognizable branding with a cleaner, more modern look. Sales dropped roughly 20% within two months, an estimated $30 million in lost revenue, and the company reverted to the original design within weeks. |
| MARKS & SPENCER, 2014
A £150 million, two-year website overhaul aimed at modernizing the retailer’s online experience. The scale of the investment did not translate into a proportional commercial win, a reminder that budget and timeline are not substitutes for testing against a real conversion baseline. |
Neither company set out to make things worse. Both changed something that was already working, at scale, without first confirming the new version actually performed better than what it replaced.
Across the redesigns that hold up under real measurement, one habit shows up more consistently than any other: establishing a specific, documented baseline before any design work begins.
Conversion rate by page, not just site-wide. Bounce rate on the pages that matter most. Session duration. Lead volume broken out by traffic source. Without that baseline, a team has no honest way to know whether the redesign helped, hurt, or changed nothing, and success quietly gets redefined as people like how it looks instead of it converts better than before.
| Redesigns that establish a real conversion baseline before design work begins are consistently the ones that can prove the new site actually outperformed the old one. The ones that skip this step are guessing. |
None of this is an argument against investing in design. McKinsey’s Design Index, which tracked 300 publicly listed companies over five years, found that top-quartile design-led companies achieved 32% higher revenue growth and 56% higher total shareholder return than their peers.
The distinction that separates that outcome from a Tropicana-style miss is that the companies achieving it treat design as a measured, ongoing business function, tested against real outcomes, which is the same discipline behind how we approach UX and UI design work, rather than a one-time cosmetic refresh evaluated by internal opinion in a conference room.
A full, simultaneous redesign changes too many variables at once to know which specific change moved the needle if conversion shifts after launch.
A more disciplined approach redesigns and tests one high-value page or flow first, measures it against the baseline, and rolls proven learnings into the rest of the site incrementally.
One documented case following exactly this pattern, redesigning a single product page, testing it, then applying what worked to the next page, achieved a 250% increase in leads before the full redesign was even complete.
The site never had to bet its entire conversion performance on one untested, all-at-once launch. It is the same underlying logic behind why every new integration costs more than the last one: changing many things at once makes it impossible to know which change actually caused the outcome, whether the outcome is a broken system or a disappointing conversion rate.
At roughly two weeks post-launch, the technical signals are visible: no unexpected drops in search visibility, no broken redirects, conversion tracking firing correctly, Core Web Vitals holding steady on commercial pages.
At four to six weeks, conversion data starts to stabilize enough to read reliably.
By sixty days, the real commercial answer is usually clear: did conversion at the specific pages that were redesigned actually improve against the documented baseline, or not.
Judging a redesign by launch-week enthusiasm, before any of these signals have had time to settle, is how a genuinely underperforming redesign gets called a success before anyone has looked at the data closely enough to know.
If you are planning a redesign, or trying to figure out honestly whether your last one actually helped, that is worth grounding in real data before the next big decision gets made on instinct.
Book a Discovery Call and we will help you build a baseline that actually means something.
AI & Automation
Key Takeaways Start with the job, not the tool. Write down the steps, the people, and the rules before you look at any product. Six checks matter most. Requirements, integration, scalability, security, reporting, and build versus buy. Test with your own work. A demo shows the best case. A trial with real tasks shows the […]
System & Data Integration
Key Takeaways System integration makes systems act. An event in one application triggers an action in another, usually in seconds. Data integration makes data trustworthy. It combines data from many sources into one consistent, usable set. The test is action or answer. If something should happen, you need application integration. If the numbers disagree, you […]
AI & Automation
Key Takeaways It connects, not just automates. Value comes from linking systems, data, and decisions across a process, not from speeding up one step. AI handles messy input. Emails, PDFs, and chat messages can be read and routed. Rules-based tools and RPA need tidy, structured data. People stay in the loop where risk is high. […]