ATRIUMsearch → argument graph
Video · 2026-08-02 · 1h 25m · 6 moments

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

✦ AI generated

timeline · colored by role

01
Claim

We regret that product management exists — it's better to not assume we need a PM in every place, and we only hire one where there's a really specific need.

Tom Verrilli explains the core premise behind Whatnot's product team: 'We regret that product management exists.' It's a framing device to force the org not to hire PMs by default, but only where specific need justifies it.

transcript

Tom Verrilli: the whatnot product team was built on the somewhat simple premise. We regret that product management exists. Not a thing you probably hear from a lot of CPOS. We articulate 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's really specific need. It is better to not assume we need a PM in every place.

02
Mechanism

The only argument for product management as a specialist function is that it's a trade, not a qualification — but the more you abstract engineers and designers from doing PM work, the more their muscle atrophies.

Verrilli explains that PM is a skill built by reps, and abstracting engineers/designers away from product decisions under-develops their muscle. So Product management should be deployed for leverage on specific high-stakes things, but avoided wherever possible.

transcript

Tom Verrilli: 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. And as every private trainer has ever told me, muscles are built by reps. And so the more you do it, the better you get at it. But the the flip side of that is the more you abstract your engineers and your designers from doing the same thing, their muscle gets underdeveloped. And so I think product management plays a really important role. And I think, you know, you can deploy product management to have really important leverage on particular things that need to go really well. Um, and in a lot of ways doing that lets design and engineering be the best they can be at their craft in those situations. But wherever possible it's kind of optimal to not have a product manager uh and instead have design and engineering going through those those kind of steps and making sure that their muscles are well repped.

03
Mechanism

Hiring so many PMs infantilizes engineers and designers who are perfectly capable of making good decisions, but never had to because there was always a PM to babysit them.

As tech companies scaled, an HR ratio emerged — for every six engineers you add a designer and a PM. Verrilli argues this default ratio produced too many PMs and infantilized engineers/designers who no longer needed to make decisions themselves.

transcript

Tom Verrilli: as tech companies scaled and we ended up hiring so many engineers somewhere along the line um and I don't want to pin it on like HR but somewhere along the line this kind of HR ratio of like a pod popped into being you know every time you hire six engineers you add a designer you add a PM you add an EM... In most cases, you probably don't need a PM for notifications infrastructure, right? Engineers are perfectly capable of understanding how that works. And in a lot of ways, you know, as we just described, 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 to babysit them.

extends · 1supports · 1

04
Claim

The best use of PM IC work is literal hands-on work — reading support tickets, pulling your own data, querying the codebase directly — and VPs/directors should spend most of their time doing IC work rather than just coaching.

Verrilli is excited about PMs moving back to hands-on IC work. He personally spends ~50% of his time on IC work, and all PM managers at Whatnot spend 90%+ on it, because senior people can make faster, better decisions and stay connected to ground truth.

transcript

Tom Verrilli: What does IC work for PM in this context mean? Does it mean shipping code, building or is it like running a team, writing owning a road map, writing the strategy dock? Imagine it's the second bucket. Uh whatever is required to kind of like most effectively ship is the short answer. Um have I personally shipped some production code at whatnot? Yes... But I do think it starts with like 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? You know, have you queried the codebase directly in order to understand how things work? and then have you written the spec are you then running your stand up... You can see my scar tissue coming through. Um, uh, on our team, uh, everybody is like there are managers, there's like I think four or five people across the team who manage other PMs. All of them would spend 90 plus% of their time doing IC work. I'm still probably 50% of my time doing IC work personally.

05
Prediction

Live commerce combines the scale and convenience of the internet with the social, cultural experience of physical shopping — it's a completely different customer need from agentic commerce, not a competitor to it.

Verrilli explains that most retail is low-intent shopping, which is why e-commerce has never exceeded 20% of US retail. Live commerce is the first to combine internet scale with the social/cultural experience of malls, serving a need agentic commerce won't replace.

transcript

Tom Verrilli: Actually a lot of shopping is low intent. I I'm going to the mall. I might be because I've got a wedding coming up and I don't have anything to wear and I'm going to wander around and see what people have available because I don't actually know specifically what I want... What I think live commerce does is it's the first time that we've ever managed to kind of like bring together scale and convenience of the internet and also that same kind of like social cultural experience uh of physical shopping... I think it's not really in kind of like competition with aic. I think it's a completely different kind of like customer need.

06
Anecdote

Averages mean nothing to the individual — relying on average metrics leads to deprecating features that are the core 100% use case for a small group of people, so data around averages must be treated with caution.

In the 'Fail corner,' Verrilli shares his most recurring failure: relying on average utility or adoption figures, which hides small groups for whom a feature is 100% of what they do, and can blow up a real community or business.

transcript

Tom Verrilli: there probably is a really common thread to it and I think it's probably an easy trap for for any PM to fall into which is like um averages mean nothing to the individual is probably the thing that I've like really scarred by. uh in any sizable population, it's really attractive to go and look at like average utility or average adoption of something and then you find that like you know only 3% of people use something and you're like cool we can probably get rid of that feature. It's not used widely but if you don't go a layer deeper and be like actually for like you know it's only 3% of something but there's a group of people for whom that's 100% of what they do... this is their core use case and for expediency's sake because somebody doesn't want to maintain a feature anymore you're just going to deprecate it and then it turns out you like blow up the use case of that group of humans... I think, you know, I've probably screwed up in all of the ways in my career, but most of the time I've made genuinely like I'm disappointed in myself levels of decisions. It's typically that I've relied on averages without thinking about the individual use cases that that are hidden underneath.

Highlight slides
Related episodes