When the numbers flatten, the redesign conversation starts. The site feels dated. Leadership wants something fresh. A new look promises a clean break from whatever isn't working. So you spend three to six months and a real budget building a new site, and a quarter after launch, the growth problem is still there, now wearing a nicer template.
This happens constantly, and it's not because the redesign was done badly. It's because a redesign answers a question almost nobody actually asked.
section 01a redesign is a guess
Most redesigns start from aesthetics and work backward. The brief is "modern," "premium," "clean": words about how the site should feel. Almost none of that is downstream of evidence about why the current site underperforms.
So you're guessing. Maybe the new layout helps. Maybe it hurts the one page that was actually converting. You won't know, because the redesign changed a hundred things at once and measured none of them in isolation. A guess that touches everything is impossible to learn from.
section 02what a redesign doesn't change
Growth lives in four places, and a typical redesign skips all of them:
Positioning. If visitors can't tell within five seconds why you and not a competitor, a new color palette doesn't fix it. That's a strategy problem, not a design problem.
Search intent. Whether your pages match what people are actually searching for is about content and structure, not visuals. A prettier page targeting the wrong intent still ranks for nothing.
Conversion logic. The path from "interested" to "took action" is a sequence of decisions: what you ask for, when, and what proof you offer. Redesigns routinely rebuild this from scratch on instinct, which is as likely to break a working path as improve a broken one.
Content depth. If competitors have answered fifty questions you haven't, that gap doesn't close because your site got faster to load. It closes when you build the missing content.
A redesign can carry these improvements, but only if they're the actual goal. When the goal is "make it look better," they come along by accident, if at all.
section 03when a redesign is the answer
Sometimes it genuinely is. If the site can't be edited without a developer, if it's unindexable, if it breaks on mobile, if the technical foundation actively fights every change you try to make, then rebuilding the foundation is the prerequisite for everything else. That's a real reason.
The test is simple: a redesign is the right move when the structure is the constraint. It's the wrong move when you're hoping a new surface will fix a problem that lives underneath it.
section 04start with the diagnosis, not the redesign
Before committing to a rebuild, get specific about what's actually holding growth back: positioning, intent, conversion, content, or genuine technical debt. Sometimes the answer is a redesign. More often it's three targeted fixes that would have worked on the old site too, for a fraction of the cost and the timeline.
A new website is a satisfying decision because it feels like decisive action. But decisive action in the wrong direction is just a faster way to arrive at the same place. Fix what's broken first. Then, if the structure is still in the way, rebuild it on purpose, knowing exactly what you're trying to change.