wear my respect on my shirt-sleeve for the many dedicated Product Management professionals that hold down what I believe is one of the most difficult and one of the most critical roles in today’s fast moving technology and B2B organizations. I firmly believe that these talented and well-rounded business professionals are potentially some of the most valuable assets in an organization’s talent pool.
It was a tough week for blogging. A perfect storm of business and personal schedule challenges conspired to keep me from spending quality time on the blog. OK, and the fact that I have been holding steady at 99 posts for a few days, and somehow it seemed like I needed to create something truly remarkable for the milestone, 100th post. I'm over the "need for remarkable" part, but thought I would take a few minutes this Saturday morning to reflect back on what I've learned in this half year of blogging about all things management, leadership, strategy and project and product management.
Product Management's position in the organization is a topic that invites vigorous debate, usually around whether marketing or development should own the function. While any debate about optimal organization structure can sound a lot like the radio and television sports shows where people argue fiercely over the greatest running back or quarterback of all time (there is no one right answer!), the PM issue merits some consideration. Of course, the right answer may be, "It depends."
The relationship between the Product Manager (or PM team) and the Sales force is one that is filled with great potential for all parties and also prone to frequent misuse or abuse. Frankly, it is a complicated relationship that should be governed by some shared rules of engagement and some good commonsense about when to throw the rules out in support of getting the job done.
y posting, The Product Manager as MVP, offered my perspective on the potential for the professional in this role to have a material impact on a firm's success. I truly believe in the power of this function to shape firms, and for individuals and teams of Product Managers to serve valuable formal and informal leadership roles in organizations. I've also seen some remarkable wholesale failures in Product Management—at the team and individual levels. Truthfully, these failures often have their root causes at the top of the team or even elsewhere in the leadership or organizational design structure. Nonetheless, the symptoms become visible in Product Management. While we all love studying and reading about best practices and successes, in my experience, most of the best lessons come from studying the train-wrecks. Consider these as cautionary tales.
Few roles in B2B and technology organizations carry loftier expectations or face more challenging tasks than that of the Product Manager. This position tends to be backed by a job description with responsibilities that makes many executive roles look tame by comparison. The right person in this important role can mean the difference between wild success and mediocre performance for the business. And while organizations commonly under-staff (both in number and in power/experience) and over-describe (expectations are excessive), it is a thing of beauty when you latch onto a professional Product Manager that understands how to build value through this role. This super-employee operating in this tough role consistently gets my vote for MVP.
