Skip to content
Product discovery

Drive innovation with product discovery frameworks: the complete guide

By Clément Gauthier 9 min read

Design thinking, impact mapping, Lean Startup, OKRs: the product discovery frameworks used by Google, Amazon and Netflix to solve problems and innovate.

Product discovery has changed the way teams approach problem solving, idea generation and product development. Leading companies like Google, Amazon and Netflix rely on product discovery frameworks to innovate more.

This guide presents the main frameworks and techniques that help product teams align strategy, user needs and execution, so they can deliver products that truly resonate with their target audience.

To go further and learn how to launch discovery in your organization, see our Product Discovery in 2025 guide.

Understanding product discovery and why it matters

Product discovery is the process of identifying and understanding users' problems and needs, in order to design and build a product that offers relevant solutions. Industry figures like Marty Cagan and Teresa Torres advocate continuous discovery, an essential part of any product team's journey: this approach helps product managers ensure a good fit between the product and the market.

The process is organized around three main steps:

  • Identify the problem space: spot users' friction points and the company's challenges;
  • Generate ideas: come up with solutions alongside a cross-functional team;
  • Validate ideas: test the viability of the solutions you're considering with MVPs (Minimum Viable Products) or user feedback.

To understand how it differs from user research, also read the difference between product discovery and user research.

The product manager's role in discovery

Product managers play a central role: they have deep knowledge of customers, market dynamics and product strategy. They work with development and delivery teams so solutions stay aligned with the product vision and address real problems. Their main responsibilities in discovery:

  • define the problem space and articulate user needs;
  • collaborate with product teams to generate and validate ideas;
  • prioritize solutions based on their potential impact on the business and on customers.

Well-known discovery frameworks: design thinking and impact mapping

Design thinking

Design thinking is a widely used discovery framework, popularized by the design agency IDEO. This human-centered methodology encourages teams to empathize with users, define problems, design solutions, prototype and test. It helped shape the discovery process of companies like IBM and Ford. The focus stays on the user experience, and the iterative nature of the process allows for continuous discovery and refinement. Its core principles:

  • empathize with users: deeply understand their needs and friction points;
  • ideate solutions: explore a wide range of possible directions;
  • prototype and test: quickly build and validate prototypes to refine solutions.

Impact mapping

Impact mapping, developed by Gojko Adzic, is another key framework: it helps teams define strategic goals, visualize the links between business objectives, user needs and possible solutions, and understand how their product can influence user behavior. It follows an “actor – goal – impact” structure: who the product is for (actor), which goals it helps achieve (goal) and which results are expected (impact). The main steps:

  • define business goals: establish the results expected from the product;
  • identify the target audience segments: recognize the different groups of users the product wants to serve;
  • surface needs and friction points: understand the specific problems the product solves for each segment;
  • ideate solutions: generate a wide range of ideas that meet the needs and contribute to the goals.

Starting the process: defining the problem

The process usually begins with defining the problem. Product teams seek to understand their customers and their challenges. Techniques like job outcome mapping help focus on the problems to solve. For example, Amazon's practice of writing the press release for the future product in advance helps visualize the problem and the solution from the customer's point of view.

From problem to solution: generating and testing ideas

Once the problem is defined, teams move on to generating solutions, then test the ideas likely to solve the problems they've identified. Several tools help them do so:

  • the idea validation grid, which lets you assess the feasibility and value of potential solutions, and so select ideas and prioritize features;
  • the MVP and the Lean Startup approach, championed by Eric Ries and Steve Blank: you build a minimum viable product, test it, then refine it iteratively based on customer feedback. Companies like Uber have applied this method to quickly validate their ideas and adjust their product strategy;
  • the KANO model and the MoSCoW method, which help rank features.

Continuous discovery: the key to lasting success

Continuous discovery, advocated by Teresa Torres, invites teams to build these activities into their work on a regular basis rather than in isolated phases. It relies on ongoing user experience testing, constant contact with customers and iterative feedback loops that feed the product roadmap.

Its benefits:

  • react faster to changes in the market and in user needs;
  • limit the resources wasted on unviable solutions;
  • encourage a culture of experimentation and learning across the organization.

These techniques and frameworks aren't rigid processes: they should adapt to the team's needs and the nature of the problem. Jeff Gothelf, co-author of “Lean UX,” also champions a user-centered approach: he encourages product teams to use design thinking and iterative validation techniques to create products that truly meet users' needs.

Aligning team efforts with product strategy: OKRs and Mission Briefing

Goal-setting frameworks like OKRs (Objectives and Key Results), used by Google and other tech giants, emphasize clear objectives and measurable key results to align product strategy and team efforts. Similarly, the Mission Briefing method, proposed by Stephen Bungay, guides teams to agree on the “what” and the “why” of a product, while leaving them to decide the “how,” which fosters creativity and ownership.

Discovery and delivery: finding the right balance

To succeed in product management, you need to find the right balance between discovery and delivery. Discovery aims to identify and validate the right problems to solve and the right solutions to build; delivery ensures those solutions are actually built, tested and rolled out to customers. Product managers play a pivotal role in this balance: they work with cross-functional teams to ensure a smooth transition from one to the other. By integrating discovery and delivery, organizations drive innovation while keeping a strong focus on execution and customer satisfaction.

Fostering a discovery culture: the examples of Netflix, Amazon and Google

Succeeding at discovery isn't only about choosing the right framework or technique: you also need to cultivate an environment that supports it. Netflix and Amazon have thrived by empowering their teams and maintaining a culture of freedom and responsibility, which has let them drive product innovation.

  • Amazon takes a customer-centric approach: understanding user needs and developing innovative solutions. Its recommendation system, which uses data to offer personalized suggestions, is one example.
  • Netflix relies on constant attention to the user experience and on continuous discovery. The company constantly uses A/B testing and data-driven decision making to optimize its platform and content.
  • Google has long championed product discovery, drawing on design thinking and user-centered approaches to create solutions like Google Maps or Google Assistant.

What the experts say

A few references for understanding the discipline:

  • Marty Cagan, a former product executive at eBay and founder of Silicon Valley Product Group, stresses the importance of continuous discovery and urges teams to solve real problems for real customers. For him, the goal of discovery is to manage risk before investing in delivery.
  • Teresa Torres, a product discovery coach, developed “Opportunity Solution Trees,” which help teams visualize and systematically explore possible solutions.
  • Tim Herbig, a product leader and author, promotes lean and agile development practices and rapid hypothesis validation through prototyping. He advocates a flexible approach that adapts to market changes and new learnings.
  • Jeff Gothelf, co-author of “Lean UX,” champions the user-centered approach described above.

To dig deeper, you can read “Inspired” by Marty Cagan, “The Lean Startup” by Eric Ries or “Continuous Discovery Habits” by Teresa Torres.

Measuring discovery success

To assess how effective discovery is, teams can track a few key indicators:

  • time to market: the time it takes for a product or feature to go from the initial idea to production;
  • customer satisfaction: user feedback, measured for example with Net Promoter Score (NPS) or customer surveys;
  • product-market fit: how well the product meets the needs of the target audience, visible in engagement, retention and growth;
  • return on investment (ROI): the product's financial benefits relative to development and maintenance costs.

Adopting discovery frameworks to succeed

Product discovery frameworks are an essential part of product management: they help teams move from understanding the problem space to exploring the solution space. The path is complex and full of uncertainty, but frameworks like design thinking, impact mapping or Lean Startup provide the structure and direction you need. The right choice depends on the team's structure, the nature of the problem, the market environment and the organization's culture. With the right frameworks and a team that collaborates, organizations reduce risk and build high-performing, user-centered products.

Written by Clément Gauthier All articles

Did you like this article?

In 30 minutes, see what Screeb shows on your own journeys.

Shall we look at your journeys together?