This CPO regrets that product management exists | Tom Verrilli (CPO of Whatnot)

Episode Overview

• Rethinking the Role of Product Management: This episode challenges the traditional tech industry assumption that every engineering team requires a dedicated product manager (PM), arguing instead that over-specialization and bloated product structures often isolate builders from customers and slow down execution.
• The Transition from "Product Theater" to High-Impact Execution: The discussion exposes "product theater"—where PMs are rewarded for alignment meetings, storytelling, and complex frameworks rather than shipping successful products—and advocates for highly skilled, hands-on individual contributors (ICs).
• The "Accordion" of Product Development: Listeners learn a vital mental model for product design, balancing a long-term strategic vision (zooming out) with rapid, tactical execution (zooming in), while avoiding the paralysis of overthinking downstream consequences.
• Navigating the Future of E-Commerce and Community: Using examples from Whatnot and Twitter, the episode explores why human curation, trust, and physical-world social dynamics remain invincible to AI disruption, and why true product-market fit can survive massive organizational dysfunction.

Key Concepts

• The Origins of Product Management and the "Pod" Trap: Historically, early internet startups succeeded via direct communication between founders, engineers, and designers. As companies scaled, they standardized organizational ratios into product "pods" (e.g., one PM and one designer for every six engineers). While useful for rapid expansion, this structure often leads to an overabundance of PMs in technical or infrastructure domains where engineers are fully capable of making roadmap decisions.
• Product Management as a "Trade" vs. "Product Theater": Product management is an experiential trade developed through hands-on repetition, resolving ambiguity, and driving clarity. In contrast, many large, matrixed organizations reward "product theater"—focusing on internal politics, stakeholder alignment, and polished presentations rather than a deep understanding of technology, data, and customer needs.
• The Risk of Engineering and Design Infantilization: Automatically assigning PMs to "babysit" teams and handle all stakeholder alignment isolates engineers and designers from direct user and business context. This prevents builders from developing their own decision-making muscles and commercial instincts.
• The "IC" (Individual Contributor) Executive: This model represents a shift away from traditional middle-management layers toward highly paid, deeply experienced product leaders who spend up to 90% of their time doing direct execution (e.g., writing specs, pulling data, and querying codebases) rather than coaching or coordinating.
• The "Verify and Trust" Management Style: Rather than blindly "hiring great people and getting out of their way," effective product leadership requires diving into support tickets, raw data, and code to verify the "ground truth" before making strategic macro decisions.
• "Playing the Accordion" in Product Development: A critical product cadence where PMs must stretch the accordion out (zooming out to define a long-term strategic vision and systemic impacts) and then press it all the way back in (zooming in to build, launch, and iterate on a highly tactical V1). Over-indexing on either strategic roadmapping or blind, directionless iteration leads to product failure.
• High-Intent vs. Low-Intent Commerce: AI-driven agents will easily dominate high-intent, transactional tasks (e.g., finding and purchasing the cheapest utility item). However, the majority of retail is low-intent, experiential, and social. Platforms that simulate physical-world mall browsing, live human curation, and community interaction remain highly resilient to AI disruption.
• The Danger of Relying on Averages: High-level dashboard metrics can mask critical user behaviors. A feature with a mere 3% average adoption might be the core, irreplaceable workflow for a highly dedicated cohort of power users whose departure could trigger a negative platform network spiral.

Quotes

• At 0:00:23 - "Since its earliest inception, the Whatnot product team has been built on a somewhat simple premise: we regret that product management exists." - Explaining the foundational philosophy at Whatnot that challenges the default necessity of the PM role.
• At 0:00:30 - "We articulated it that way to force ourselves to remember that you don't hire a PM just for the sake of hiring one. You hire one where there is a really specific need." - Detailing how this contrarian stance serves as an internal safeguard against organizational bloat.
• At 0:00:39 - "The only argument for why you would want product management to be a specialist function is really... it's a trade, not a qualification. It's something you get good at by doing. It's a muscle." - Defining PM skills as practical and experiential rather than theoretical.
• At 0:00:49 - "The flip side of that is the more you abstract your engineers and your designers from doing the same thing, their muscle gets underdeveloped." - Highlighting how intermediary managers can weaken the product instincts of actual builders.
• At 0:01:06 - "I can tell you what's definitely trending down: folks who spend a lot of their time in their interviews talking about driving alignment and stakeholder management... because there's definitely a group of PMs whose specialty wasn't technical; it was politics." - Noting the industry shift away from professional meeting-coordinators toward execution-focused builders.
• At 0:01:23 - "If you were really successful as a PM, you got promoted into being a director, where we took all of our A-players and then promoted them out of doing things." - Critiquing corporate ladders that pull top talent away from hands-on product craft and into management.
• At 0:23:04 - "On our team, there are managers... but all of them spend 90% plus of their time doing IC work. I'm still probably 50% of my time doing IC work personally." - Highlighting the organizational structure shift away from heavy middle-management toward execution.
• At 0:24:28 - "If you're thinking about how we manage sellers who ship slowly, and you know about the power of discovery, you can in either case make the correct decision... we cut out months and months of back-and-forth and the politics that tend to take it from company-first to career-first." - Explaining how having senior leaders in the weeds prevents cross-team friction and speeds up decision-making.
• At 0:26:49 - "I think it starts with: Are you literally in the support tickets? Do you know what customer problems we're having? Have you pulled all of the data yourself so that you actually understand it? Have you sat with engineering and design? ...All of that is just core individual IC work." - Defining what "IC work" actually means for a high-performing product leader.
• At 0:29:03 - "Go and take the comp required to have five L5s reporting to one L7, and four L7s reporting to one VP, and total the comp of that product org... What if I had three people? Why can't I pay them all VP money, particularly if they're having that level of impact?" - Illustrating the financial efficiency and talent density benefits of a flat, highly-skilled product organization.
• At 0:31:06 - "Just that attitude that says we're going to do fewer things, execute the hell out of them, and push our best people to be in the weeds everywhere means you fix lots of things as you go and don't end up making loads of tradeoffs." - Advocating for extreme focus and execution quality over trying to do too many things at once.
• At 0:37:28 - "I think those core PM skills aren't necessarily the things we have rewarded PMs for over the last five years, versus storytelling, alignment, and strategy... can I genuinely understand the customer, the business, and the tech, and translate the three together?" - Contrasting "theatrical" PM skills with the actual functional skills required to ship successful products.
• At 0:41:47 - "Reviews got very into 'listen for yes' where all you're trying to do as a PM is just get a green light so you can go back to your engineers and say 'I have some credibility'... as opposed to this idea that says we're just trying to find the right answer." - Exposing the toxic alignment loops of traditional product reviews and advocating for truth-seeking over permission-seeking.
• At 0:52:38 - "The point of the analogy of 'play the accordion' is... before you can play a note, you've got to stretch it all the way out, bring the air in [and ask] 'what is it we are trying to get done here?' But you don't make music until you press the key and push it all the way back in to V1. You've got to get used to this motion that says constantly: zoom out, and push back in." - Explaining the critical cognitive rhythm of successful product creation.
• At 0:54:47 - "If you truly find product-market fit, if you manage to bottle lightning, it doesn't matter how badly you screw up the organization of it... Twitter genuinely had that level of product-market fit where you could emotionally feel how much people loved the product." - Illustrating the immense defensive moat of genuine product-market fit, drawing from Tom's experience at Twitter.
• At 0:55:20 - "Most of the time you hear 'it's really complex,' it isn't. Leadership is just weak." - Highlighting how organizational paralysis is often just a failure of leadership to make hard, decisive product trade-offs.
• At 0:56:13 - "Averages mean nothing to the individual... In any sizable population, it's really attractive to go and look at average utility or average adoption... but if you don't go a layer deeper, [you miss that] there's a group of people for whom it's 100% of what they do. This is their core use case." - Warning against using aggregate dashboard metrics to justify product deprecation.
• At 0:58:20 - "The best book anyone's ever recommended to me to read... is 'The Purpose Driven Church' by Rick Warren... It's this wild examination of why people emotionally invest in something and how to engineer emotional investment into it from a group of people." - Detailing how building highly engaged user communities mirrors the sociological principles of building a congregation.

Takeaways

• Eliminate Unnecessary Coordination Layers: Stop promoting top product builders out of IC roles and into pure coordination, coaching, or "alignment" positions that slow down development.
• Transition from "Trust" to "Verify and Trust": Require product leaders to personally review support tickets, query databases, and read code to find the "ground truth" rather than managing via high-level summaries.
• Implement Hands-On Hiring Case Studies: Combat "product theater" by having candidates solve real problems using actual company data, then requiring them to verbally defend their decisions in the interview.
• Avoid the "Average Metric" Trap: Analyze user cohorts deeply before deprecating low-adoption features, ensuring you do not alienate high-value power users for whom that feature is a primary workflow.
• Consistently Play the Accordion: Establish a regular rhythm where the team zooms out to clarify long-term strategic impacts, then rapidly zooms in to build and ship a simplified V1.
• Democratize Context Over Coordination: Empower engineers and designers with direct access to user feedback and business performance metrics so they can make high-quality product decisions without a PM intermediary.
• Look Outside Tech for Community-Building Strategies: Read sociological and theological texts (such as The Purpose Driven Church) to understand the psychological principles of shared belief, belonging, and organic user engagement.
• Prioritize Decisive Trade-Offs Over Perfection: Avoid endless design sprints and alignment loops. Realize that the business cost of inaction is almost always higher than the cost of shipping a slightly imperfect launch.