Lenny's Podcast

Tom delivers concrete, non-obvious claims throughout: the ratio-driven hiring of PMs infantilizes engineers, the accordion mental model (zoom out/zoom in iteratively), averages hiding individual use cases, and top-down leadership being effective when grounded in truth. However, some sections drift into expected PM wisdom (systems thinking, first-principles analysis), and there's occasional throat-clearing. The density is high but not exceptional - most insights are well-articulated rather than truly surprising.

“As tech companies scaled somewhere along the line, this HR ratio of a pod popped into being. Every time you hire six engineers, you add a designer, you add a PM... hiring so many PMs infantilizes the engineers and the designers who are perfectly capable of making good decisions, but just never had to because there was always a pm, um, to babysit them.”

“I think I fail more often than I succeed across the course of my career. Genuinely, uh, to the blog you referenced right at the start, I published... it starts with, like, batting 500 is like, the goal. So, like, you're hoping to be right as often as you're wrong.”

Tom's core thesis - regretting PM existence to force intentionality - is provocative and relatively fresh, as is his reframing of IC work for senior PMs and the 'accordion' mental model for product development. However, he also leans on familiar concepts (systems thinking, founder-led companies work well, culture alignment) and the data science/AI acceleration narrative is already widely discussed. The originality is above average but not breakthrough; he's synthesizing existing ideas more than inventing new ones.

“since its earliest inception, the whatnot product team has built was built on the somewhat simple premise, we regret that product management exists.”

“Why wouldn't you want Messi playing for your team rather than trying to have the academy coming along all the time?”

Tom is an exceptionally credible operator: CPO at Whatnot (fastest-growing US marketplace ever), former CPO at Twitch (major scale, live product complexity), Director of Product Growth at Twitter (scaling challenges). He has shipped products at multiple massive scales (consumer and marketplace), managed large teams, and his current role involves solving real, high-impact problems (GMV, seller growth, fraud). This is not a career podcaster or theoretical thinker - he is actively doing the work he discusses.

“Chief Product Officer at Whatnot, former longtime Chief Product Officer at Twitch, and former Director of Product Growth at Twitter”

“I can tell you what's definitely trending down. Folks, uh, who spend a lot of their time in their interviews talking about those like alignment meetings and driving alignment and stakeholder management”

Tom provides concrete details in places (31,832 applicants, 1 hired; Whatnot's 20-22 PMs; the accordion analogy; specific features like sudden death auctions; live lobster example; six-month planning cycles). However, he often discusses strategy and philosophy without quantified outcomes or named metrics. He references internal processes but rarely cites hard numbers on impact (e.g., what happened to velocity after restructuring? how much faster do senior ICs move?). Data exists but is somewhat sparse relative to the philosophical claims.

“In the last two years, 31,832 people applied to be a product manager at whatnot. We hired one.”

“We've just passed 20pm we have uh, kind of I think 21, 22PMs uh, in the building today, which um, for those following what our trajectory is, is pretty small considering uh, the volume of GMV that our sellers move.”

Lenny asks sharp, probing follow-ups (e.g., 'What's trending down in PM hiring?' 'How do you manage founders?' 'What did you learn from Twitter?'). He pushes back gently ('I want to hear more about that') and connects ideas across the episode. However, he occasionally lets Tom's answers run long without interrupting for deeper specificity, and there are moments where he affirms rather than challenges. The host doesn't aggressively test Tom's claims (e.g., on the superiority of top-down leadership or whether fewer PMs actually scales). The conversation is thoughtful but not adversarial.

“How do you think about that? Just like, especially as the company scales, engineers having to be in alignment meetings, having to write docs, aligning everyone, uh, taking notes, you know, all these like kind of minutiae, part of pm”

“uh, what makes me think about it, I imagine you've seen this list of all of these chief technology officers that have gone to become just engineers at Anthropic.”