The Website Redesign Process: When to Redesign, When to Wait, and How to Scope It

The website redesign process, explained honestly. When to redesign, when to wait, and how to scope it without wasting months.

Most website redesigns solve the wrong problem. A founder decides the site ”feels outdated,” commissions a full rebuild, spends three months and a serious chunk of budget, and lands somewhere that is prettier but converts the same. The website redesign process is one of those decisions that looks tactical but is actually strategic, and getting it wrong is expensive. Getting it right starts with being honest about whether you should be redesigning at all.

I have worked on redesigns from both sides. As a designer running the projects, and as someone who has watched clients pay for redesigns that did not deliver what they hoped for. The framework below is what I actually think through when a founder asks ”should we redesign?” It is opinionated, and it is willing to tell you not to.

When you actually need a website redesign process

Some signals genuinely mean it is time. The clearest one is that your business has changed and your site has not. If your positioning has shifted, your audience is different, your services have evolved, or your pricing model has changed, a site that still speaks to the old version of your business is actively working against you. This is not vanity. It is your homepage telling visitors the wrong thing about who you are.

Another clear signal is that the site cannot do what you need it to do. If you need to add a booking system, a members area, a proper blog, or ecommerce, and your current platform makes that difficult or impossible, that is a real reason to redesign. The redesign in this case is not about looks. It is about capabilities.

A third signal is performance. If your analytics show that people arrive, look around for a few seconds, and leave, and you have already tried tweaking the copy and the calls to action, structural problems in the site itself may be the reason. When enough small changes have not moved the needle, a bigger change is worth considering.

And finally, if the site is technically broken. Slow load times, poor mobile experience, a CMS that requires developer help for every update, security vulnerabilities. These are not opinions about design. They are operational costs that compound over time. Fix them.

When you should not redesign

This is the section most articles skip because their business model depends on you saying yes. I will say it plainly: sometimes a redesign is the wrong answer.

If your site ”feels dated” but is converting well, do not touch it. Aesthetic dissatisfaction is not the same as a business problem. Some of the ugliest sites on the internet make excellent money because they solve their visitors’ problem clearly. Before you redesign because you personally have gotten bored of your site, look at the numbers. If they are healthy, the site is doing its job.

If the real problem is content or copy, no visual redesign will fix it. I have seen founders redesign three times chasing a conversion problem that was actually a headline problem. If your homepage does not tell a visitor what you do, who it is for, and why they should care, in the first five seconds, no amount of new typography will save you. Fix the words first. If the fixed words convert, you never needed the redesign.

If the underlying strategy is unclear, redesigning is premature. A redesign forces a hundred small decisions about hierarchy, emphasis, and structure. All of those decisions require a clear answer to ”what is this site trying to do.” If you cannot answer that in one sentence, spend a week on strategy before you spend three months on design. I wrote about this dynamic in designing a landing page that converts. The same principle applies to a full site.

If you have never done a real audit of the current site, redesigning is a shot in the dark. You do not know what is working, what is not, or why. Spend a few days looking honestly at your analytics, your heatmaps, and a handful of user recordings before you commit to a rebuild. You may find the problem is one page, not the whole site.

Scoping the website redesign process

If you have decided to move forward, the next question is scope. This is where most projects go wrong before they even start. Scope drift on a redesign is not a matter of a few extra hours. It is the difference between shipping in eight weeks and shipping in eight months.

Start with a ruthless list of what is actually in scope. Which pages get redesigned. Which pages get carried over. Which functionality gets built. Which integrations connect. If a page does not appear on the list, it does not get touched. If a feature is not on the list, it does not get built.

Then be honest about what is out of scope. Content writing. New photography. Brand refresh. A new logo. A shift in positioning. Any of these can be part of a redesign, but each one adds weeks and cost. Most redesigns bundle them because it feels efficient, and then discover halfway through that they are actually four projects wearing a trench coat. If the brand needs work, do that first. Then design the site that expresses it. Trying to do both at once means every design decision has to wait for a brand decision that has not been made yet.

The best redesigns I have run had a scope document of one page, decided before design started, and referred back to every time someone said ”while we are at it, could we also…”. The answer to that question is almost always no, and putting it in writing gives everyone permission to say no without seeming difficult.

What the website redesign process actually looks like

Once scope is locked, the process itself has four phases. Different teams call them different things, but the sequence is roughly the same.

Discovery. One to two weeks. You look at the current site, the analytics, the user feedback, the competitive landscape, and the business goals. You articulate what the redesign needs to accomplish in measurable terms. Not ”make it feel modern.” Something like ”increase the trial signup rate on the pricing page from 2 percent to 3 percent.” Measurable targets keep everyone honest later.

Strategy and structure. Two to three weeks. You decide on the site map, the page hierarchy, the content strategy, and the visual direction. This is where a lot of designers want to jump straight to Figma. Do not. Locking the strategy before opening the design tool saves weeks of rework.

Design. Four to eight weeks depending on site size. Wireframes first, then visual design, then components, then full pages. Iterate on the difficult pages (homepage, key landing pages, checkout) more than the easy ones. Not every page needs the same amount of design time.

Build and launch. Four to eight weeks. The actual implementation, testing, content migration, SEO preservation (keeping URLs intact where possible, setting up 301 redirects where not), and go-live. The build phase is where SEO work happens. A redesign that ships without a redirect map has just deleted its own search traffic.

Total realistic timeline for a mid-sized site: three to five months from decision to launch. Anyone selling you a four-week full redesign is either lying about the scope or lying about the quality.

The mistakes I see most often

Redesigning without a plan for content. New design, old content, no thought given to what actually goes on each page. The design ends up feeling empty or over-decorated because there is nothing solid to hang it on.

Ignoring SEO in the transition. Changing URLs without redirects, changing page structure without preserving keywords, removing content that ranked. A redesign can tank your search traffic overnight if nobody is thinking about it. Assign someone specifically to protect the SEO before the site goes live.

Redesigning by committee. Every stakeholder wants their thing on the homepage. The homepage cannot be about everything. Someone needs the authority to say no, and they need it in writing before the project starts.

Choosing a designer or agency on portfolio alone. The portfolio shows finished work, not how the process runs. For more on this, see my post on what to ask when you hire a designer. Process fit matters more than any one shiny screenshot.

Trying to fit brand work into a design project. If you also need a brand refresh, know that. Budget for it, schedule it, and do it in the right order. I wrote about the difference in brand visual identity vs logo. Redesigning a site on top of a brand that is not resolved yet produces a site you will redesign again in two years.

The right question to start with

The best redesigns start with a clear, honest answer to one question. What specifically will this site do better after the redesign than it does today? If you can answer that in one sentence with a measurable outcome, you are ready to start the website redesign process. If you cannot, you are not ready yet, and starting anyway will cost you more than waiting a few weeks to figure it out.

For related thinking on scoping a first version rather than a redesign, see MVP design and how to know what to build first. Many of the same discipline principles apply. And for a good outside perspective, the Nielsen Norman Group’s comparison of radical redesign and incremental change is one of the few resources that treats this decision with the seriousness it deserves.