Skip to main content
TS

Theresa Schwartz

9episodes
1podcast

Featured On 1 Podcast

All Appearances

9 episodes
Product Talk

Staying Sane

Product Talk
28 min

AI Summary

→ WHAT IT COVERS Theresa Torres and Petra Mayer share personal strategies for maintaining mental stability during turbulent political times, covering media consumption habits, community engagement, platform responsibility, and how small, consistent acts aligned with personal values compound into meaningful resistance and psychological resilience. → KEY INSIGHTS - **Dual-source media consumption:** Reading two ideologically opposed outlets daily — one left-leaning, one right-leaning — reveals what each omits from the same story. Theresa reads the New York Times alongside the Wall Street Journal specifically to catch narrative gaps, reducing reactive thinking and building a more complete picture before forming opinions. - **Counter-polarization through nuance outlets:** The independent US publication Tangle covers one news story daily by presenting conservative perspectives, liberal perspectives, and then the editor's moderate synthesis — sometimes adding international viewpoints. This format directly combats oversimplification and helps readers locate where genuine complexity exists versus where outrage is manufactured. - **Values-aligned platform curation:** Declining speaking invitations where you are the sole woman on an all-male conference lineup, or refusing to fly cross-country for a single one-hour talk when virtual delivery is viable, are concrete ways to enforce personal values through professional decisions rather than just stated beliefs. - **Local community as the unit of change:** Advocacy rooted in neighborhood-level identity — framed as protecting neighbors rather than advancing national political positions — stays grounded in human connection. Attending a local protest rather than following national narratives shifts focus from abstract ideology to concrete relationships, which sustains motivation and avoids polarization traps. - **Continuous improvement over perfection:** Applying a discovery mindset — something is better than nothing — to personal ethics prevents paralysis. Rather than abandoning values because trade-offs exist (AI use, air travel, plastic), the practice is identifying one additional aligned action each day, treating ethical behavior as iterative rather than all-or-nothing. → NOTABLE MOMENT Theresa arrived at a local protest skeptical it would accomplish anything before the next election cycle. She left surprised by the scale of attendance and the unexpectedly celebratory atmosphere — participants wore costumes, carried flags, and projected optimism — which she had not anticipated given the severity of the circumstances. 💼 SPONSORS None detected 🏷️ Mental Resilience, Media Literacy, Political Polarization, Platform Responsibility, Community Advocacy

Product Talk

Kill Your Darlings

Product Talk
22 minCo-host/Guest

AI Summary

→ WHAT IT COVERS Teresa Torres and Petra Ville examine when to discontinue stable but stagnant products, using Teresa's decision to cut 40% of her revenue by sunsetting deep-dive courses and a $19/month Slack community, and introduce the McKinsey Horizon model as a portfolio management framework for product teams. → KEY INSIGHTS - **The Flatline Trap:** A product generating revenue but showing zero growth is more dangerous than a failing product, because it consumes team resources while masking the absence of true product-market fit. Teams mistake stability for success, preventing investment in higher-potential experiments. Sustained flatline growth is the signal to begin sunsetting conversations, not reassurance. - **McKinsey Horizon Model for Portfolio Decisions:** Structure your product portfolio into three buckets: H1 covers current revenue lines, H2 covers investments maturing within one to two years to replace H1, and H3 covers three-to-five-year bets. When sunsetting an H1 product, H2 experiments should already be ready to graduate, preventing revenue gaps and reactive decision-making. - **Sunsetting Column in Product Reviews:** Add a dedicated sunsetting column to your product portfolio board. Reviewing it regularly — Teresa does this annually — forces the explicit question of what is no longer growing. This structures the conversation before a crisis forces it, giving teams time to reallocate people and plan transitions rather than react under pressure. - **Portfolio Decisions Belong One Level Up:** The team managing a product is not the right group to decide whether it should be retired. Sunsetting is a portfolio-level decision requiring a broader view of resource allocation and strategic fit. Product leaders must own this conversation, removing the emotional conflict of interest that makes individual teams resistant to discontinuing their own work. - **Selective Customer Design via Pricing Structure:** Teresa eliminated monthly subscriptions entirely, moving to annual-only memberships at producttalk.org to filter out low-commitment users who asked surface-level questions without engaging with existing content. This deliberately limits growth but improves customer quality and alignment. Pricing structure can function as a customer selection mechanism, not just a revenue lever. → NOTABLE MOMENT Teresa revealed she cut 40% of her total revenue by discontinuing her deep-dive course line — a product that was profitable and had instructor dependencies. Her reasoning was that years of recurring operational problems and flat growth signaled the market had shifted, making space for new experiments the only viable path forward. 💼 SPONSORS None detected 🏷️ Product Market Fit, Portfolio Management, Product Sunsetting, Revenue Strategy, Team Topology

Product Talk

Lost in the Woods

Product Talk
23 minCo-host

AI Summary

→ WHAT IT COVERS Petra Villa and Theresa Schwartz use Robert Koester's book *Lost Person Behavior* — a study of how people navigate being physically lost in the woods — to examine five behavioral patterns that mirror how product teams and organizations lose direction and attempt recovery. → KEY INSIGHTS - **Staying Put (Escalate, Don't Wander):** Teams operating in IT-execution mode — told what to build with no discovery capability — should stop and escalate rather than improvise. Attempting self-directed fixes in that context risks greater damage. The correct move is raising the alarm to experienced leaders or an advisory board, not wandering further off-path. - **Shortcut Risk and Validation:** Pursuing a strategic shortcut, like Spotify shifting from low-margin music licensing toward podcasts, is only sound if tested before full commitment. Shortcuts reflect overconfidence when taken without validation. Engineering teams are an underused resource here — they frequently surface faster paths to outcomes that product managers never consider during discovery. - **Opportunity Mapping Over First-Path Bias:** Following the first visible path is a trap. Frameworks like opportunity solution trees and KPI trees exist specifically to surface multiple paths before committing to one. The discipline is making more options visible first, then selecting directionally — not defaulting to whatever solution appears earliest in the process. - **Intuition Requires Data Inputs, Not Replacement:** Product sense and taste are legitimate factors in decision-making, but applying them means exercising judgment across all available inputs — customer data, metrics, and observation — not ignoring instruments. Teams still operating on the product manager's opinion or sales requests alone are navigating without a compass. - **Retracing Steps to Restore Principles:** When bugs pile up or outcomes drift, the fix is not faster iteration — it is pausing to revisit the quality assurance rules or product principles that eroded. In continuous discovery, each forward habit creates a feedback loop on the previous one, signaling when to step back and correct the foundation before proceeding. → NOTABLE MOMENT Theresa pushes back on a trending industry argument that design process should be abandoned in favor of taste and intuition alone. She reframes taste not as a replacement for process but as the judgment applied to reconcile conflicting data points — the compass versus the setting sun. 💼 SPONSORS None detected 🏷️ Product Discovery, Team Alignment, Decision-Making Frameworks, Product Strategy, Organizational Behavior

AI Summary

→ WHAT IT COVERS Petra Villa and Theresa Schwartz examine where product manager responsibility ends and engineering ownership begins, focusing on bugs, tech debt, and architecture decisions that product managers commonly absorb but should not own. → KEY INSIGHTS - **Role Boundary Framework:** Engineers own the "how" — architecture, component sequencing, tech debt, and bug resolution. Product managers own the "what" alongside the product trio. When PMs absorb engineering decisions, code quality degrades and PMs burn out from defending work they lack expertise to explain. - **Bug Reporting Ownership:** PMs acting as middlemen relaying bug status between engineers and stakeholders is a structural failure. The fix is two-pronged: facilitate a direct channel (Slack, dashboard, or bug tracker) between engineers and stakeholders, then separately escalate systemic code quality concerns to engineering leadership. - **IT Mindset vs. Product Mindset:** Organizations without engineering leadership — only order-taking engineers — cannot build modern products. Functional product teams require engineering leaders who actively manage automated testing, CI/CD pipelines, code maintainability, and tech debt without waiting for PM direction or business tickets. - **Skills Gap Diagnosis:** When engineers cannot self-organize on zero-to-one builds or PMs are held accountable for bug status, the root cause is typically an IT-era engineering culture, not a product problem. The structural fix is hiring or developing engineering leadership, not expanding PM scope. → NOTABLE MOMENT Theresa points out that no other business function is held responsible for a separate function's quality of work — yet product managers routinely absorb accountability for engineering output, a dynamic she describes as structurally unique and damaging. 💼 SPONSORS None detected 🏷️ Product Management, Engineering Ownership, Tech Debt, Product-Engineering Collaboration

AI Summary

→ WHAT IT COVERS Product leaders Petra Villa and Theresa Schwartz examine support systems for CPOs and heads of product during periods of headcount reduction, AI disruption, and rapid organizational change, focusing on delegation strategies and scaling leadership impact effectively. → KEY INSIGHTS - **Executive Assistant Support:** CPOs rarely have executive assistants despite being C-suite peers with CEO and CFO who typically do have this support. Even three to six hours weekly of calendar management, email filtering, and boundary reinforcement helps leaders who struggle with saying no delegate effectively. - **Strategic Research Resources:** Product leaders conducting strategy initiatives should delegate market research, competitor analysis, and data analysis to dedicated researchers or data specialists rather than doing heavy lifting themselves. This applies to both internal product KPIs and external macro trend studies for 2026 planning cycles. - **Delegation Quality Standard:** The principle that 80 percent done by someone else equals 100 percent awesome helps leaders overcome perfectionism barriers. Leaders can still refine delegated work to 100 percent if needed, but avoid doing the initial 80 percent themselves, making delegation more palatable for those who feel responsible for quality. - **Communities of Practice:** Active product communities within organizations handle onboarding, candidate pre-qualification interviews, and role description drafting. Senior community members take these tasks off leadership plates, allowing CPOs to focus on unique value contributions rather than tactical execution that others can manage. → NOTABLE MOMENT Petra Villa observes that product leaders scale poorly because they operate as solo product people on development teams for so long that they never learn to request administrative help, maintaining an ingrained mindset of handling everything themselves despite reaching executive levels. 💼 SPONSORS None detected 🏷️ Product Leadership, Executive Delegation, Leadership Coaching, Product Strategy

Product Talk

Claude Code

Product Talk
45 minCo-host

AI Summary

→ WHAT IT COVERS Petra Wille shares her first four weeks using Claude Code for content creation, revealing setup challenges, workflow experiments, and debugging processes. Teresa Torres provides troubleshooting guidance on context management, model selection, and building custom tools for writing workflows, comparing Claude Code capabilities to browser-based Claude for newsletter production and research tasks. → KEY INSIGHTS - **Context File Architecture:** Claude Code requires layered instruction files including global ClaudeMD initialization files plus folder-specific briefings for tone, style, and project details. Setup takes approximately half a day to reach functional performance. Files cascade from global to local directories, making it easy to misconfigure which context Claude actually sees during specific tasks. - **Model and Mode Selection:** Switch models using slash model command to optimize speed and cost. Haiku model handles simple tasks like calendar review and task management significantly faster than default Sonnet. Disable thinking mode for routine work by checking the indicator under the prompt line, as most tasks don't require extended reasoning capabilities. - **Content Retrieval Excellence:** Claude Code excels at searching local files for past content, finding references across books, blog posts, and transcripts that authors forgot existed. This capability proves valuable for user interview analysis, customer service ticket review, and identifying when specific topics were previously discussed. Local file access eliminates document upload limitations present in browser versions. - **Web Fetch Debugging:** When Claude spirals during web searches, stop execution and ask directly what it's doing and why instructions seem confusing. Claude will identify conflicting information in system prompts or ClaudeMD files causing the confusion. This conversational debugging reveals which context elements need adjustment to improve task performance. - **Custom Tool Development:** Build reusable slash commands, sub-agents, and hooks for repetitive workflows like headline generation, SEO analysis with API integration, and fact-checking that validates claims against interview transcripts or research papers. Bundle related tools into plugins. This infrastructure enables rigorous work previously too time-consuming, like maintaining Zettelkasten note systems for literature reviews. → NOTABLE MOMENT Teresa reveals her writing output increased from 8,000 to 35,000 words monthly using Claude Code without quality degradation, receiving some of her best feedback during this period. She attributes this to building specialized tools for headline brainstorming, SEO optimization, and fact-checking that automate tedious aspects while she focuses on critical thinking and analysis. 💼 SPONSORS None detected 🏷️ Claude Code, AI Content Creation, Workflow Automation, Knowledge Management, Product Management

Product Talk

Build Vs. Buy

Product Talk
17 min

AI Summary

→ WHAT IT COVERS Petra Billet and Theresa Schwartz examine when product teams should build custom solutions versus buying existing tools, exploring how AI and vibe coding capabilities are shifting traditional decision frameworks around data ownership, vendor lock-in, and engineering complexity. → KEY INSIGHTS - **Core Value Rule:** Teams should buy tools that are not core to customer value delivery rather than spending product, engineering, and design resources on peripheral systems. The exception occurs when engineering teams lack the technical capabilities to maintain critical infrastructure, making purchase faster than hiring specialized talent. - **Data Ownership Priority:** AI capabilities elevate data portability as a primary decision factor when evaluating vendor solutions. Before selecting platforms like Salesforce or HubSpot, teams must verify complete data export capabilities including comments and attachments, or risk losing control of business-critical information that could limit future AI applications and strategic flexibility. - **Vendor Capability Assessment:** Choose vendors who excel beyond internal capabilities in specialized domains like payments, where Stripe dominates because no reasonable timeline allows matching their expertise. Evaluate whether competitors use the same vendor, creating competitive risk, and whether the vendor supports unique business requirements that justify avoiding custom development. - **Build Complexity Reality Check:** Engineering teams often overestimate their ability to replicate SaaS functionality due to hidden business logic complexity. Conduct technical spike tests to validate feasibility and user experience capabilities before committing to custom builds. Even simple-seeming tools like DocuSign contain years of accumulated features serving diverse customer segments. → NOTABLE MOMENT Theresa built her own task management system using Cloud Code and Obsidian in three days to maintain data ownership and integrate notes with tasks, while simultaneously rejecting the idea of building her own blog platform despite AI making both technically feasible. 💼 SPONSORS None detected 🏷️ Build vs Buy, Data Ownership, AI Development, Product Strategy

Product Talk

Product at Heart 2026

Product Talk
20 minHost

AI Summary

→ WHAT IT COVERS Petra Villa and Theresa Schwartz preview Product at Heart 2026 in Hamburg, Germany. They detail the ninth annual conference format changes, including a single-track program, AI integration across sessions rather than dedicated tracks, roundtable discussions, hands-on workshops, and a new extended product leadership retreat in April. → KEY INSIGHTS - **Single-Track Conference Curation:** Product at Heart 2026 runs a single-track format for 800 attendees due to venue renovations, requiring more careful speaker selection than previous dual-track events. This eliminates audience choice between parallel sessions, making content curation more challenging as organizers must predict relevant product management topics six months ahead in a rapidly evolving AI landscape. - **AI Integration Philosophy:** The conference avoids creating a separate AI track, instead embedding AI discussions throughout all sessions. This approach treats AI as a standard tool in the product toolkit rather than a specialty topic, reflecting the belief that AI capabilities should be integrated into every product manager's core competencies rather than siloed as an optional specialization. - **Roundtable Alternative Programming:** Theme-based roundtables accommodate 12-20 people and serve as alternative programming to main stage talks. Two formats run simultaneously: speaker-led Q&A sessions immediately following talks, and topic-based discussions hosted by product coaches and consultants. This addresses the missing second track and provides intimate learning opportunities for attendees seeking deeper engagement. - **Maker Studio Workshop Format:** Theresa Schwartz's full-day workshop requires pre-conference homework setting up Claude or Codex, then guides participants through identifying AI-augmentable work tasks, designing workflows using discovery habits and story mapping, and building a functional personal AI workflow deployable immediately after the conference. The hands-on hackathon approach delivers practical implementation skills rather than theoretical knowledge. - **Extended Leadership Retreat Model:** The product leadership event expands from half-day to one-and-a-half days in April, limited to 60 attendees. The format includes speaker sessions, Hamburg harbor excursions, improv workshops, networking dinners, and six ninety-minute mini-workshops offered twice so attendees can select two topics. This addresses the isolation product leaders experience as solo practitioners in their organizations. → NOTABLE MOMENT Petra describes meeting cyber psychologist Elaine Caskett at an airport after a conference in Morocco, leading to a two-hour conversation about digital afterlife research. Caskett's work examines how chatbots mimicking deceased people gradually dilute the original personality with each conversation, as the AI learns from new interactions and waters down the initial personality model. 💼 SPONSORS [{"name": "Netlight", "url": "not provided"}] 🏷️ Conference Planning, AI Integration, Product Leadership, Workshop Design, Community Building

Product Talk

Happy New Year!

Product Talk
23 minCo-host

AI Summary

→ WHAT IT COVERS Teresa Torres and Petra Wille share their 2026 business plans, including Torres transitioning from cohort-based courses to on-demand learning with AI tools, and Wille expanding her product leadership coaching program and assessment framework. → KEY INSIGHTS - **Course delivery transformation:** Torres eliminates live cohorts to create space for AI tool development, converting deep dive courses to on-demand format for consumers while launching a Discovery Habits Toolbox subscription for companies with leader coaching playbooks. - **AI teaching tools strategy:** Torres builds AI products like an interview coach and interview snapshot generator, navigating the tension between teaching synthesis skills versus providing automated solutions for time-constrained product teams still learning discovery habits. - **Leader coaching gap:** Discovery interviews revealed leaders want to coach teams on skills like interviewing and assumption testing but lack the expertise themselves, creating demand for curriculum paired with coaching playbooks rather than standalone training workshops. - **Academic research vetting:** Using Claude for literature reviews, Torres investigates synthetic user claims and finds vendor promises exceed academic validation, planning to publish research reports helping teams evaluate AI discovery tool purchases with realistic expectations. → NOTABLE MOMENT Torres reveals she cannot release some podcast episodes after interviews expose that teams claiming AI implementations actually have minimal or no AI functionality, highlighting widespread misrepresentation in the current market landscape. 💼 SPONSORS None detected 🏷️ AI Product Development, Product Discovery Training, Leadership Coaching, Course Business Models

Never miss Theresa Schwartz's insights

Subscribe to get AI-powered summaries of Theresa Schwartz's podcast appearances delivered to your inbox weekly.

Start Free Today

No credit card required • Free tier available