Hire the Right Product Manager: Skills and Experience to Look for Beyond a Job Description or Resumé
A smart man asked me last week, "What do you look for when hiring a product manager?". A great question, and one I'm not sure I answered fully at the time because there's so much to consider, and so much at stake. An average product manager vs. a great product manager can make such a huge difference in a product and its market success, it can translate to hundreds of thousands or millions of dollars difference in revenue. How could a company ignore putting a product manager through the interview wringer?Product management is the science of distilling a real, immediate customer problem into a solution those people will pay for (in time or money). In the world of technology, where I live, that means specifying the target market, target buyer, features, functions and customer experience for software, hardware and/or internet sites. The Must Have traits are crucial for making that happen and getting a timely result that resonates with the buyer. Most are personality or behavioral traits, rather than specific skills, and therefore are much overlooked during interviews which tend to focus on skills and domain.
(ordered from least to most important)
10. Domain Knowledge
9. Verbal and Written Communication Skills
8. Organization
7. Goal-Driven Motivation
6. Analytical Thinking
5. Ability to Make a Decision with Limited Information
4. Selflessness / Lack of Ego
3. Problem Solving Skills
2. Social Skills
1. Empathy
10. Domain Knowledge
Understanding your market is something that will help any product manager when starting out at your company, but too many hiring managers put far too much emphasis on this. They say
nobody can just learn my industry". Of course if a product manager (PM) "gets" the market and the customer, their ramp speed and usefulness will come much faster. But, having experience within a market doesn't make a great product manager. In many cases, someone who thinks they understand everything about a user or a market becomes closed-minded, stops listening, and creates a barrier to developing good products. Or, applies the same "knowledge" to every problem.
In many cases, someone with strong PM traits and a solid understanding of the product lifecycle process can make a bigger impact with a new product because they're listening 100% to the user - they have no choice. I've seen so many companies hire a product manager - even at a VP level - because they come from a competitor or from 'the industry', and so many times that person fails to make a difference. So, when interviewing for a product manager, weight domain knowledge the least important of all attributes. A great product manager can start making an impact in 1-2 months in any domain (as long as its not super-super-technical).
9. Verbal and Written Communication Skills
Product managers are the evangelists for a customers, potential customers, and for the company. They must be able to quickly and clearly articulate plans, goals and processes to many different personality types, all the time. Many times they'll be in sales situations directly interfacing with prospects or customers. They take executive feedback to the engineering team, and take engineering feedback to the marketing team, and customer insight and data to all teams. They've got to be able to speak well, create excellent, readable and influential Powerpoints and product specifications. They represent the company to the press, to industry analysts and to everyone at tradeshows.
A great product manager is a great communicator and naturally becomes a central hub of information flow about a product. A superlative product manager takes this one step farther, and creates an automated hub of information about a product that removes him from the day to day as much as possible. The superlative product manager understands the importance of communication as well as the fact that he's only one person, so intranets and portals, or at least document shares, are critical for keeping communications moving without personal involvement.
8. Organization
Product managers must juggle dozens, hundreds or thousands of moving parts - feature lists, schedules, names, faces, data, specs, customers, developers, sales people, special customer requests, bugs and fires and more. A product manager must be able to triage issues and move quickly through the items (bullets) that other constituents send (fire) at him every day - so he can tackle the things that are actually on his own To-Do list. The product manager must be constantly classifying and organizing things for immediate projects and also for reference and for future projects. Not everything is immediate, so having an an excellent storage system / scheme (and excellent memory) is critical. If a product manager isn't organized and can't move through the hundred emails they get before 10am, they'll never have time to make an impact and will get put into 'reactive' mode very quickly. They become pawns of the organization, rather than leading the organization to new revenue opportunities.
7. Goal-Driven Motivation
6. Analytical Thinking
Product managers must be able to acquire, organize and analyze data and come up with solid conclusions. Like any science, there are theories and there are controlled experiments to test those theories. Theories can be created from customer feedback, market feedback or ideas from executive meetings, but having the ability to run a multi-variate test or experiment to prove or disprove the theory is the difference between a market leading product and a dud. Great products are developed according to data - qualitative and quantitative - from multiple sources. There are budgets, there are feature priorities, there are time constraints. Good math and the ability to extrapolate, work back, and identify the big wins is simply critical.
5. Ability to Make a Decision with Limited Information
4. Selflessness / Lack of Ego
Problem solving is critical - finding a solution from the data and resources you have at hand. Figuring out what features to cut if the deadline slips. Determining if priorities need to be juggled. Handling 100 requests at the same time. It's all in a days' work. Product managers must be able to solve problems that are 'outside the book' without running to their boss for help. Much of this is natural or 'nurtured' intelligence but a lot of it is being able to see the big picture, envision multiple scenarios, then frame each in context - 'what will be the most effective way to reach my goal?'. Problem solvers get things done without burdening other staff, complaining, or delaying projects.
Problem solving is also critical when dealing with a customer problem. A product manager has to come up with one on more ideas on how to solve the problem they identify. They have to be able to envision software before its built, screens and interfaces before they're designed. They've got to be able to solve the customer's problem FOR them. Even the best customer /user / buyer will never be able to describe the best way to solve a problem, that's the key to what the product manager does.
So, that's my Top Ten list. I'm sure there's more, and related items, but you can only look for so many behavioral or personality traits during an interview. The thing that's not on this list is execution - has a PM successfully done this before. That's a leading indicator that they can do it again, regardless of domain.