The most important skill for a product manager is empathy.
It’s a bold statement to make. Succeeding as a product manager requires mastery of a diverse skills set, encompassing data analysis, communication, psychology, research, prioritization, UX, marketing, software development… the list is endless. Ultimately, most of these traits trace back to a base requirement of empathy. Empathy is the capacity to recognize and understand the emotions being expressed by others, and is core to a product manager’s job of representing the customer within the company.
Because the product manager role is a hub function (as I explain in this post), you are constantly mediating between different viewpoints, weighing the opinions of various stakeholders and forging compromises between them to champion a clear and effective path forward for the product. Understanding the underlying motivations of each stakeholder in order to cut through to the real pain points requires empathy. You must also successfully represent the customer’s needs, who is never present during internal decision-making, but is arguably the most essential stakeholder.
The product manager is responsible for knowing the customer like the back of their hand — their frustrations, their daily thoughts, the context in which they use the product, and their needs.
It is Product’s understanding of the customer that produces value for the company, and a company that doesn’t understand who it’s selling to is bound to fail.
From the high-level tasks of prioritizing a product roadmap to the day-to-day of writing requirements, knowing how a customer will use your product and what he/she hopes to gain from it is the key to success. While there are many tasks a PM is responsible for, your biggest contribution to the company is a deep understanding of the customer — which you must use to guide a development team.
It’s simple — get away from your computer and start talking to stakeholders and customers. Steve Blank coined the now-famous phrase “There are no facts inside your building,” and the way to start understanding customer pain points and willingness-to-pay for what you’re building is to ask open-ended questions and understand the context around the user problem you’re trying to solve as well as their usage of your product. Kissmetrics has a good list of resources to get you started.
Even though a product manager has many different responsibilities inside an organization, the biggest value you add is an understanding of the customer that informs the direction of product development. It’s a forward-facing role with a lot of uncertainty, but you can mitigate much of it by simply knowing and empathizing with your customers.
Liked this post? Read my other one on why PM roles differ across companies.