Product Discovery Basics: Training

Product Discovery is the process by which teams determine which problem they should solve for which target audience, before investing a lot of time in development. The goal is to mitigate risks early on and focus only on solutions that deliver real value.

• Understanding user needs and jobs-to-be-done (e.g., interviews, observation)

• Identifying and prioritizing assumptions

• Quickly test solution options (prototypes, fake doors, MVP experiments)

• Define success metrics (e.g., activation, conversion, retention)

This creates a solid foundation for product strategy and roadmap: start with the most important assumptions.

The discovery phase is the early stage of a project or product in which the problem, target audience, and proposed solution are defined. It provides direction before design and development move into implementation.

• Define objectives, scope, and success metrics

• Conduct user and market analysis (qualitative & quantitative)

• Formulating hypotheses and prioritizing risks

• Iteratively validating concepts (prototyping, testing, data)

• Create a decision-making template for “Build/No-Build”

The result is usually a clear, tested solution, ideal for then moving on to delivery or implementation with a clear focus.

A discovery product is not a “finished” product, but rather a validatable artifact that helps identify the right solution. It serves to test assumptions and make learning progress measurable, quickly and with minimal effort.

• Prototype or click-through mockup for usability testing

• Landing page or “fake door” for testing demand

• Concierge/Wizard-of-Oz approach to simulate value

• MVP with minimal functionality and clear metrics

• Experiment setup (tracking, A/B testing, survey)

It’s important to remember: A discovery product answers specific questions. Choose the format that will most quickly reduce your greatest uncertainties.

Discovery ensures that a team prioritizes the right problems and finds the right solution before resources are poured into features that no one uses. The focus is on learning, validation, and clear decision-making.

• Understanding customer problems and their causes (research, data analysis)

• Refine the value proposition and segment the target audience

• Evaluating ideas: Value, feasibility, effort, risk

• Testing and iterating concepts (tests, experiments, feedback)

• Translating insights into clear requirements and priorities

This makes product development more predictable and effective. Start with the top three risks, and test them first.

Product discovery refers to the process of defining a product or feature in such a way that it meets a genuine need and makes economic sense. It often involves understanding the problem, generating ideas, and validating them in the market.

• Identifying needs: user problems, market trends, data

• Define the target audience and value proposition

• Develop and compare potential solutions

• Assess demand and usability (tests, MVP, pilot)

• Prioritize and develop a realistic plan

The process varies depending on the industry and stage of development. The best next step: Formulate a clear problem statement and test it with real users.

In product management, product discovery is the systematic phase that precedes implementation, during which product managers work with design and engineering teams to determine what is worth building. It combines a user-centric approach, business objectives, and technical feasibility.

• Defining problems and goals, including metrics (outcome rather than output)

• Research: Interviews, analytics, competitive analysis

• Hypotheses and prioritization (e.g., RICE, Opportunity Scoring)

• Prototyping & experiments for validation

• Handoff to Delivery: Clear Requirements, Risks, and Lessons Learned

This makes roadmapping more robust and stakeholder communication easier. Treat discovery as an ongoing process, not just a one-time phase.