Product discovery Isn't a Phase. It's a Practice. Most product teams think discovery ends before ...Product discovery Isn't a Phase. It's a Practice. Most product teams think discovery ends before ...
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Lopamudra's avatar
Lopamudra Misra
• Jun 29
Product discovery Isn't a Phase. It's a Practice.
Most product teams think discovery ends before delivery begins.
I've learned the opposite.
Discovery is something that should continue throughout the life of a product.
A couple of experiences changed how I think about it.
The project that almost duplicated another product
We were about six weeks into a project.
The team had done everything "right":
User interviews
Problem statements
Opportunity assessment
Stakeholder alignment
We were preparing solution designs when someone casually mentioned that another internal team had been building a tool for the exact same problem.
Same users.
Same business problem.
Different implementation.
Nobody had checked.
Nobody had connected the dots.
We caught it just before development started, but it could have easily become months of duplicated effort.
That experience made me realize something important.
We hadn't skipped discovery.
We had simply defined discovery too narrowly.
A completely different project exposed the same weakness
About a year later, another product faced a different challenge.
A major regulatory decision completely changed the environment we were building for.
Suddenly:
assumptions became invalid
priorities shifted
stakeholder expectations changed
several weeks of work needed to be revisited
No amount of customer interviews would have predicted that.
But paying closer attention to external signals might have helped us prepare much earlier.
Different project.
Different problem.
Same lesson.
Discovery isn't only about customers.
It's about understanding the entire environment surrounding a product.
The Five Dimensions of Discovery
Over the years, working across B2B SaaS products, I've found that effective discovery usually spans five areas.
Most teams invest heavily in one.
Great teams invest across all five.
1. Customer Understanding
This is where discovery usually starts.
Understanding:
pain points
workflows
jobs to be done
current workarounds
But interviews alone aren't enough.
The goal isn't simply confirming a problem exists.
It's understanding how painful that problem actually is.
2. Organizational Context
One question has saved me from multiple mistakes:
Who else inside the organization is already solving this problem?
Internal tools.
Adjacent teams.
Existing initiatives.
Roadmap overlaps.
Ignoring these creates duplication, conflicting experiences, and missed collaboration opportunities.
3. External Signals
Markets evolve.
Competitors launch.
Regulations change.
Economic conditions shift.
These aren't events you can predict perfectly—but they are signals you can continuously monitor.
Discovery shouldn't stop once the PRD is written.
4. Technical Reality
The best solution on a whiteboard isn't always the best solution inside an existing architecture.
Early engineering conversations often uncover:
hidden dependencies
platform constraints
scalability considerations
opportunities to simplify
Technical discovery saves expensive redesign later.
5. Business Context
A solution can delight users and still be the wrong investment.
Business priorities matter.
Revenue goals.
Available resources.
Strategic direction.
Timing.
Great discovery balances user value with business reality.
Why teams still skip discovery
I rarely see teams skip discovery because they don't believe in it.
They skip it because:
it doesn't look like progress
leadership wants visible output quickly
customer interviews have structure, but organizational and business discovery usually don't
discovery gets treated as a kickoff activity instead of an ongoing practice
And that's where surprises happen.
Discovery is a habit, not a milestone
The strongest product teams I've worked with never truly "finish" discovery.
They continue validating assumptions.
They revisit changing conditions.
They monitor new signals.
They adapt.
Discovery becomes part of product thinking—not a box to check before delivery.
Because products don't exist in isolation.
They're shaped by customers, organizations, technology, markets, and business strategy—all changing at the same time.
The sooner we acknowledge that, the better decisions we make.
What dimensions of discovery do you think teams overlook most often?
I'd love to hear your experiences.
Back to feed
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started