Key Takeaways

  • Claire Vo, a product executive with more than two decades of product leadership, argued at the Lenny and Friends Summit that the traditional product roadmap is dead.
  • Roadmaps originally existed for one reason: engineering capacity was scarce, forcing product managers to draw a hard cut line on backlogs.
  • AI-driven coding agents make every visible feature technically plausible and fast to build, eliminating engineering bandwidth as the primary constraint.
  • When execution capacity outpaces strategic clarity, backlog lists turn into ammunition for what Vo calls a "slob cannon," spraying low-value features at users.
  • Modern product teams must shift their operating model toward high-ambition convictions, disposable software, and explicit tiers of customer commitment.

The Death of the Engineering Scarcity Cut Line

For twenty years, product management operated on a simple economic reality: engineers were scarce and expensive. The primary job of a product manager was to prioritize a massive backlog, run estimation meetings, and draw a brutal cut line between what got built and what got killed. The static quarterly roadmap served as the peace treaty between engineering, sales, and executive leadership.

Vo believes that era is over. As she told the audience at the Lenny and Friends Summit: “The road map has been the defining artifact of our industry, of our careers. It's supposed to tell us and our teams where we're going, what's next, and what matters. And I have been in product for over two decades. And I believe, fingers crossed, a lot of us in this room are about to write our last road map.”

When coding agents can generate code and ship working interfaces in minutes, the cut line disappears. The problem is no longer filtering out ideas your engineering team lacks the hours to build.

When Execution Is Free, Conviction Is the Bottleneck

If you can build anything in your backlog this week, buildability stops being a proxy for value. The bottleneck moves from technical delivery to strategic judgment.

Vo described this shift directly: “And now I feel like I have more execution capacity than true conviction about what to build. So my bottleneck has moved from building, what can I build, to believing: what do I believe is actually worth building.”

When building becomes cheap, teams face an uncomfortable truth. Most product roadmaps were full of filler features designed to keep engineers busy or placate noisy enterprise clients. Without the natural constraint of engineering scarcity, teams that lack strong conviction will drown in their own speed.

The Slob Cannon Trap and Disposable Software

When building costs fall to zero, bad teams do not build better things; they build more junk. Vo warns that an uncurated backlog becomes dangerous when execution is frictionless: “This feature list I say becomes ammunition for a very powerful slob cannon.”

Teams shoot dozens of undifferentiated features into production simply because they can. The software becomes bloated, unmaintainable, and confusing to customers.

To avoid the slob cannon, Vo argues for a different approach. First, treat code as disposable rather than precious. If building is fast, throwing away an experiment costs almost nothing. Second, replace long-term feature promises with high-ambition convictions and clear tiers of customer commitment. You commit to solving specific customer outcomes and testing bold hypotheses, rather than locking your team into a six-month delivery schedule of minor buttons and settings.

What to Do With This

Audit your current product backlog tomorrow morning. Delete every low-priority ticket that was sitting beneath your team's historical cut line, rather than feeding it to an AI coding tool just because it is now easy to build. Replace your six-month feature delivery chart with three high-conviction problem statements that your team will rapidly test and discard code against this quarter.