A redesign won't fix the wrong problem. The right questions might.
It's one of the most common messages I receive.
"We're thinking about redesigning our product."
Whenever I hear that, I ask the same question.
"What's driving the redesign?"
Sometimes the answer is clear.
The product feels outdated.
Conversions have dropped.
Users are struggling with onboarding.
Support tickets are increasing.
But just as often, the answer is surprisingly vague.
"We want something more modern."
"Our competitors look better."
"We think it's time for a refresh."
Those reasons might justify a visual update.
They don't necessarily justify a redesign.
A redesign is one of the most expensive decisions a product team can make.
It consumes time, engineering resources, design effort, and attention.
If you redesign the wrong thing, you'll end up with a better-looking product that still has the same business problems.
Before changing a single screen, ask yourself these ten questions.
1. What Problem Are We Actually Trying to Solve?
A redesign should always begin with a business problem, not a design preference.
Are users struggling to complete important tasks?
Has activation dropped?
Are conversions declining?
Is customer retention getting worse?
Or do you simply dislike how the interface looks?
Those are very different situations.
If you can't clearly define the problem, you probably aren't ready to redesign.
2. What Does Success Look Like?
"Better UX" isn't a measurable goal.
Instead, define success in business terms.
For example:
Increase trial-to-paid conversion.
Reduce onboarding drop-off.
Improve feature adoption.
Decrease support tickets.
Increase customer retention.
Shorten sales cycles.
A redesign without measurable outcomes quickly becomes subjective.
3. What Are Users Actually Saying?
Founders often redesign based on assumptions.
Customers usually tell a different story.
Read support conversations.
Review customer interviews.
Watch session recordings.
Look for repeated patterns.
One complaint isn't enough.
Twenty similar complaints usually point to a real usability issue.
Design should solve recurring problems—not isolated opinions.
4. What Does Your Data Say?
Opinions are useful.
Behavior is better.
Analytics often reveal problems users never report.
Look at where people:
Leave onboarding.
Abandon forms.
Stop using key features.
Drop out of important workflows.
Your analytics show what happened.
User research helps explain why.
You need both.
5. Are You Solving a UX Problem—or a Product Problem?
Not every issue requires a redesign.
Sometimes users are confused because the messaging is unclear.
Sometimes pricing creates friction.
Sometimes onboarding delays the first moment of value.
Sometimes a feature simply isn't useful.
Changing colors won't solve any of those problems.
Before redesigning the interface, make sure you've identified the real cause.
6. Which Parts Already Work Well?
One mistake I see during redesign projects is replacing everything.
That's rarely necessary.
Every product has strengths.
Maybe users love the navigation.
Maybe reporting is intuitive.
Maybe the dashboard already supports great decision-making.
Protect what's already working.
A redesign should improve the experience—not erase it.
7. What Business Objective Does Each Change Support?
Every major design decision should answer one question:
"How does this help the business?"
Does it improve activation?
Increase trust?
Reduce support requests?
Encourage upgrades?
If a change doesn't support a meaningful outcome, ask whether it's worth making at all.
Design isn't about changing interfaces.
It's about changing results.
8. Are You Redesigning for New Users or Existing Customers?
These audiences often have different needs.
New users need clarity.
Existing customers value familiarity.
A redesign that excites prospects but frustrates loyal customers can create unnecessary friction.
The best redesigns improve the experience without forcing users to relearn everything.
9. Can Small Improvements Solve the Problem?
Not every challenge requires a complete redesign.
Sometimes a better onboarding flow is enough.
Sometimes rewriting interface copy removes confusion.
Sometimes simplifying navigation has a bigger impact than rebuilding the entire product.
Look for the highest-impact, lowest-effort improvements first.
A thoughtful evolution often outperforms a dramatic redesign.
10. Have You Watched Someone Use Your Product?
This might be the most important question of all.
Sit beside someone who's never used your product.
Ask them to complete a common task.
Don't help.
Don't explain.
Just watch.
Where do they hesitate?
What confuses them?
Which assumptions did your team make that users don't share?
Those moments are incredibly valuable.
They reveal problems no design review ever will.
The Questions Matter More Than the Mockups
A successful redesign isn't measured by how different the interface looks.
It's measured by whether the product performs better afterwards.
Better onboarding.
Higher activation.
More confident users.
Fewer support tickets.
Greater customer trust.
More meaningful business growth.
The interface is simply the visible result of better decisions.
Final Thoughts
Design is often mistaken for the last step in product development.
I see it differently.
The best design work happens before the first wireframe.
It starts by understanding the business.
Understanding the users.
Understanding the problem worth solving.
Only then should pixels start moving.
A redesign shouldn't be driven by trends.
It should be driven by evidence.
Because when you solve the right problem, good design becomes much easier.
Not Sure If Your Product Needs a Redesign?
Sometimes the biggest opportunity isn't rebuilding your product.
It's identifying the friction that's quietly holding it back.
That's exactly what a UX audit is designed to uncover.
I help SaaS companies and growing businesses evaluate their products through the lens of user behavior, business goals, and conversion—not just visual design.
A typical audit focuses on:
User journeys and onboarding
Landing page clarity and messaging
Information architecture
Dashboard usability
Conversion friction
UX debt and usability issues
Actionable, prioritized recommendations
The goal isn't to recommend a redesign.
The goal is to help you understand what will have the biggest impact on your product and your business.
Sometimes that's a redesign.
More often, it's a series of smarter decisions.
The best redesigns don't begin with Figma. They begin with better questions.
If you had to redesign just one part of your product tomorrow, what evidence would you use to decide where to start?
