More All Things Product episodes

Discovery & The 4 Risks thumbnail

Discovery & The 4 Risks

Published 10 Nov 2026

Duration: 00:19:17

Teresa Torres questions whether continuous discovery has product-market fit for large organizations due to systemic obstacles.

Episode Description

In one of their most philosophical episodes yet, Petra Wille and Teresa Torres turn product thinking on the discovery practice itself. If you treat th...

Overview

The discussion centers on whether continuous discovery practices have product-market fit when treated as a product sold to organizations. Teresa Kors frames the question using the four risks - desirability, usability, feasibility, and viability - and argues that while organizations clearly want discovery, the organizational context creates significant barriers to sustained adoption. She identifies that boards expect predictable quarterly results and executives tend to dictate solutions, producing a trust-breaking cycle that undermines team-level discovery habits.

Teresa clarifies she is not questioning the value of discovery or the four risks themselves. She acknowledges that individual teams and small organizations can successfully adopt these practices, but her concern is specifically at the organizational level in larger companies, where she says she is "not convinced it's possible" to sustain the change. She proposes that the industry may need to find alternative ways to bring customer centricity and feedback loops into organizations that fit within existing incentive structures and governance constraints, rather than requiring a fundamental shift in how organizations operate.

What If

  • What if you treated your own product's discovery process as a fixed habit loop rather than a one-time research sprint?

    • Move: Schedule a recurring 30-minute customer conversation every week for 12 weeks and treat it as non-negotiable calendar time, even during busy shipping periods.
    • Why Now? The source identifies willingness to "reserve the time on my calendar" and do it "in the weeks when things get busy" as the core desirability risk. As a solo operator, you control your own calendar and can remove the organizational friction the source describes.
    • Expected Upside (proposed): You may find that consistent, small discovery interactions build a compounding habit, mirroring the source's observation that people "fall in love with some of them and then they're willing to do those because they saw the benefit of them."
  • What if you designed your onboarding to explicitly test all four risks at each user step?

    • Move: Map your user's journey step-by-step (the source's "story map" approach) and for each step write one question per risk: Do they want to take this step? Can they find it? Is it technically possible? Does it serve the business?
    • Why Now? The source stresses that "do they want to and are they willing to?" and "are they able to?" are distinct, and "sometimes those aren't the same, right?" Testing both separately prevents conflating motivation with capability.
    • Expected Upside (proposed): You may isolate a specific step where willingness drops but ability is fine, or vice versa, giving you a concrete fix rather than a vague usability complaint.
  • What if you built your product to work within a skeptical executive's constraints rather than requiring organizational change?

    • Move: Design your product so a single decision-maker can adopt it as a pilot without altering team processes, reporting structures, or quarterly reporting - essentially a low-friction entry point that proves value before asking for broader adoption.
    • Why Now? The source argues that "the organizational incentives and governance and structure is not going to change" and that pushing decision-making to product teams is "limited in the impact that we can have" in larger organizations.
    • Expected Upside (proposed): You may demonstrate results incrementally, leveraging the source's point that "once you work that way, what has been seen cannot be unseen," and earn trust without requiring a top-down mandate.

Takeaway

  • Map your product's user journey step-by-step and test each step against all four risks (desirability, usability, feasibility, viability) before building the next feature, using the source's "story map" method of asking what the customer must do at each step.
  • Schedule a fixed, recurring customer conversation slot and protect it even during busy shipping weeks, since the source identifies willingness to "reserve the time on my calendar" as the primary desirability risk for discovery habits.
  • Distinguish "do they want to" from "are they able to" at each user step and test both separately, because the source notes these "sometimes... aren't the same, right?" and conflating them hides the real blocker.
  • Design your product or service so a single decision-maker can adopt it as a pilot without requiring organizational restructuring, since the source argues that above a certain size, organizational change is "not... possible" and you should work within existing constraints.
  • Expose your users or team to several small discovery experiments rather than one comprehensive framework, since the source observes that people need to "try some of them" and "fall in love with some of them" before those practices become lasting habits.

Recent Episodes of All Things Product

17 Nov 2026 The Sharing Gap

Product leaders are encouraged to share their real experiences and specific examples on social media to foster genuine learning and community growth.

3 Nov 2026 What AI Changes

AI exposes existing organizational flaws rather than replacing essential processes like testing, planning, and customer discovery, while SaaS failures stem from poor strategy and excessive valuation rather than AI competition.

27 Oct 2026 Defining What Good Looks Like

"Explores AI product development challenges, emphasizing measurable outcomes, customer-centric evaluation, cross-functional collaboration, and real-world impact over technical metrics."

13 Oct 2026 Training Expectations

"Continuous product discovery training requires habit-building and practice, not just short sessions, as teams often underestimate the depth of skill development needed for mastery."

6 Oct 2026 Recorded Conversations

"AI and technology's role in recording conversations raises ethical, psychological, and social challenges, including trust, evolving opinions, memory inaccuracies, and the impact of transcripts on relationships and accountability."

More All Things Product episodes