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.
A few of the more mundane responsibilities I’ve collected from various Product Manager job descriptions include:
- Asses market direction and customer needs and translate these
needs into requirements for offerings that will ensure the
organization’s market leadership, growth and profitability.
(Translation: who needs a CEO?)
- Coordinate across all functions to ensure timely delivery of new
offerings and organizational preparedness for launch. (Translation:
must be competent at herding cats!)
- Serve as the external spokesperson and champion for assigned
products and through speaking, writing and promotional activities,
position selfas thought-leader in target markets. (Translation: after
doing the CEOs job and herding cats, must put on regular, impassioned
Oscar-winning performances without a script.)
I left out the additional six or seven bullets that roughly translate to "must act mild-mannered while functioning as superhero. Allergies to kryptonite not allowed." Clearly, the Product Manager has a big job and an ability to directly impact the fortunes of a business.
A note on the dichotomy between Product Management and Product Marketing
Many organizations (especially in technology) have bifurcated the traditional role of the Product Manager into two distinct jobs: Product Manager (internal-development and requirements orientation) and Product Marketer (external, pricing, promotion and positioning oriented). Like any attempt at organizational structure, there are benefits and disadvantages to this approach-I will tackle this thorny issue another day. For the purposes of this posting, I am viewing the role traditionally and holistically.
The Impact of Super-Successful Product Managers:
The Super Product Manager is rare. In over twenty-years of leading PM teams, I’ve worked with exactly a handful. And while I’ve been graced with the contributions of dozens of outstanding professionals, this small group of professionals stand head and shoulders above the rest for their ability to tangibly make a difference in their businesses.
In one noteworthy case, this cantankerous individual had a remarkable ability to understand the business of our clients and translate this understanding into feature requirements that when implemented, earned rave reviews for cost savings from speed and efficiency improvements. We grew the business on the back and brain of this gifted individual.
In another example, this person truly was impervious to kryptonite. The individual’s gifts were (are) multi-faceted. A unique and detailed understanding of our offerings, a remarkable sense of vision on where the market was moving and a tireless commitment to internal education and persuasion. It helped that this individual was/is a complete, well-rounded business person as well.
In both cases, the individuals described above were grossly under-appreciated. Success in their role required a level of aggressiveness and a never-say-die attitude that rubbed some the wrong way. They were irrationally called on the carpet for organizational failures and often under-appreciated by their own team members for a variety of reasons. Nonetheless, they both lived up to the lofty expectations inherent in the job description bullets above and at the end of the day, their fingerprints were all over our success. I would gladly deal with the challenges of leading and supporting these Superstar Product Managers and so should you. It is with individuals such as these two in mind, that I’ve developed my own list of attributes that make-up my view of the best Product Managers.
The Attributes of Great Product Managers:
- An understanding of their offerings developed from two perspectives: creation and use. Most Product Managers bring one or the other-they come from a technical capacity in engineering/development (the majority) or they have client-side experience (the minority). I want both and they are darned hard to find. Most often, you have to create this well-rounded person.
- A bedside manner (interpersonal) that is calm, confident and politely assertive. Product Managers have the single most challenging diplomatic job in an organization. Of all others, they must be successful at getting teams and individuals to follow their direction in a coordinated manner. People will follow this true leader if he/she commands respect and has credibility in their eyes. The first bullet above earns credibility and the communication style and ability to logically and emotionally persuade commands respect.
- The mind of a strategist balanced with the results-orientation of a COO. Again, it is easier to find someone that is a good strategist and someone that is execution-focused than it is to find someone that is both. The best Product Managers are true strategists constantly thinking about the market forces driving their clients and competitors and working on identifying ways to monetize those forces. They are also hell-bent on getting products to market in an effective and timely manner. These individuals propel organizations forward with their vision and their drive.
- A savvy perspective on positioning and promotion. One of the laments of many Marcom teams is the inability of Product Managers to articulate the value proposition for their offerings as well as to serve as an effective spokesperson with industry influencers. The best Product Managers relish the opportunity to talk about their offerings, yet they have a keen sense of describing the value proposition and making the message tangible and meaningful. In contrast, many/most Product Managers suffer from a bad case of "blah, blah, blah."
The Bottom-Line:
The best in any profession are a wonder to observe as they apply their skills to solving problems and creating value for their organizations. The right Product Manager can literally propel an organization to success, yet organizations often grossly misfire in their selection and development of people in this critical role. In an organization where "products" are the life-blood of growth, it is up to the firm’s leadership to recognize the value from this role and to develop a rigorous approach to identifying and developing these gifted professionals. In an era where the battle for brains determines a businesses success or failure, it is imperative that firms recognize the critical role and contribution of the Product Manager.
Art:
Hear, Hear!
You’ve brought to the forefront one of the key issues of organizational design – the product management/marketing model that they adopt and it’s implications on both their staffing approaches and ultimately, their innovation strategy. All to often, technology and service firms “fall into” their model, not by design, but mostly by happenstance and/or the personalities of their founders (esp. the case with early stage technology firms where the development/product management function is co-located in the technical founder.)
Look forward to hearing more from you on this, particularly your thinking on the organizational trade-offs…
Greg, thanks much for your insightful comments. I’ve long felt that organizations are leaving big money on the table by misplacing and misdirecting Product Management. Couple that with a frequently flawed approach to staffing this important function, and there is a tremendous amount of opportunity for improvement. BTW, I agree on your small company issue, and have seen even worse handling of the function in global tech firms. It’s good to have insightful people like you and the pros at Pragmatic evangelizing on best practices. I am excited to join the cause. -Art
As a product manager, I want to totally agree with you and support the nomination of PM as MVP. But I want to point out that this focus on the the PM as an individual source of success also unfortunately works the other way as a single point of failure.
Companies should not look at the product management function as a role of an individual. The function is no different than the sales function or the marketing function or other functions in the company. There needs to be a properly staffed team of people executing on the things that product management is required to do.
Want a neck to strangle if things don’t work out — look at the VP of PM first (if there is one — which there should be). This is no different than looking at the VP of Sales if the numbers aren’t met. Yes, there are those rare individuals who can “do it all”, but the reality is that is true for any group. It take a team to build a product! 🙂
I think companies should stop having a false expectation that the product management function can be successfully carried out by individuals and instead realize that small teams are needed, possibly lead by Dir. level individuals. These teams — a mix of business/technical, inbound/outbound etc. can get the job done in an efficient, scalable and repeatable way, without single points of failure.
Saeed
Saeed:
When I first read your post, I found myself disagreeing, but after re-reading (and reconsidering), I think I may be in agreement. It is the PM’s responsibility to form, lead and drive these small, cross-functional teams. responsibility and accountability for successful products are thus shared, so there is no single point of failure, and a high-performance team can support and/or offset a poorly performing team member.
However, it is still important to hold these team members – as well as the team leader (the product manager) individually responsible for their own contributions, and the PM responsible for overall success. When and if the team is not performing, it is the PM’s responsibility to identify why the team is not performing, cofrrect it within the context of the team if possible, and where necessary, call in outside support via escalation (which should be identified and discussed at appropriate phase-gate reviews.)
All too often, I have seen leaderless, “self-empowered” teams flounder ande fail because where there is shared responsibility there is no responsibility…decisions are not made because of a dynamic requiring total consensus, an “I’m OK, you’re OK” group dynamic fails to drive the team to meet deadlines, etc…
Arthur,
I think we may be in “violent agreement”. I’m not implying that no one should lead. Clearly someone has to lead the charge, and a Product Manager is an appropriate person for that, but that person should be a relatively experienced person, roughly at a Dir. level position. Under them should be a small team of people with a breadth of skill sets, ranging (as needed) from deep technical to deep business.
This PM team structure, with a clear leader responsible for overall product leadership with other teams such as Dev etc. is much more efficient and scalable than the (all too common) alternative of having a single individual who must be multi-faceted business/marketing/technical etc. jack-of-all-trades, and master-of-all as well.
That perception of the role of Product Manager is the one I have trouble with. Companies need to understand the breadth of the product management function and realize that a few additional headcounts with specialized skills will create a scalable and highly impactful team that will help optimize the efforts of all those other dependent groups, such as marketing, sales, development, support etc. It makes clear business sense to me.
I write about this topic in this article…
http://www.pragmaticmarketing.com/publications/topics/05/0501sk2
Saeed
P.S. I’ve added you to the blogroll on our blog: http://onproductmanagement.wordpress.com
Saeed:
I think we’re all in violent agreement (I wrote that last post, not Arthur.) Arthur alluded in his article to the issues surrounging the role of product management vs. product marketing ( a favorite topic of mine, which I’m starting to discuss at my firm’s own blog (http://quantumleadersblog.com/). I’d be interested in hearing your perspectives on this. My own is that many of the strategic marketing issues can and should reside within the PM function, but that “tactical” marketing execution – marcomm, PR, etc.. is better executed elsewhere, while still being responsible to the PM and overall product team.
On my own part I’ve added Arthur’s blog to our blogroll, and will do the same with yours….
Gregg and Saeed, thanks for the participation and insightful comments. I look forward to reciprocating and adding both of your excellent blogs to my roll as well. -Art
Gregg,
Sorry about that. I didn’t look at who posted the comment and assumed it was Art.
Saeed
Product Manager as MVP
Art Petty discussing “In support of the Product Manager as MVP.”
I’ve always been amused by the hole that PMs get dug into. If support is weak, the PM may help resolve customer problems. If QA is weak, the PM will often test new releases. If sales is weak, the PM may need to spend time closing deals and responding to RFPs. Because competent and intelligent PMs can do these things, the organizations tend to remain weak in those areas. It becomes hard to justify incremental cost to strengthen them because it’s very hard to quantify what is being sacrificed–namely, the PMs positive influence on end product quality.
Just an observation from my 4-5 year stint. I’m too busy multi-tasking to figure out how long it’s actually been.
[…] won’t let go and wants to be an individual contributor as well as a leader. In his post, In Support of Product Manager as MVP, Art Petty shares, “In an organization where products are the life-blood of growth, it is up to […]