Don't solve non-problems…
summary
Argues that developers become better by adopting product management habits and gives concrete practices: write a one-sentence problem statement at the top of the ticket (example: put the missing CFO data into the CSV, not build a giant report), use a spreadsheet or ticket system to put priorities in a shared ordered list, and cut scope ruthlessly—avoid hypothetical, trivial, unsolvable or conflicting “custom vs universal” requests. Offers a real avoided waste: a feature set dropped when perfect data proves impossible.
AI-written summary · about
chapters (9)
- 0:00Introduction to PM for devs
- 4:29Product management as a tool
- 7:15Embracing real problems
- 9:27Problem statements vs features
- 12:21Cutting meaningless work
- 14:48Handling common non-problems
- 20:59Ordering and prioritizing
- 24:11Executing and iterating
- 27:17Q&A and conclusion
related talks
30mAre You Doing Product Management or Bullshit Management?
15mHow to NOT waste time
36mDEVELOPER ORIENTED PROJECT MANAGEMENT
41mProduct Owner & Developer: An Unexpected Journey
29mDriving clarity in ambiguous projects
39mYou should stop writing code
17mMake Work Not Suck Improving the Developer Experience
42mSlaying the Backlog Beast: A #NoBacklogs Approach to Product Management