26 problems with being a product manager

And it’s not moaning, it’s just reality

Robert Drury
Getting Started in Product

--

  1. There are too many ideas to keep track of, but you’re expected to keep them all safe for when you need them
  2. There aren’t enough good ideas to hit the goal you need to hit, only ideas for things that won’t affect the KPI you need to affect
  3. There isn’t enough time in the current sprint to finish all the work, every sprint
  4. There isn’t enough time to plan the next sprint, because you’re too busy with the current sprint
  5. One stakeholder wants it to work likes this but another wants it to work like that and you’re expected to make them both happy
  6. Stakeholders have never thought about the return on investment of the feature they’re requesting
  7. Stakeholders always think that their request is easy to build
  8. Stakeholders always think their request is more important than any other stakeholder’s request
  9. Stakeholders think that PMs just ask too many questions
  10. Engineers think that PMs don’t ask enough questions
  11. Engineers think that the feature requests are too hard to build
  12. You need to think tiny detail one minute and then long term strategy the next

--

--

Robert Drury
Getting Started in Product

Helping people kick start their product management career with product coaching, job application prep, & resources at gettingstartedinproduct.substack.com