Are you doing product management or bullshit management?
summary
Argues that product work becomes “bullshit management” unless teams stop shipping features and start falsifying assumptions: he deletes 1,200+ stale backlog items (1767 → 100) to create space, shows 9/10 ideas fail so use quick experiments (prototypes, 404/painted-door tests, A/Bs that take hours–days) to drop losers, and removes PO approvals and pointless reports to restore team accountability. Recommends assumption-first discovery, run cheap experiments, delete old backlog items and shares 17 practical templates (LinkedIn reach ~700k).
AI-written summary · about
chapters (26)
- 0:00Product management traps
- 4:24Bullshit management in products
- 5:31Waiter trap in PM
- 6:57Dangers of bloated backlogs
- 9:47Pitfalls of performance reports
- 11:31Avoiding consensus Frankenstein
- 12:55PO approval harms accountability
- 14:27Meeting marathon cost
- 15:59Saying no in PM
- 17:25From bridge to catalyst
- 19:31Great products remove features
- 20:34Learning from startup failures
- 22:23Assessing PM mindset
- 25:14Recognizing build trap
- 28:45Escaping build trap
- 30:57Team empowerment speed
- 34:14Key ingredients for PM
- 38:47Start with assumptions
- 41:38Agile product manifesto
- 44:04Manifesto principles
- 47:38Balancing yes and no
- 50:27Clean relevant backlogs
- 51:36Reflecting on goals
- 54:28Earning team empowerment
- 55:31Gradual agile steps
- 56:37Challenge status quo
related talks
50mFree your mind and the rest will follow - delete your backlog
26mManifesto for a Product Mindset in Agile Development
49mAgile Manifesto is outdated! We urgently need a Product Manifesto!
18mEffective backlog prioritisation for company happiness
36mProductized: How to transform your project into a product company
32mWhen Trying to Figure Out What Is Worth Building Backfires
16mScrum Buts - and how to remove them
29mHow to ruin your product by using Agile as an excuse not to plan