About the author
Vinko Borčić
Project Manager and Product Owner
To ensure you build the right solution for the right problem, product discovery is a critical step that comes before development. This way, teams can identify opportunities, validate ideas, and set a clear direction before investing a lot of resources into development. 34% of startups that fail cite a lack of product-market fit, something that can be remedied by product discovery. Here’s how you can conduct product discovery successfully:
Understanding the foundation
Product discovery starts with gaining clarity around your objectives and limitations. Step one is to clarify your business context and constraints before you even conduct customer research or begin ideation.
To begin, try answering basic questions:
- What business outcomes are you trying to achieve?
- Do you want to make more money, keep customers coming back, go to a new place, or fix a problem?
Knowing your objectives will help you with the discovery process and evaluating ideas against real success. Write down any limitations you know about, like the budget. These limits help you concentrate your exploration and eliminate wasting time on things that can’t happen.
The ideal product team structure
For product discovery to work effectively, it requires a core product trio made up of people from different teams. This balanced team structure typically includes:
- Product manager who focuses on business viability and strategic fit. They help ensure that the right problems are solved and that the solution will drive business results.
- Product or UX designer makes sure that the solution is desirable and workable for the customers.
- Software engineer (usually senior or software architect) who assesses which solutions can be built and the optimum method for implementation.
This balanced team structure makes sure that all three critical perspectives – business viability, user desirability, and technical feasibility – are properly represented during the discovery process. When you have all three perspectives involved right from the beginning, you can avoid designing solutions that can't be built, won't be liked by users, or don't make business sense. Every core team member should be a part of customer research, ideation, and decision-making, not functioning in isolated handoffs. This common context means we're all on the same page and decisions can be made faster and more thoughtfully.
Phase 1: Research & understanding
Step 1: Stakeholder interviews
Start by interviewing internal stakeholders—executives, sales teams, customer support, and teams that interface with users. These talks reveal what the organization knows, where it wants to go, and identify any potential roadblocks.
Questions to ask
- What problems do they believe customers are facing?
- What patterns have they observed in customer feedback?
- What business goals need advancement?
- What constraints or requirements should be considered?
Record these insights and identify trends and contradictions. Though useful, stakeholder views might not match actual customer needs.
Step 2: Customer research
Now, move to direct customer interactions. This might be the most important in product discovery. Use a mix of quantitative and qualitative methods.
- Talking to users – Conduct deep conversations with current and prospective users to learn about their workflow, challenges, and goals.
- Get more feedback from more people to find trends and back up your best guesses.
- Examine user behavior through analytics to find friction points and opportunities.
- To see how users currently solve problems, observe them in their natural environment.
Gain insight into customers’ jobs-to-be-done, current solutions, and desired emotional and functional outcomes. There is more to what customers demand than what they say, so find out the truth behind this.
Step 3: Examining the market and the competitors
Look at the market and your business’ competitors.
- Identify direct and indirect competitors
- Analyze competitor strengths and weaknesses
- Review industry reports and trends
- Examine adjacent markets for inspiration
This context helps you spot opportunities to stand apart and not make existing things.
Phase 2: Comprehensive analysis and market insights
Step 4: Problem framing
Combine your research results into clear problem statements. A well-framed problem statement articulates:
- Who is experiencing the problem
- What the specific challenge is
- Why it matters to them
- How it impacts their goals
Make many problem statements that show different user groups. Then, prioritize them based on:
- Business impact
- Customer pain level
- Frequency of occurrence
- Strategic alignment
Step 5: Opportunity mapping
Transform your problem statements into opportunity spaces. While problems focus on what is wrong, opportunities focus on future possibilities and value creation. Design an opportunity map that shows how different problem areas relate to possible solutions. It allows teams to identify the bigger view and strategic areas for innovation.
Phase 3: Continuous discovery approach
Step 6: Setting a routine for discovery
The process of discovery should not be considered as a one-time project but rather a rhythm.
Establish weekly touch points with customers to keep validating assumptions and collecting insights. Continual interactions with your customers will help you understand their changing needs early on, allowing you to change your focus before spending huge resources on development.
Step 7: Connect opportunities to solutions
Make a visual connection map for your high-level business outcomes and customer opportunities and then to solutions. This allows you to understand why you’re doing things and how each contributes toward meaningful outcomes. When you find an opportunity, think of multiple solutions. This can help prevent us from making the mistake of defaulting to the first idea. When you explore different ways of solving the same problem, you often come up with better solutions.
Step 8: Small-batch testing
Instead of holding off on condoning a whole product idea, break down the thinking into small ideas. Every week, think about the crucial assumptions that drive your current direction or solution and design lightweight ways to test them. You can try tests like low-fidelity prototypes, concept walkthroughs, or mini-experiments with live features. The aim is to get proof regarding what works before going in for the pledge.
Phase 4: Collaborative decision-making
Step 9: Evidence-based choices
As you create insights through your constant questioning work, decide through evidence, not opinion. Make it easy to monitor what you learn and how it impacts your path. When talking about options with your team, orient the discussion on customer evidence: “What have we heard from customers that supports or challenges this direction?” This means talking about what customers think instead of what you prefer, which is more objective.
Step 10: Breaking down silos
Let engineers, designers, and other team members join the discovery process. When they hear it directly, it gives technical people important context for what they implement. When teams collaborate, information is not lost in translation, and technical work can inform the discovery work from day one.
Phase 5: Developing a discovery culture
Step 11: Continuing the training
Make your team regularly schedule conversations with customers and experiments. Schedule regular times for these, just like sprint planning and sprint review. This ensures they don’t get displaced by delivery pressures.
Step 12: Balancing discovery with delivery
Product teams often feel pressured to choose between learning what to build and building it. Instead of thinking of these as things in competition to one another, think of these as things that work together, which happen alongside each other. When you have a continuous discovery practice along with delivery, you can course-correct with new learnings and without dragging your delivery timeline.
Conclusion
Good product discovery isn't something you complete and move on from. It's a continuous practice done in parallel with delivery.
When you get into the habit of doing discoveries regularly, talking with your customers continuously, and testing assumptions in small batches, you create a learning engine that consistently delivers value.
The best product teams don’t see discovery as a project that has a start and finish but as a perpetual discipline that informs everything you do. They create space for regular customer conversations, small experiments, and evidence-based pivots – even when pressure is high to deliver.
Remember that discovery is both a science and an art. The process offers structure, but genuine curiosity, empathy for users, and the bravery to question key assumptions are what enable success. Taking the time to understand problems iteratively means you’re more likely to create solutions that matter.
