What makes a good product manager?
I came across this question tonight on Quora. It’s an area that I have quite a bit of experience so I thought I’d post my thoughts:
Having worked with a number of companies in a product management consulting capacity, I’ve found that the roles & responsibilities of a product manager vary widely based on company. That said, here are some common threads that I believe are generally indicative of a good product manager:
- Good product managers are extremely detail oriented throughout the product development process. You should be able to identify and resolve inconsistencies in the features/application you are defining and participate in the entire development process. Driving a quality product to release may require hundreds of minor adjustments, clarifications and decisions to get to that highly polished state of a truly great experience.
- Good product managers are pragmatic and clear communicators. The specs you write should be as simple as possible and no simpler. Knowing this line and staying on the right side of it is part of the art of product management. Your team needs to understand the intention of what should be created but you need to facilitate this understanding in the most efficient way possible. The level of communication required varies widely based on the experience of your team, whether you work together onsite or remotely, the backgrounds of individual team members, etc but as product manager you should have an instinctive understanding of what information your team needs from you right now.
- Good product managers have enough technical understanding of the product they are creating to know why some things are difficult to implement and why some things are easy to implement. Initially you will need help from your engineering team to understand the system you’re working on, but good product managers quickly internalize the basics and can have reasonably accurate guesses on time and effort required for changes. These guesses will need to be validated with your engineering team but should be directionally correct as your team is depending on you to make the calls as to whether a particular feature or change is worth the time required to implement it. Good product managers can also think about their product from an engineering perspective and understand how the thing they’re specifying fits into the existing patterns, database structures, etc that already exist in the product.
- Good product managers have great relationships with their engineering teams. Product managers typically have very few direct reports but have to work with many members of the team to get something successfully released. This means they can’t depend on authority to get things done – product managers must cultivate a strong feeling of collaboration and team work, so that when you ask someone to put in that extra effort to get the release out the door, they’re willing to do it because they know you would do the same for them.
- Good product managers maintain strong ownership and leadership of the build/release/get feedback/iterate process. In practice this means that a good product manager puts feedback systems in place (both quantitive and qualitative), actively monitors those systems and uses those signals to inform future decisions, and is adaptable and willing to quickly change thinking/approach when data indicates the reality is contrary to a hypothesis.
- Good product managers have good taste. A good product manager will strive to get the product out the door as quickly as possible, but knows when something just isn’t ready for prime time and will be the one to say so. Good product managers are keepers of a great user experience.
- Good product managers think of engineering bandwidth as the single most valuable resource on the planet. They should seek to refine the product development process so that the engineering team has everything they need to build the product as efficiently as possible. This means that required documentation is done in advance, concepts are validated with prototypes or other low-impact tests prior to investing time in full builds, the real data and assets needed are prepared prior to the dev team needing them. You won’t always achieve this level of preparedness, especially if working in an agile process, but the bar should remain high.
Finally, a less specific but important point: good product managers are prepared to do whatever is needed to release a quality product. Most of the time this means doing a great job with the above points, but at times you need to do things that may not exactly fall within your responsibilities. Do you think there’s a need for one final usability test before release? You should be willing to find the participants yourself. Is the engineering team close but not quite there on the current release? You should be willing to go buy pizza to keep them going or tell them all to go home and get some sleep if you think it’s better for the team and the product. Is the QA team having trouble tracking down a particular display bug that’s blocking release? You should be scanning the site with Firebug and trying to find the buggy CSS selector yourself. Good product managers are ready to get their hands dirty with what whatever needs to happen to move the product forward.






