Common Product Management Screw-ups That Strike Even the Experienced

Last updated on 

  1. Acting like a Requirements Monkey.

  2. Punting on strategy.

  3. Not focusing on a particular target market.

  4. Not meeting with enough customers often enough.

  5. Not meeting with prospects and non-customers (aka potentials) often enough.

  6. Not truly understanding the real problems faced by your target market.

  7. Hearing only what you want to hear.

  8. Being afraid to draw pictures, lest you offend your UX designer.

  9. Writing a Magnum Opus of a requirements doc or strategy doc, primarily to cover your ass.

  10. Forgetting to incorporate features into your product that help you measure success or failure, and thereby improve over time.

  11. Going along with a development process that can't adjust when faced with negative market feedback.

  12. Becoming Development's co-dependent, and having them come to you about the placement of every freakin' pixel.

  13. Allowing a piece of junk to ship.

  14. Making the product hard to buy or up-edition.

  15. Thinking that landing reference customers for a new product/release is someone else's job.

  16. Letting the release treadmill create a "boat anchor" editioning and pricing situation, where customers can't upgrade without major migration headaches or losing functionality.

  17. Assuming that everyone that stands in your way is an asshole or a political player.

  18. Neglecting to spend the time building rapport and credibility with engineers.