Month: March 2009

  • Two questions software product managers must always ask

    1) “What is the problem we are trying to solve?” Ask the internal stakeholders who are pitching new ideas to you, ask this of customers who are asking for new features and repeatedly ask yourself to make sure you are not deviating from it as you are getting caught up…

  • Do your customers know?

    How often have your customers asked you for functionality that you already have in your product – functionality you have had in the product for a year or two? I have had this happen often enough in my career. There are two causes for this 1) You forgot to tell…

  • Messenger of problems?

    It is very easy to identify problems. What is difficult is figuring out how to solve them? Ones who do the latter are valued and get ahead. Sounds like cliche? Absolutely. But it still surprises me when I run into “messengers” of problems. Many want to bring a slew of…

  • Futility of “feature wars”

    If you as a software product manager is arming your sales force with detailed information on all of the features in your product(s), you are arming them with information to fail. If your sales team is engaging in a “feature war” with your competitors, you are bound to lose to…