Why most redesigns fail
Most SaaS product and website redesigns restyle the surface and keep the old problem. A short checklist for deciding what to change before you redesign.
- Note
- June 2026
- 2 min read
Most redesigns fail because they treat a strategy problem as a styling problem. They change how the thing looks without revisiting what it is for, so the new surface sits on the same unresolved intent and the same problems come back wearing nicer clothes. For a SaaS product or marketing site, that means checking what users actually struggle with, and what the site needs to say now, before anyone touches the visuals.
A common pattern: a team spends months on a redesign, launches it, and a few months later the same complaints are back. Usually the colors, type and layout changed, but nobody went back and asked what the product or site is for now. That’s a restyle. It’s fine if that’s what you need, it just won’t fix the problem.
Restyling is not redesigning
Most redesigns change the surface and leave the substance untouched. New colors, new type, new layout, sitting on top of the exact same unexamined idea of what the thing is for. That is restyling, and it can be worth doing, but it is rearranging the furniture in a house with a broken foundation. The intent was never revisited, so the original problem is still load-bearing.
A redesign that does not revisit the intent is just the old problem in new clothes.
What a real redesign starts with
- Re-ask what it is for. The answer that was true at launch may not be true now.
- Name what has changed: the audience, the market, the product, the goal. Redesign for the present, not the past.
- Decide what to remove. Most things that need a redesign are bloated, not lacking. Subtraction is the harder, better move.
- Write the intent in one sentence. If you cannot, you are about to restyle, not redesign.
Redesign the why first, and the surface has something true to follow. Skip it, and you will produce a more beautiful version of the same failure, on schedule, to applause, and you will be back here in a year. The new look is the easy part. The reason underneath is the work.
Before you redesign a SaaS product: a checklist
- Where do users drop off or get stuck? Check analytics and support tickets.
- What has changed since launch: audience, pricing, market, AI features?
- Which screens and pages matter most for revenue?
- What can be removed?
- Is the problem the design, the positioning or the product?
- Will search traffic survive? Plan redirects for any URL changes.
Redesign or polish?
If the intent still holds and only the surface is inconsistent, a focused polish across product, site and brand may be all you need. Partner (from US$6k/mo) handles that one focus at a time. If the intent has changed, start with Launch-style scoping.
Redesigning the why first is how we start every engagement, including our product design partnerships for SaaS and AI teams.
Asked & Answered
Because they treat a strategy problem as a styling problem. They change how the product looks without revisiting what it is for, so the new surface sits on the same unresolved intent and the same problems return.
Not visuals. Start by re-asking what the thing is for, what has changed since the last version, and what to remove, then write the intent in one sentence. The surface should follow that, not lead it.
Only once you know what the redesign has to fix. Otherwise it’s a restyle.
Keep reading
- Rebranding a live SaaS: identity, website and keeping your trafficHow to rebrand a live SaaS or AI product: what changes in the identity, website and product UI, the order to do it in, and how to keep your search traffic.
- SaaS dashboard design: what the first screen of a B2B product should showWhat a B2B SaaS dashboard should show first, how many KPIs belong on it, how to keep a data-dense screen readable, and when a redesign is worth it.
- Design systems for early-stage SaaS: when, how much, how smallDoes your startup need a design system? When to start one, how small it can be, and what to build first so your team and AI tools stay consistent.