Marty Cagan and Teresa Torres on Product Discovery: Different Layers of the Same Work
Comparing Marty Cagan's product model and four risks with Teresa Torres's continuous discovery habits: how they complement each other and where each fits.
Two names dominate how modern product teams talk about discovery: Marty Cagan, whose books describe what strong product organizations do, and Teresa Torres, whose habits turn discovery into a weekly routine. People compare them because both argue against building features from a list of requests, and because their vocabularies overlap.
What is the core difference?
Cagan's concern is the operating model. What kind of team, with what authority and what leadership, reliably builds products customers love? His answer centers on empowered teams that own problems rather than feature lists, and on dealing with risk before building.
Torres's concern is cadence. What does a team do every week to keep learning? Her answer is a set of habits: interview customers continuously, map opportunities, and run small experiments.
One describes the environment in which discovery succeeds. The other describes the work inside it.
What does Cagan say?
Marty Cagan, founder of the Silicon Valley Product Group, wrote Inspired (2008, updated 2017) and Empowered (2020, with Chris Jones). He distinguishes product teams that are empowered to solve problems from teams that implement feature requests, and argues that the second is the common failure.
His four risks are value, usability, feasibility, and viability. Discovery exists to address them before delivery, using prototypes and tests rather than full builds. Empowered describes the leadership needed to support this, including the roles of product leaders. His work is a practitioner's account drawn from companies he has worked with and advised, and SVPG sells training and advice.
What does Torres say?
Teresa Torres, a product discovery coach, wrote Continuous Discovery Habits (2021). Her central claim is that teams should do discovery continuously, with at least weekly customer touchpoints by the team making the product. She calls the product manager, designer, and engineer working together the product trio.
Her tools include the opportunity solution tree, which maps a desired outcome to customer opportunities, solutions, and experiments, story-based customer interviews, and assumption testing. The book is practical and example-driven. She also teaches courses based on the habits.
How do they compare?
| Dimension | Cagan | Torres |
|---|---|---|
| Level | The product organization and its leadership | The team's weekly practice |
| Core idea | Empowered teams, four risks, product discovery before delivery | Continuous discovery habits, the product trio |
| Main tools | Prototypes and tests for value, usability, feasibility, viability | Opportunity solution tree, interviews, assumption tests |
| Typical reader | Product leaders and executives | Product managers, designers, and engineers on a team |
| Source | Experience advising and working with product companies | Coaching practice and teaching |
| Main risk | Treating the model as a checklist without changing leadership | Habits running without authority to act on what is learned |
| Best known for | Inspired (2008, updated 2017), Empowered (2020) | Continuous Discovery Habits (2021) |
When does each one fit?
Cagan's work fits when the problem is structural: a team that is a feature factory, leadership that dictates solutions, or discovery treated as a phase before the real work. It gives a vocabulary for naming what is wrong.
Torres's work fits when a team already has some autonomy and wants a practical routine for staying close to customers. It gives specific habits that can start next week.
If the team has no authority to act on what it learns, habits will run into a wall. If the leadership is supportive but the team has no routine, Torres's habits fill the gap.
What does this look like in practice?
A team keeps shipping features requested by sales and finds that usage is flat. A Cagan reading says the team is implementing requests instead of solving problems for customers and the business. The fix involves leadership giving the team a goal, not a list, and the team testing value and viability before building.
A Torres reading asks what the team does each week. They set up weekly customer conversations, build an opportunity tree from what they hear, and test the riskiest assumptions with small experiments. The two readings reinforce each other: the first creates the permission, and the second creates the routine.
"Here is how my product team works today: [describe how work is chosen, who talks to customers, how decisions are made]. First, using Cagan's ideas, tell me whether it looks like an empowered team or a feature team, and which of the four risks it addresses before building. Then, using Torres's habits, suggest a weekly routine for a trio, including how many interviews, how to capture opportunities, and one small experiment to run this month."
Why it works: the first half checks the conditions and the second creates a routine that fits them.
Can you use both together?
Yes, and many teams effectively do. The model sets expectations for how teams should operate, and the habits make it concrete. A team following Torres's routine inside an organization that follows Cagan's principles has both permission and practice.
The usual failure is adopting the vocabulary of either without the behavior. Calling a feature backlog an opportunity tree changes nothing.
"A stakeholder has requested this feature: [describe]. For each of Cagan's four risks, tell me what we would need to learn before building, and what cheap test could address it. Then place the request on an opportunity solution tree: what customer opportunity does it serve, and what other solutions could address the same opportunity?"
Why it works: turning a request into risks and alternatives is the habit that separates discovery from order-taking.
Where to go next
Marty Cagan and Teresa Torres both sit in the Product Leader category. For the originals, read Inspired and Empowered by Cagan and Continuous Discovery Habits by Torres. Both authors' organizations sell training, so treat the books as one practitioner's view.
Frequently asked questions
Are Cagan and Torres competing approaches?
No. They address different layers of product discovery. Cagan's Inspired and Empowered describe how strong product organizations operate, including the roles, the risks to address, and the leadership they need. Torres's Continuous Discovery Habits describes the weekly practices a product trio can adopt. Many teams treat one as the model and the other as a practice, so they fit together. Reading both in sequence usually works best: the model first to understand the destination, then the habits to start the journey.
What are Cagan's four risks?
He describes four risks a product team must address before building: value, whether customers will buy or use it; usability, whether they can figure it out; feasibility, whether engineers can build it; and viability, whether it works for the business. The emphasis is on testing these risks quickly and cheaply in discovery instead of finding out after delivery. The four risks are meant to be addressed together, and a team that tests only value or only feasibility often meets the others late.
What is a product trio?
In Torres's work, a product trio is a product manager, a designer, and an engineer who do discovery together on a regular basis instead of handing work from one to the next. She argues that the trio should talk to customers weekly and share what they learn. The term is hers, though the idea of cross-functional teams is widely shared. She argues that doing it together reduces handoffs and shared understanding builds faster than reports can pass it on.
What is an opportunity solution tree?
It is a visual tool Torres describes in Continuous Discovery Habits (2021) that links a desired outcome to the customer opportunities, such as needs and pain points, that could achieve it, and then to candidate solutions and the experiments that test them. It helps a team see what it is choosing between and why. It also records the assumptions behind each solution, so the team can see which experiments matter most before building anything.
Do I need the whole product model to try continuous discovery?
Not necessarily. Torres's habits can be adopted by a single team, starting with a few customer interviews each week. Cagan argues that the habits will struggle without empowerment and good leadership around the team. Starting small and noticing what blocks you is a reasonable way to learn what your organization needs. If you can only change one thing, schedule a standing weekly slot for customer conversations and invite your designer and an engineer.
Can AI help with product discovery?
It can help draft interview guides, cluster notes into opportunities, and suggest assumptions to test. It cannot speak to customers for you, and summaries can flatten what people actually said. Use it to organize what your team has learned, and keep real conversations as the source. Always keep the original notes and quotes available, so the summary can be checked against what customers actually said.
Written by Gareth Hoyle. Last updated 8 October 2026. Part of the authority.md guides library.
More guides.
Daron Acemoglu vs Ha-Joon Chang: Do Good Institutions Cause Growth, or Follow It?
Comparing Daron Acemoglu's institutions-first account of national prosperity in Why Nations Fail with Ha-Joon Chang's historical critique of the institutions literature: two views of development, with the main point of disagreement. General education.
Bill Ackman vs Carl Icahn: Two Styles of Activist Investing. Not Investment Advice
Comparing Bill Ackman's public, thesis-driven activism with Carl Icahn's decades of corporate pressure campaigns: how each approaches companies, boards, and the public. Not investment advice.
Adam Smith vs Ha-Joon Chang: The Founder of Market Economics and One of Its Historical Critics
Comparing Adam Smith's Wealth of Nations and Theory of Moral Sentiments with Ha-Joon Chang's history-based critique in Kicking Away the Ladder: what Smith actually argued, what Chang adds, and where they differ. General education.