One lesson I’ve learned in product management is that good ideas aren’t necessarily good opportunities.

A customer might ask for a feature. A stakeholder might have a strong opinion. Product data might show an obvious drop-off.

All of these are useful signals.

But before deciding what to build, we need to understand the problem behind them.

That’s where Design Thinking can be useful in product discovery.

Start With Empathy

The first step is understanding the people experiencing the problem.

This sounds obvious, but it’s easy to skip.

Product teams often rely on assumptions because they already know the product, the market, and the customer.

Design Thinking encourages us to step back and understand the customer’s experience directly.

Talk to customers.

Observe how they work.

Understand their environment, constraints, goals, and frustrations.

Don’t just ask what they want.

Try to understand what they are actually trying to accomplish.

Define the Real Problem

Discovery often produces a lot of information.

The challenge is figuring out what matters.

A customer might say, “We need better reporting.”

That’s a request, not necessarily the problem.

Dig deeper.

What decisions are they trying to make?

What information are they missing?

How do they solve the problem today?

What happens when they can’t get the information?

You might discover that the real problem isn’t reporting at all. It could be that customers spend hours manually combining information from different parts of the product.

A good problem definition creates better options later.

Don’t Fall in Love With the First Solution

Once a problem is identified, teams can quickly jump into solution mode.

Design Thinking encourages divergence before convergence.

Generate multiple ways to solve the problem.

Could we simplify the workflow?

Automate part of it?

Change the information architecture?

Provide better defaults?

Give users a template?

Build a new feature?

The point isn’t to generate ideas endlessly.

It’s to avoid assuming that the first solution is automatically the best one.

Prototype Before You Commit

One of the biggest advantages of Design Thinking is the emphasis on making ideas tangible early.

A prototype doesn’t have to be a working product.

It could be a wireframe, clickable mockup, workflow diagram, or even a manually created experience.

The goal is to learn.

When customers interact with something concrete, you can uncover problems that wouldn’t appear in a conversation.

They might misunderstand the workflow.

They might ignore a feature you thought was important.

They might use the solution in a completely different way.

That’s valuable discovery.

Test Assumptions, Not Just Designs

A common mistake is treating usability testing as a final design check.

But product discovery should test assumptions much earlier.

Do customers actually have this problem?

Is it frequent enough to matter?

Are they willing to change their behaviour?

Does the proposed solution fit their workflow?

Will solving it create meaningful value?

These are product questions, not just design questions.

Iterate Based on What You Learn

Discovery rarely produces a perfect answer on the first attempt.

You may learn that the problem is smaller than expected.

You may discover another segment has a much stronger need.

You may find that your proposed solution solves the wrong part of the workflow.

That’s why iteration matters.

Go back, refine your understanding, test another approach, and continue learning.

The objective isn’t to defend the original idea.

It’s to improve your understanding until you have enough confidence to build.

Don’t Turn Design Thinking Into a Checklist

Empathize.

Define.

Ideate.

Prototype.

Test.

These steps are useful, but product discovery isn’t about completing them mechanically.

Sometimes you need to interview customers before defining the problem.

Sometimes a prototype reveals that you need to return to discovery.

Sometimes the best outcome is realizing you shouldn’t build anything yet.

The framework should support better thinking, not become another process to follow.

Final Thought

Design Thinking is valuable in product discovery because it creates space between hearing a problem and building a solution.

That space is where much of the important product work happens.

You understand the customer.

Challenge your assumptions.

Explore alternatives.

Test ideas early.

Then decide what is worth building.

The goal isn’t simply to build products that customers can use.

It’s to understand the problem well enough to build something they actually need.