I do not recommend a website redesign as a default solution anymore.
That does not mean a website should never change. It means “redesign” often describes a large visual project before anyone has explained what the business needs to improve.
A new look can be satisfying. It can also leave the important problems untouched: unclear positioning, weak proof, confusing navigation, slow pages, poor qualification, or a contact path nobody follows up on.
The first question should be what the current website is failing to do. If visitors do not understand who the business serves, changing colors will not solve it. If qualified people cannot find the next step, a new homepage animation will not solve it. If the team cannot maintain the site, a more elaborate design may increase the burden.
I prefer focused improvements. Clarify the offer. Remove pages that do not help. Strengthen a case study. Make the inquiry path more direct. Improve the mobile experience. Reduce unnecessary scripts. Replace a fragile publishing setup when the operating model calls for it.
This approach is less dramatic than a redesign, but it produces better questions. What changed? Who benefits? How will we know? Which existing URLs, assets, and content still matter?
There are times when a new visual system is justified. A business may have changed its audience, merged brands, outgrown its information architecture, or inherited a site that cannot be repaired safely. In those cases, the work should begin with strategy and structure, not a mood board.
A website is not a piece of furniture that needs replacing because it looks dated. It is part of an operating system for the business. Improve the parts that create friction, preserve what already works, and only rebuild when the evidence says the foundation itself needs to change.