--- id: ins_verrilli-dri-eliminates-pm-layer operator: Tom Verrilli operator_role: Chief Product Officer, Whatnot co_operators: [] source_url: https://www.lennysnewsletter.com/p/this-cpo-regrets-that-product-management source_type: podcast source_title: "This CPO regrets that product management ever became a job" source_date: 2026-08-02 captured_date: 2026-08-06 domain: [product, org-design] lifecycle: [team-structure, leadership] maturity: applied artifact_class: framework score: { originality: 4, specificity: 5, evidence: 4, transferability: 4, source: 4 } tier: B related: [] raw_ref: "" --- # Fixed PM pods produce alignment theater; rotating problem-centric DRI assignments restore judgment to the people doing the work ## Claim Permanent product manager assignments to feature teams create a layer of coordination that removes judgment from engineers and designers. Replacing that layer with six-month problem-centric DRI roles, which any discipline can hold, restores decision ownership to the people closest to the work. ## Mechanism The standard PM model assigns a product manager to each team as a permanent role, making them the decision translator between strategy and execution. Verrilli argues this structure infantilizes engineers and designers: because someone always interprets the work for them, they never develop the judgment to do it themselves. Over time the PM layer becomes load-bearing not because it adds value but because the team has learned not to decide without it. The DRI (directly responsible individual) model inverts this. Instead of assigning PMs to teams, Whatnot assigns a DRI to a problem for six months. The DRI can be a PM, an engineer, or a designer, depending on which discipline is best positioned to own that problem's outcome. When the six months end, the assignment rotates. This forces every discipline to develop judgment, eliminates permanent coordination overhead, and keeps decision authority close to the work rather than above it. Whatnot runs 21 to 22 PMs across the entire marketplace with this model. The headcount efficiency is a byproduct of the structure, not the goal. ## Conditions Holds when: the company is mature enough to trust engineers and designers with outcome ownership, problems can be scoped discretely enough to assign a single DRI, and leadership is willing to tolerate the learning curve as non-PMs develop judgment. Fails when: the organization lacks the psychological safety for engineers to make product decisions without cover, or when problems are too interdependent to isolate under one DRI. Also fails if DRI assignments are treated as nominal ownership without real decision authority. ## Evidence Verrilli stated in the Lenny podcast interview on August 2, 2026: > "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." The Whatnot implementation: 21 to 22 PMs covering the entire marketplace operation, with six-month rotating DRI assignments across PM, engineering, and design disciplines. ## Signals - Your product reviews consist mostly of status updates rather than decisions, indicating the PM layer is coordinating rather than deciding. - Engineers escalate questions to PMs that they previously would have resolved in design review, indicating atrophied judgment. - PM headcount grows with team headcount rather than with problem complexity. ## Counter-evidence The DRI model requires a specific organizational maturity. Companies where engineers and designers have historically operated inside tight PM-defined specs will face a long transition before judgment distributes. The model also concentrates risk: a poorly chosen DRI for a high-stakes six-month problem creates more damage than a mediocre PM who can be redirected weekly. Whatnot's marketplace is a specific product context; companies with highly regulated products or complex stakeholder requirements may not achieve the same PM-to-engineer ratio. ## Cross-references - (none in current corpus)