I’ve worked in product teams where discovery was treated as a phase.

We would conduct interviews.

Write requirements.

Validate an idea.

Then move on to delivery.

It looked like a healthy product process.

But over time, I noticed something.

The teams that consistently made better product decisions weren’t necessarily doing more discovery.

They had simply made curiosity part of their everyday work.

That’s what a discovery culture really means.

It’s not about adding more research activities to the calendar.

It’s about creating an environment where teams are encouraged to question assumptions before investing heavily in solutions.

Discovery Isn’t a Product Manager’s Job Alone

One of the biggest shifts I’ve seen is when discovery stops being something the Product Manager does before handing work to the rest of the team.

Engineers ask questions about the problem.

Designers speak directly with customers.

Data analysts challenge assumptions with behavioural evidence.

Customer Success brings patterns from customer conversations.

Sales explains what prospects are struggling with.

Everyone contributes.

When discovery becomes a team activity, you get perspectives that a single function simply can’t provide.

Start With Questions, Not Solutions

A discovery culture begins with the questions teams ask.

Instead of:

“How quickly can we build this?”

Try:

“What problem are we solving?”

Instead of:

“Can we add this feature?”

Ask:

“What is the customer trying to accomplish?”

Instead of:

“When can we launch?”

Ask:

“What would we need to learn before we’re confident enough to launch?”

These questions slow the conversation down for a moment.

But they often prevent much bigger mistakes later.

Make Customer Contact Normal

I’ve always believed that Product Managers shouldn’t be the only people talking to customers.

When engineers and designers hear customer problems directly, something changes.

The problem becomes real.

A support ticket is no longer just a ticket.

A feature request becomes a conversation.

A usability issue becomes something the team can visualize.

You don’t need every team member on every customer call.

But regular exposure to customers can dramatically improve product judgment.

Reward Learning, Not Just Being Right

This is probably one of the hardest parts of building a discovery culture.

Teams need to feel safe discovering that their original assumption was wrong.

Imagine spending two weeks researching an idea and concluding that customers don’t actually need it.

That’s not wasted work.

That’s a successful discovery outcome.

But if the organization treats it as failure, people will learn to avoid uncomfortable findings.

Eventually, discovery becomes confirmation.

People look for evidence that supports what they already want to build.

That’s the opposite of a healthy discovery culture.

Make Evidence Visible

Another practice I’ve found useful is making customer evidence accessible.

Research notes.

Interview recordings.

Support themes.

Product analytics.

Experiment results.

When evidence is hidden inside individual documents or conversations, teams naturally fall back on opinions.

When evidence is visible, discussions become more grounded.

Instead of saying:

“I think customers want this.”

Someone can ask:

“What evidence do we have?”

That’s a much healthier product conversation.

Don’t Turn Discovery Into Bureaucracy

There’s a danger on the other side too.

Teams can create so many discovery processes that discovery becomes a bottleneck.

Mandatory interviews.

Long research documents.

Multiple approval meetings.

Heavy templates.

That’s not discovery culture.

That’s process.

Good discovery should help teams learn faster, not create more paperwork.

Sometimes five customer conversations are enough.

Sometimes you need deeper research.

The method should match the uncertainty.

Connect Discovery to Delivery

Discovery shouldn’t happen in isolation from execution.

The strongest teams I’ve worked with create a continuous loop:

Discover → Build → Measure → Learn → Discover again

Customer insights influence what gets built.

Product behaviour creates new questions.

Experiments provide new evidence.

That evidence influences the next decision.

The process never really ends.

Leadership Sets the Tone

Culture doesn’t change because someone creates a new product framework.

Leaders influence it through the questions they ask.

If leadership asks only:

“When will this ship?”

Teams will optimize for delivery.

If leadership also asks:

“What have we learned?”

“What assumptions are we testing?”

“What evidence supports this decision?”

The team’s behaviour starts to change.

What leaders repeatedly ask for becomes what teams prioritize.

Final Thought

I’ve come to believe that a discovery culture isn’t about doing more research.

It’s about becoming more comfortable with uncertainty.

It’s creating a team where people can say:

“We don’t know yet.”

And instead of immediately debating opinions, the next question becomes:

“How can we find out?”

That’s the behaviour I associate with strong product teams.

They don’t assume they have all the answers.

They build systems that help them find better answers faster.

Because great products aren’t created by teams that are always right.

They’re created by teams that are willing to keep learning.