Product Thinking

The episode contains a few genuinely useful framings—particularly Teresa's 'never stop' principle and the Covid agility example—but as a 15-minute compilation of clip highlights, it sacrifices density for breadth, and the Granola ad and host narration bridges consume significant airtime that could hold substance.

“if you find yourself stopping to do something, you're already doing it wrong”

“the only thing that changed in a Covid world for you was you started working from home...You just said, you know what, this new opportunity is coming in. That seems a lot more important. Let's do that next”

The opportunity-solution tree and continuous weekly cadence are well-established in PM circles (Teresa's book is a primary source, so it's canonical rather than fresh), and 'go slow to move fast' is a recycled aphorism; Christina's self-to-stranger testing scaffold is the episode's most distinctive structural contribution.

“first you test with yourself...Then you test with other designers...And then you start moving out to friends and family...and then eventually you move to stranger testing”

“we start with an outcome...Then we have to discover the opportunities...And then we need to discover the solutions”

All three guests have real practitioner or practitioner-turned-educator credentials—Teresa Torres is the primary author on the topic, Christina Wotke has hands-on Zynga product experience, and Julia Austin taught at HBS—but the compilation format means we get curated highlights rather than full depth from any of them.

“I got that from Zynga where we would always have user research every single week. I don't know if all game studios do it at that pace, but that pace was mind blowing”

“Teresa Torres, author of Continuous Discovery Habits”

The episode offers a handful of concrete specifics—Zynga's weekly cadence, the sticky-note workaround anecdote, the B2B buyer-vs-user distinction—but lacks named metrics, outcomes, timelines, or dollar figures, and most advice stays at the level of principle rather than proof.

“there's a user and there's a buyer and our user, it lands for them beautifully. But they're not the ones that are going to swipe your credit card to buy this thing”

“it was like opening a drawer and looking at a sticky note because there was some code they needed to do a thing, but they never bothered to tell us that”

The host questions are mostly generic setup prompts ('can you tell us about the framework,' 'what does it mean to go slow to move fast') with no real pushback or probing follow-ups; the compilation format structurally prevents the conversational tension that produces the best insights.

“So can you tell us a little bit about what is the framework for continuous discovery habits? How would you describe it? Why should people do it?”

“What do you think game design does as well too to make sure that you remember the user value”