Based on Lenny's Podcast data
PM Theater
Project Managers in PM Clothing
"They're dramatically overpaid for the value they provide. Because it's a project management role. It is a lot easier to deliver output than it is to deliver outcomes."
- The pandemic hiring surge created armies of agile coaches, product owners, product ops, business analysts
- Most of them are project managers — not product managers
- Output = features shipped. Outcome = problems solved for users.
- PM theater: the rituals of product management without the substance
The tell
Real PMs obsess over outcomes. Theater PMs obsess over roadmap delivery, story points, and status reports.
The Core Distinction
Feature Teams vs. Empowered Product Teams
Feature Team
Stakeholders decide what to build. PM schedules, coordinates, reports. Engineers execute tickets. Success = shipped on time.
Empowered Team ✓
Team owns the problem, not the solution. PM, design, engineering collaborate on discovery. Success = measurable outcome for users.
- Missionaries vs. mercenaries: feature teams are mercenaries executing orders. Empowered teams are missionaries who believe in the mission.
- The best tech companies (Apple, Amazon, Netflix, Google at its peak) run empowered teams
- Most companies run feature teams and wonder why their product isn't great
"Too many PMs view themselves as a victim of their company, like they're stuck in a feature team and there's nothing they can do. I think that's not true. There is so much they can do."
The shift
Getting to an empowered team often starts with the PM — proposing outcome-based goals, doing real discovery, and demonstrating what good looks like.
Product Discovery
Discovery Is the Job — Delivery Is the Cost
- The risk: will users buy it? Can we build it? Will it work at scale? Is it ethically sound?
- Discovery is about tackling these risks before you build — not after
- Delivery (building) is expensive. Discovery (prototypes, tests) is cheap. Do more discovery.
- Strong PMs protect their team from building the wrong thing — not just shipping the right scope
- Product sense = understanding what users need before they articulate it
"The skills you need to be a great product manager: product sense, business acumen, and tech fluency. Not project management, not stakeholder management."
The Transformed thesis (new book)
Companies can move from feature factory to product company. But it requires changing how leaders think about product — not just re-labeling project managers as PMs.
The PM's Job
What Great PMs Actually Do
- Fall in love with the problem, not the solution
- Know your users better than anyone else in the company
- Partner with engineering as equals — not as order-takers
- Own the outcome, not the output. Push back on feature requests without clear outcome rationale.
- Learn continuously: tech, users, business, data
- Be the missionary — believe the mission matters and make engineers believe it too
On AI's impact
AI reduces the cost of building — which means discovery becomes even more important. The bottleneck shifts to knowing what to build, not how to build it.
Contrarian
PM Advice Worth Unlearning
✗
PMs are the CEO of the product
INSTEAD →
✓ PMs have no authority. They lead by influence, user insight, and trust. The CEO metaphor sets wrong expectations and leads PMs to act like managers instead of missionaries.
✗
A good roadmap = a good product team
INSTEAD →
✓ Roadmaps are output plans. Great teams work from problems and outcomes. A beautiful roadmap with no discovery behind it is theater — it just looks like product management.
✗
Ship more features to stay competitive
INSTEAD →
✓ Feature volume is not competitive advantage. Solving real problems for users better than anyone else is. Most feature factories ship more and win less — they just exhaust their teams doing it.
✗
You're stuck if your company runs feature teams
INSTEAD →
✓ You can demonstrate empowered team behaviors even inside a feature factory. Propose outcome goals. Do your own discovery. Show what good looks like. Change often starts with one team.