Context
Teresa Torres brings Petra Wille a blog post she is afraid to publish, titled "Does continuous discovery have product market fit?" She treats discovery as a product and the organizations that hire her for training as its customers. Then she runs that product through the four big risks she teaches product teams. For PMs, the episode is a rare case of a discovery advocate questioning whether discovery, as usually sold, fits how larger companies actually work.
The Big Idea
Continuous discovery works at the team level, but at the organizational level it may not fit. Boards, executive incentives and quarterly pressure may be constraints that will not change, so the practice itself may need to adapt.
Teresa is clear that she still believes in discovery. Her worry is that she and every other consultant she talks to keep seeing it fail to stick in larger organizations.
Key Insights
Four risks, taught per step
Teresa teaches the four risks by having teams story map what a customer must do to get value from a solution, then checking each step.
- Desirability: do customers want to take this step, and are they willing to? Teresa prefers "desirability" to Marty Cagan's term "value."
- Wanting and being willing are not the same. Login is her classic example: nobody desperately wants to log in.
- Usability: are customers able to take the step? Can they find it and understand it?
- Feasibility: is the step technically possible to build?
- Viability: will the step be good for the business?
Discovery passes viability, fails willingness
Applied to discovery as a product sold to organizations, Teresa sees no viability problem. Companies reach out to her every week asking for help, so they want discovery and will pay for it.
The risk sits in willingness. A PM might want to talk to customers every week, but will they protect the calendar time, keep doing it in busy weeks, and push through when the organization blocks customer access? Each habit carries that same gap between wanting and doing.
The organization is the customer
Teresa stresses that the problem is not product teams. She knows plenty of teams adopting the habits with real success.
The problem appears when the customer is a whole company. For continuous discovery to work there, the organization must be willing to change its own structures so teams can practice the habits. Teresa says she sees, over and over, that organizational context makes this extremely hard.
Pressure for certainty runs top-down
Teresa traces the obstacles through the company, stressing that she is describing a system, not blaming anyone.
- Board: public or not, it watches quarterly results and wants smooth up-and-to-the-right charts, not jagged improvement. That sets an expectation of predictability from the very top.
- Executives: they have deep industry and role experience, believe what got them here will get them there, and are paid through incentives from the board that reinforce this.
- The result: it is easy for an executive to feel 100% certain about a proposed solution. That is why the HiPPO (highest paid person's opinion) idea exists, with executives telling teams exactly what to build.
- Despite evidence that most of what teams build falls short of expectations, Teresa says this behavior is not changing.
Change rarely survives leadership turnover
Teresa says the only lasting adoption she has seen is when a CEO, or a product leader with strong influence on the CEO, stays at the company for a very long time. She does not see the change survive a leadership change.
The other exception is size. Teresa has seen it work in companies below Dunbar's number, which she put at about 120 employees. Petra agrees it can work well in small organizations. Teresa thinks it gets harder as a company grows, and says she is not convinced it is possible at scale.
Leaders dictate, trust breaks
Teresa describes what discovery adoption actually asks of a company, admitting it sounds more cynical than she is.
- Teams must learn a new, hard way of working, and the change takes a long time.
- People change at different rates, so for a long stretch some work the old way, some the new way, and some in between. That creates chaos.
- Leaders must stop dictating solutions. That is hard because they are held to outcomes, and dictating solutions is how they feel confident they will hit them.
- When leaders dictate, they break trust with teams, and teams stop wanting to do good discovery.
- That creates a vicious cycle of broken trust, lost habits and missing results, while leaders are still expected to deliver quarterly results throughout.
Team wins versus org fit
Petra pushes back. In an organization with 50 product teams, maybe half run SAFe (the Scaled Agile Framework), but the remaining teams can run pilots and adopt the habits. Once they work that way, those teams suffer less and finally see their numbers move. She asks whether improving 10% of an organization's teams is a good enough result.
Teresa does not question that impact. She hears daily from people whose habits, teams and careers changed after reading her book. Her point is that all of this is at the individual and team level, and she is asking a different question about the organizational level.
Mental Models & Frameworks
Willing versus wanting
A step can pass "do they want to" and still fail "are they willing to." Use this check on any behavior your product depends on, including internal practices like weekly customer interviews. Teresa's login example shows it: customers want the value behind a login, but nobody wants the login step itself.
Treat your practice as product
Teresa's whole argument comes from applying product thinking to the practice of discovery.
- Name the customer: here, the organization that buys training, not the individual team.
- Name the solution: the set of continuous discovery habits.
- Run the four risks against that solution, step by step.
- Take the constraints you find as given, the way you would with a real customer, instead of blaming the customer.
Constraints are requirements
Teresa notes that every consultant in the space complains that leaders buy training for their teams but not for themselves, and never remove organizational barriers. She suggests that may be the wrong way to look at it. If board governance, incentives and structure will not change, treat them as fixed requirements and ask whether the solution needs to change instead.
Trade-offs & Nuance
Empowerment is right but maybe infeasible
Teresa still fully believes product teams are closest to the customer and should be empowered. What she now questions is whether pushing decisions down to teams is feasible in a modern organization above a certain size. She is careful to frame this as a feasibility question, not a loss of faith in discovery.
Petra's view: exposure builds habits
Petra argues that adoption happens through trial. She has an old slide listing many experiments for reducing the four risks. Teams cannot try them all, but they try some, fall in love with a few after seeing the benefit, and those become habits.
- People from a design background tend to focus on usability risk.
- People from a business background tend to model the business case, covering viability.
- Coverage of all four risks stays patchy, and Petra thinks teams could cover them more evenly.
Teresa replies that this is a team-level answer to an organization-level problem.
Practical Application
Story map your riskiest steps
Before testing a solution, map every step a customer must take to get value from it. For each step, ask separately whether customers want it, are willing to do it, and are able to do it, then add feasibility and viability. This shows which step carries the real desirability or usability risk instead of judging the whole idea at once.
Find your company's discovery blockers
If you are introducing discovery habits, list the organizational forces that will push back, using the ones Teresa names.
- Does leadership expect smooth quarterly progress?
- Do executives tend to arrive with a fixed solution?
- Will adoption depend on one leader who may leave?
Plan around these as fixed constraints instead of hoping they disappear.
Protect trust when outcomes slip
If you lead product teams, notice the moment you feel pressure to dictate a solution to hit a target. Teresa's warning is that dictating breaks trust, and teams that lose trust stop doing good discovery. Be explicit with the team when you do step in, and why, so a one-time override does not erase the habit.
Questions to Consider
- If you treated your team's way of working as a product, would your own organization pass the willingness test, or only want it in theory?
- Which board or executive expectations in your company, such as smooth quarterly growth, are making continuous discovery harder to sustain?
- Would your team's discovery habits survive if your current CEO or head of product left tomorrow?
- If your company will not change its incentives, what way of bringing customer feedback into decisions could still fit inside those incentives?
Bottom Line
Continuous discovery clearly helps the teams that adopt it, but Teresa doubts it fits larger organizations as currently sold. Her open question is how discovery advocates can evolve their approach so customer feedback loops work within boards, executive certainty and quarterly pressure, rather than waiting for those to change.
Resources Mentioned
| Resource | Type | Why it was mentioned |
|---|---|---|
| "Does continuous discovery have product market fit?" | Blog post (unpublished) | Teresa's draft post, which the whole episode discusses. Petra encourages her to publish it as an open question. |
| Organizational Change is Exhausting | Podcast episode | An earlier All Things Product episode Teresa points to as background on why organizational context is so hard. |
| Continuous Discovery Habits | Book | Teresa's book, which she says people credit for changing their individual habits, their teams and their careers. |
| Petra's experiments slide | Slide | An old slide of many experiments for reducing the four risks, which Petra may share in the show notes. |
Concepts to Explore
Dunbar's number
The idea that people can maintain only a limited number of stable relationships. Teresa uses it as a rough company size, which she put at about 120 employees, below which she has seen discovery adoption last.
HiPPO
Short for "highest paid person's opinion," the pattern of an executive deciding what gets built based on their own certainty. Teresa cites it as evidence that executive-dictated solutions have been common for decades.
Notable Quotes
"I wholeheartedly still believe in continuous discovery." (Teresa Torres)
"Maybe the problem is not the organization." (Teresa Torres)
"So we have this vicious cycle of breaking trust, destroying habits, not getting results." (Teresa Torres)
"Once you work that way, what has been seen cannot be unseen basically." (Petra Wille)
