I had a great conversation with a former coworker about the challenges faced since we went our separate ways. I couldn’t help but think about how the things we discussed were so similar to every situation that I’ve ever faced as a product manager.
Internal Politics vs. Customer Priorities
As a product manager, when I was faced with the task of determining what we should do for our next release, the core challenge always came down to selecting the best enhancements &/or new products that would help drive market adoption, drive increase value (revenue) and drive reduced costs. At face level, this seems to be an easy task. In truth, this process is much more an artform than a science. The challenge faced by most product managers is the validity of the “truth” used in making decisions.
When the CEO or the executive management team make assertions that the number one priority for the company is to do something, it is often difficult to refute. Further, doing so can be a career limiting move if you don’t have market facts to back yourself up with.
When the VP of Sales or any respected member of the sales team claims that a particular feature which is lacking would generate a higher close rate and millions of dollars in additional revenue, it is a challenge to hold a different opinion.
When the executive in charge of customer loyalty and customer experience points to user flows or the absence of features and boldly states that changes will lead to reductions in customer attrition or increases in use and revenue, any dedicated product managers will want to deliver solutions that improve customer revenue and longevity.
When all three of these executives are demanding different things and the development organization only has capacity to implement a portion of one thing, what is the correct answer? Should you side with the CEO? Do you act on the advice of Sales? Perhaps you focus on the areas identified by the stakeholder responsible for customer loyalty & customer experience?
The unfortunate truth is that none of these individuals can absolutely know the right answer. The right answer can only be determined in hindsight — after the decision is made, the development team executes, and the organization pushes the new release to production. Even then, the product must be used and opinions made by the intended beneficiary of the enhancement before any true measure of the ROI can be made.
What makes this even more challenging is the fact that not everyone on the team has the same objectives. What if the sole objective of the CEO is to earn short-term reputation points with the board of directors? Or, perhaps she is looking to get the incremental valuation bump based upon early news of the release? What is the motivation behind the message from Sales is closing a very specific deal which will help him to get his commission or save his job? What if the reason that your seeing customer attrition has nothing to do with specific features and the real reason is due to poor customer support?
Seth Godin posted some thoughts on who the “Boss” actually is just a few days ago which helps to keep things in perspective. At the end of the day, it doesn’t matter who on the team thinks they are right. What matters is whether the decisions made add new customers, keep current customers longer, drive up revenues, or decrease the costs of servicing those customers. The “boss” will always let you know how you’re doing in a measure called revenue from which you can qualify your success using another measure called profit. Make the right investments in the right way, profit goes up. Make a mistake… and well… that’s another discussion.
So… who is driving your priorities?