I originally wrote a much shorter version of this article in July 2017. Looking back almost a decade later, I considered rewriting it from scratch, or simply deleting it altogether. Instead, I realized that the central idea hasn't changed. If anything, it's even more relevant today.

The way we build websites has evolved dramatically. We have AI-assisted workflows, faster development frameworks, better analytics, and far more sophisticated design systems than we did back then. Yet one mistake remains surprisingly common: teams decide to redesign a website before they truly understand the one they already have.

A redesign is not a replacement exercise. It's a decision-making exercise.

The pattern I keep seeing

Throughout my work with startups, enterprise platforms, SaaS products, and established businesses, I've seen the same pattern repeat itself. Stakeholders often become focused on visual improvements before asking more fundamental questions.

Why do users visit this website?
Which pages consistently perform well?
What content brings qualified traffic?
Where do visitors abandon the journey?
What is actually helping the business, even if nobody notices it?

What already works, even if it doesn't look like it

Every website, even one that feels outdated, contains valuable information. Sometimes it's content that has quietly built years of search authority. Sometimes it's a navigation pattern users already understand. Sometimes it's a workflow that isn't particularly elegant but consistently helps people complete their tasks. Removing those elements simply because they don't fit the new visual direction can create more problems than it solves.

Why every redesign I work on starts with an audit

That's why every redesign I work on begins with an audit. The objective isn't to criticize the existing website or justify starting over. It's to understand it.

What an effective audit looks like

An effective audit combines different perspectives. Analytics reveal user behavior. Search performance highlights what people are already finding. Content reviews expose inconsistencies and opportunities. Conversations with stakeholders uncover business goals, while user research explains how real people experience the product. None of these sources tells the whole story on its own, but together they provide the context needed to make informed design decisions.

What the audit usually reveals

Almost every audit eventually leads to the same conclusion:

Some parts of the website deserve to be preserved, because they're already working.
Some should be improved, because they no longer support the business effectively.
Others should disappear, because they've become unnecessary complexity.

The goal isn't to redesign everything. The goal is to understand what deserves to evolve and what already provides value.

Why this approach works

This approach consistently produces better outcomes. Instead of rebuilding an entire experience from scratch, teams can focus their effort where it has the greatest impact. Existing strengths are preserved, technical and UX debt become visible, and design decisions are supported by evidence rather than assumptions or personal preference.

A successful redesign isn't measured by how different the new website looks. It's measured by how much clearer the experience becomes for users, how effectively it supports business goals, and how confidently every design decision can be explained.

Understanding before rebuilding

That was the point I was trying to make back in July 2017. Nearly ten years later, I still believe it's one of the most important principles in product and website design, and perhaps today, with AI making it easier than ever to redesign anything in a matter of hours, it's more important than ever to remember that understanding should always come before rebuilding.