Skip to main content

Evaluating a Product Manager's Performance

In a previous entry, I argued that companies should not evalute a product manager's performance flatly in terms of product revenue. How should, then, a company evalute a product manager's performance?

One way that Steve Johnson mentions on the productmarketing blog is in terms of the number of on-site visits to prospective and existing customers. The Pragmatic Marketing folks advocate basing bonuses on the number of on-site visits. I believe that on-site visits (in particular, one-on-one interviews) with customers are the single most effective way for a product manager to gain an understanding of the market. I have observed also that companies tend to underestimate their value.

However, I don't believe on-site visits quite get at performance. On-site visits are a means to an end. That end is an in-depth understanding of the market that a product manager successfully communicates to developers, sales, and marcom. If developers, sales, and marcom then do their jobs right, the product will likely succeed.

A company should evaluate a product manager's performance in terms of how well she communicates an understanding of the market to the development, sales, and marcom teams. I propose that a company can measure this performance by surveying the staff of those departments, asking them how well the product manager has imparted information about the market. Ask sales how well the product manager has profiled the different buyers. Ask development how effectively and convincingly the product manager has communicated the requirements. Ask marcom how clearly and credibly the product manager has defined the key messages to use in marketing programs.

Comments

Unknown said…
A 360 degree audit is a good idea but don't forget that sales, marcom, and development are often expecting tactical product support rather than market information. I'm not sure I want them determining my income so subjectively.

Here's a thought: what if we bonused product managers on next year's revenue?
Roger L. Cauvin said…
Important points, Steve.

Expect a couple of entries in the future refining the 360 degree audit idea to address the "tactical expectations" problem.

In the meantime, can you elaborate on your idea to bonus product managers on next year's revenue?
Scott Sehlhorst said…
Interesting stuff. I went back and updated an article I wrote about this (from Jan 2006). I do agree with your emphasis on customer engagement.

http://tynerblain.com/blog/2006/01/30/five-measures-of-product-manager-performance/

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Stop Validating and Start Falsifying

The product management and startup worlds are buzzing about the importance of "validation". In this entry, I'll explain how this idea originated and why it's leading organizations astray. Why Validate? In lean startup circles, you constantly hear about "validated learning" and "validating" product ideas: The assumption is that you have a great product idea and seek validation from customers before expending vast resources to build and bring it to market. Indeed, it makes sense to transcend conventional approaches to making product decisions . Intuition, sales anecdotes, feature requests from customers, backward industry thinking, and spreadsheets don't form the basis for sound product decisions. Incorporating lean startup concepts , and a more scientific approach to learning markets, is undoubtedly a sounder approach. Moreover, in larger organizations, sometimes further in the product life-cycle, everyone seems to have an opinio

What Product Managers Can Learn from the Apple iPod

The Story When Apple unveiled its iPod digital music player back in October 2001, I dismissed it as a  parity product . I already owned the Cowon iAUDIO CW100 MP3 player, loaded with my favorite tunes. There was Apple, generating great hype over the iPod as if it were a breakthrough product. The idea of a portable digital music player was nothing new. The first mass-produced MP3 players came out in 1998. In late 2001, the concept may have been new to a lot of Apple customers, but it wasn't new to me. I proudly showed my MP3 player to friends when they gushed about the iPod. Thus Apple's iPod was not an innovative product in and of itself. Years later, however, I realized the significance of ecosystem of which the iPod was a part. Apple had released iTunes (with technology purchased from  SoundJam MP ) and created the iTunes Store for finding and downloading music. Unlike Napster , it was a safe and legal way of distributing and acquiring music. The prior way of playing