Leadership Styles of Legends

Most product teams do discovery in batches. They run a research sprint, synthesize findings, hand off a report, and move on. Teresa Torres spent years coaching product teams and found that this model almost never works — not because the research is bad, but because the gap between discovery and decision is too wide.

Her continuous discovery framework collapses that gap.

The opportunity solution tree isn't a methodology novelty. It's a structural answer to a specific failure mode: product teams that ship things without being able to articulate the customer problem they're solving. Torres spent a decade building Product Talk as a coaching and writing platform, working directly with PM teams at B2B SaaS companies where product-market fit was established but product process was still immature.

If your PMs are closer to project managers than problem solvers, Torres's work is the clearest practical path between where you are and where Marty Cagan says you should be. She's the person who operationalizes what Cagan describes.

Leadership Style Breakdown

Style	Weight	How it showed up
Systems-Thinking Coach	60%	Torres's primary contribution is architectural. The opportunity solution tree is a visual system that forces product teams to slow down and map the relationship between a desired outcome, the customer opportunities that serve it, the solutions that address those opportunities, and the assumptions that need testing before committing. That's a workflow redesign, not a research method. Torres spent years working with real teams — not hypothetical ones — to understand why the gap between discovery and decision persists, and she built the framework to close that specific gap rather than to describe an ideal state.
Practitioner Researcher	40%	Torres comes from product operations and UX backgrounds, not academic research. Her authority isn't from a PhD or a famous company. It's from coaching hundreds of product teams through the Product Talk platform, running coaching cohorts, and publishing work at producttalk.org that PMs have been reading and applying for over a decade. That practice-based credibility means her frameworks carry the marks of real-world failure modes — she's seen what breaks, where teams get stuck, and where the theory doesn't survive contact with an annual planning cycle.

The split explains Torres's position in the product canon. Cagan provides the organizational architecture. Torres provides the weekly practice. Her coaching cohorts and the structure of "Continuous Discovery Habits" are designed for teams that have accepted Cagan's diagnosis and need the specific behavioral system to do something about it. She's the implementation layer for empowered product teams.

Key Leadership Traits

Trait	Rating	What it means in practice
Rigorous commitment to outcome over output	Exceptional	Torres doesn't use "outcome over output" as a slogan. She uses it as a structural constraint on how discovery is organized. Every branch of the opportunity solution tree starts with a desired outcome — a specific, measurable change in customer behavior that would indicate the product is working. If the team can't articulate the desired outcome clearly, the tree doesn't branch. That sounds simple. In practice, it forces product teams to confront how rarely they're starting from a clear outcome versus starting from a solution that was handed to them.
Patience with the messiness of real-world product work	Very High	Torres's coaching work is notable for not assuming clean conditions. Her frameworks acknowledge that most product teams are operating under annual planning constraints, with insufficient research capacity, and with executives who want solution commitments before discovery is done. Adam Grant's research on organizational psychology provides a complementary evidence base for why that messiness persists — specifically his work on how teams default to confirmation behavior under planning pressure. "Continuous Discovery Habits" doesn't describe product work at a tier-1 tech company. It describes product work at the kind of mid-stage SaaS company where one PM covers three product areas and research is a part-time role. That grounding makes her work more applicable than frameworks designed for Google's conditions.
Ability to make abstract product theory concrete	High	Torres's contribution to product thinking is largely about translation. The idea that product teams should talk to customers regularly is not new. But "talk to customers" as advice produces widely varying results. Torres's specification — at least one customer interview per week, conducted by the product trio (PM plus designer plus engineer), as a non-negotiable habit — turns a principle into a practice. That specificity is underrated. Most product principles fail not because they're wrong but because they're not concrete enough to change behavior.
Practitioner credibility earned through coaching hundreds of teams	High	Torres has coached product trios and product leadership teams across hundreds of B2B SaaS companies through Product Talk's coaching cohorts and online courses. That breadth of direct coaching experience — not just writing about frameworks but watching teams apply them in real environments — is where her most useful insights come from. She knows where the opportunity solution tree breaks down in companies with quarterly planning cycles. She knows what happens when the product trio tries to run weekly interviews without executive air cover. Her frameworks are calibrated to those conditions.

The 3 Decisions That Defined Teresa Torres as a Leader

1. Choosing to Build Product Talk as a Practice-Focused Platform

Torres built Product Talk — producttalk.org — as a coaching and writing platform rather than a consulting firm or a SaaS product. That distinction matters more than it might appear.

A consulting firm scales by adding consultants and selling engagements. A SaaS product scales by building software. A practice-focused platform scales by building an audience of practitioners who trust your thinking, and then offering structured learning experiences to that audience.

The Product Talk model built over a decade through blog posts, coaching cohorts, and online courses. The audience grew gradually, through consistent publication of specific, useful thinking rather than through marketing. By the time "Continuous Discovery Habits" was published in 2021, Torres had 10,000-plus PMs and product leaders who had read her writing regularly for years.

What the platform model enables is depth with a specific audience. Torres's readers are working PMs trying to improve their practice, not executives looking for a strategic framework. That audience shaped what she built: not a thought leadership brand, but a practitioner community. The coaching cohorts are structured around actual team practice, not certification. The blog posts are about specific problems — how to run a customer interview when your company doesn't support it, how to build an opportunity solution tree when you don't have a clear outcome to start with.

What the model constrains is scale. Torres can't coach ten thousand companies at once. The platform reaches more people through writing and courses, but deep coaching is limited by time. That's a deliberate tradeoff: depth over reach.

2. Developing the Opportunity Solution Tree

The opportunity solution tree is the central artifact in Torres's framework. It's a visual tree structure that organizes product discovery from desired outcome down through the opportunity space, into the solution space, and then into assumption testing.

The structure is: desired outcome at the top, then a branching set of customer opportunities (needs, pain points, desires that if addressed would contribute to the outcome), then proposed solutions that address specific opportunities, then the assumptions each solution rests on, and finally the experiments that test the most critical assumptions. The Jobs-to-be-Done framework is the theoretical precursor here — Torres's opportunity framing draws directly on the idea that customers hire products to do a job, and her tree structure makes that job explicit at every branch.

That sounds like a lot of steps. But it's actually solving a single failure mode: teams jumping to solutions before mapping the problem space. Most product teams start with a solution — either because it came from a customer request, a sales commitment, or an executive idea — and work backward to justify it. The opportunity solution tree makes that shortcut visible by requiring the team to place their proposed solution on a branch of the tree that connects back to a specific customer opportunity and a desired outcome.

If the solution doesn't connect to an opportunity, it doesn't belong on the tree. That's the structural constraint. In practice, it often reveals that teams are building solutions to problems nobody has diagnosed.

Torres was deliberate about making the framework visual. She found in coaching that teams could agree with the logic of outcome-driven discovery in the abstract and then immediately revert to solution-first thinking in the next planning meeting. A physical or digital artifact that the team could point to — a tree on a whiteboard or a Miro board — created a shared accountability structure that verbal agreement alone didn't provide. Shreyas Doshi's anti-goals practice reinforces the same structural logic from a different angle: both tools exist to force explicit decisions that planning optimism normally hides.

3. Writing "Continuous Discovery Habits" as a Practitioner's Manual

Torres published "Continuous Discovery Habits" in 2021 through Product Talk Press. The choice to self-publish through her own platform rather than through a traditional business publisher was itself a signal about who the book was for: practicing PMs, not business executives looking for a leadership framework.

The book is structured around a single non-negotiable habit: the product trio should interview at least one customer per week, every week, without exception. Torres's argument is that discovery fails when it's treated as a project — a research phase with a beginning and an end. Continuous discovery treats customer contact as infrastructure, like sprints or stand-ups. It's the minimum viable practice that everything else depends on.

Around that central habit, the book builds the full opportunity solution tree methodology: how to define a desired outcome, how to interview for opportunities rather than solutions, how to build and maintain the tree, how to generate solutions collaboratively, and how to identify and test the assumptions that most put the solution at risk.

The specific framing around "habits" rather than "process" or "methodology" was deliberate. Torres was drawing on behavioral science research (she cites James Clear's work) to argue that the way to install continuous discovery isn't through a process rollout. It's through habit formation at the individual and team level. That framing influenced how the book was structured — each chapter describes a specific habit, not a process step.

The result is a book that reads differently from most product management writing. It's less about describing the ideal state and more about what you do on Monday.

What Teresa Torres Would Do in Your Role

If you're a CEO, Torres's most important message for you is about what "customer-driven" actually requires structurally. Most companies believe they're customer-driven because they do NPS surveys or run quarterly customer advisory boards. Torres's argument is that those mechanisms put too much distance between the team building the product and the customers they're building for. Customer advisory boards tell you what customers say they want in a prepared setting. Weekly interviews by the product trio tell you what customers actually struggle with in their work. The first produces validation for existing plans. The second produces discoveries that change plans. If you want the second, you need to build the structural conditions for it.

If you're a COO, the operational question Torres surfaces is about how your product team's discovery work connects to your delivery commitments. Most companies plan delivery 6-12 months out, which means the assumptions built into that plan were formed months before delivery. Torres's continuous discovery model builds in weekly mechanisms to update those assumptions. That creates a tension with annual planning cycles. The operational resolution isn't to abandon planning — it's to build a lighter-weight mechanism for assumption tracking between planning cycles, so that the delivery plan can be updated when discovery reveals that a core assumption is wrong.

If you're a product leader, the most important Torres practice to install is the weekly customer interview cadence for your product trios. Not research sprints. Not user testing events. Weekly interviews, conducted by PM plus designer plus engineer together, as a recurring calendar item that doesn't get cancelled when sprint planning runs long. Torres is specific about the engineer presence because she found that engineers who participate in customer interviews make better implementation decisions without needing a requirement document to spell out every detail. The interview itself is the communication layer.

If you're in sales or marketing, Torres's opportunity solution tree gives you a diagnostic tool for understanding why customer feedback doesn't translate into product changes. When a sales team brings customer requests to the product team and those requests sit on the backlog, it's often because the request is framed as a solution (we need feature X) rather than an opportunity (customers struggle to do Y). Torres's framework can help you translate customer input from sales into opportunity language that the product team can actually use. That's not a political fix. It's a vocabulary shift that changes what happens to the input.

Notable Quotes and Lessons Beyond the Boardroom

"At a minimum, weekly touchpoints with customers by the team building the product." That's Torres's definition of continuous discovery, and the specificity is the point. Not monthly. Not quarterly. Not by the research team on behalf of the product team. Weekly, by the trio. That cadence is what makes the difference between discovery as a project and discovery as a practice.

Her argument against customer advisory boards as a substitute for direct contact is worth sitting with. HBR's research on customer-centric product development arrives at a compatible conclusion from the academic side: structured discovery rituals that keep teams close to customer struggles consistently outperform periodic advisory input. Advisory boards produce curated, consensus input from customers who have been selected for their willingness to engage. They're useful for certain kinds of strategic input. But they're not a substitute for direct, unmediated contact with customers who are trying to solve problems in real time. The advisory board customer describes what they want. The customer in a weekly interview shows you what they're struggling with.

Torres's framing of "assumptions" as the most under-examined variable in product decisions is her most intellectually precise contribution. Every product bet is a stack of assumptions — about what the customer wants, about whether the solution will work, about whether the team can build it, about whether it'll be adopted. Most teams don't enumerate those assumptions explicitly, which means they can't test the most critical ones. The opportunity solution tree's assumption-testing branch exists specifically to surface the assumption that, if wrong, would invalidate everything else.

Where This Style Breaks

Continuous discovery requires product teams with enough autonomy to act on what they learn. In companies where engineering resources are dictated by annual planning cycles or where product decisions require executive sign-off at the feature level, Torres's weekly cadence creates frustration rather than momentum. The habit of weekly interviews doesn't solve the problem if what you discover can't change what you build.

The opportunity solution tree is also a tool for experienced product thinkers. Teams early in their product maturity — PMs who are still learning how to run a customer interview, engineers who've never been in a customer conversation — often need more scaffolding than the framework provides on its own.

And Torres's work is most battle-tested in mid-stage B2B SaaS. Enterprise software with complex procurement cycles, hardware products, and consumer apps with millions of users present discovery challenges that her framework addresses at a high level but doesn't operationalize as specifically. Linus Torvalds represents the sharpest contrast in engineering culture: where Torres argues for continuous engineer involvement in customer discovery, Torvalds built the most influential engineering contribution of the last 30 years by keeping engineers as far from external requirement pressure as possible.

For related reading on product discovery and empowered teams, see Marty Cagan Leadership Style, Shreyas Doshi Leadership Style, and Building Outcome-Driven Product Teams.

Victor Hoang

Co-Founder & CMO, Rework