A product can have beautiful UI, excellent UX, and a sophisticated design system and still fail.
The reason is simple:
Good design doesn't guarantee a good product.
A product can be easy to use but solve a problem nobody cares about.
It can be technically impressive but commercially unsustainable.
It can have excellent onboarding but attract the wrong users.
This is where Product Design meets Product Strategy.
Design the right problem first
Teams often jump from:
Business request → Feature → Design
But there's an important step missing:
Problem
Before designing a solution, ask:
Who has the problem?
How important is it?
What evidence do we have?
What outcome are we trying to change?
This is where Jobs to Be Done, associated with Clayton Christensen, becomes useful.
Instead of asking:
"What feature should we build?"
Ask:
"What is the user actually trying to accomplish?"
The answer can completely change the solution.
Design solves. Strategy chooses.
This is one of the most useful distinctions in Product Thinking.
Design asks:
How can we solve this problem well?
Strategy asks:
Which problem should we solve?
A Product Designer working strategically needs to understand both.
For example:
A team might ask for a loyalty dashboard.
But research could reveal that users don't actually need another dashboard.
They need to understand:
"How close am I to my next reward?"
The solution might therefore be a progress experience rather than a dashboard.
Same business request.
Different problem.
Better outcome.
Three questions every product should survive
A useful framework is the intersection of:
Desirability
Do people want it?
Feasibility
Can we build it?
Viability
Can the business sustain it?
A product needs all three.
Something people love but cannot realistically build doesn't work.
Something technically impressive that nobody needs doesn't work either.
And something users want that destroys the business model has a fairly obvious problem.
Don't confuse engagement with value
A product can increase clicks, notifications, or session time without creating meaningful value.
Behavioral design helps influence action, but the goal shouldn't be more activity.
It should be better outcomes.
This connects to the Fogg Behavior Model, which frames behavior around motivation, ability, and prompts.
The question isn't:
"How do we make users do this?"
It's:
"How do we make the valuable action easier and more meaningful?"
That distinction matters in products using gamification, rewards, recommendations, and notifications.
The cost of solving the wrong problem
The biggest product waste often happens before development.
A wrong decision can create:
unnecessary features
engineering rework
design debt
maintenance costs
poor adoption
wasted opportunity
By the time users reject the feature, the expensive part has already happened.
The real failure started when the team chose the wrong problem.
A better Product Thinking loop
Instead of:
Brief → Design → Build → Ship
Try:
Problem → Evidence → Opportunity → Solution → Outcome
This doesn't mean research forever.
It means creating enough confidence to make a better decision.
As Don Norman's work around human-centered design demonstrates, understanding how people actually interact with systems is fundamental to creating useful experiences.
Takeaway
Great Product Design isn't about making every solution beautiful.
It's about helping teams solve the right problem.
The strongest Product Designers know when to:
question the brief, investigate the problem, validate assumptions, simplify the solution, and measure the outcome.
Sometimes the best design decision isn't improving a feature.
It's deciding not to build it.
