I’ve had this blog post in my head for a couple weeks now. I’ve been thinking about how to lay out a strong case for what I momentarily thought was a controversial topic. I figured the post would be long and go to great lengths to help readers come to the conclusion that I have.

But guess what? None of that is needed. there is such an easy answer to the question: “Should the head of Product Need to Be the Best Product Manager on the Team?”

No.

So why did I go on this journey? It was a moment of weakness that I don’t mind admitting to. Recently, I’ve had a bunch of great conversations with founders preparing to hire their first head of Product (VP, CPO, HoP). To my surprise, more than one has directly said or strongly implied that they expect their new Product leader to be “the best Product Manager on the team.”

In every leadership role I’ve been in, I’ve had at least one team member that I believe to be a better PM than I ever have been, and I have always seen that as a good thing. At the same time, I also believed myself to be the best and most capable of leading the functions I was responsible for. I guess these chats with talented CEOs made me start to doubt myself and I began pondering this question, assessing my own skills and abilities.

I don’t believe that anyone expects a CTO to be the best software developer on an engineering team. We don’t expect the CMO to be the best visual designer on the creative team. Why would we expect the CPO to be the best Product Manager on the team?

This may be cliche, but I used a sports analogy to help me put this question to rest: Steve Kerr, the Head Coach of the Golden State Warriors NBA team was not the best basketball player on any of his teams when he was a championship winning player (not even close). Yet, today he is recognized as one of the best coaches in the NBA over the past 10 years. Kerr will one day be inducted into the NBA Hall of Fame, and it will be because of his coaching career, not his playing career. He is a talented and effective leader of players that are all better than he was.

Conversely, LeBron James can arguably play all 5 basketball positions at a high level, and he is considered by many to be the best basketball player of all-time, but we have no idea if he’d be a good coach. In fact, he probably wouldn’t be. If you look at ESPN’s top 40 NBA players of all time, you’ll only find three that have had some notable success as a coach, and not a single one even close to being one of the best coaches in any given year, let alone the history of the NBA.

Why is this? The job is totally different! The skills needed to be a top tier coach are completely different from the skills needed to be a top tier team member.

If Steve Kerr thought that he was the best player, and didn’t try to “hire” players better than him, I suspect that the Golden State Warriors wouldn’t have any of their four championship titles in the last nine years, and Kerr would have been fired long ago.

Just as the jobs are different in sports, the jobs are also different in software product management. A highly talented head of Product is focused on building and up-skilling the best team they can assemble. They create an environment and playbook that allows each team member to be their best and play the role the team needs them. They are the expert when it comes to the customer and the competitors. The head of Product connects the organization’s goals to execution in the area by setting, owning, and championing a strategy to build the right products, for the right market, with the right investment, at the right time.

If you haven’t been a Product Manager, it will be much harder to be great at the things a head of Product needs to do. You don’t need to have been the best PM, but you better know the job inside and out, have witnessed it done well, and have recognized when it was done poorly (even if that was you).

That brings us to what I believe the head of Product does need to be the best at:

Setting vision & strategy: As a member of the company’s senior leadership group, you play a pivotal role in setting and guiding company vision, while owning a product strategy that guides the organization towards achieving that vision. Good strategy considers current customer needs, where the market is headed next, and what the company’s long term vision is. All packaged so that it is clear to all what the priorities are, why, and how we’ll act in order to reach defined goals.
Recognizing trends and opportunities: Product Managers and Engineers focus heavily on shipping products to satisfy a problem that exists today. While PMs are not exempt from seeing and planning for the future, I expect the head of Product to be the first to see where the market is going, to spot emerging trends, to find hidden opportunities, and then decide when and how much to invest today for big rewards tomorrow. Product leaders do this by being out in the market with customers (literally and figuratively), building user empathy, becoming a trusted advisor, and acting as a continuous student of the industry. The right team, in the right positions, with the right playcalling is a multiplying force that exceeds anything that a head of Product could ever be on their own.
Recruiting & nurturing talent: Product orgs operate at their best when they have the right people, in the right position, with the right coaching. It's not just about finding the best fit, it's also about convincing them to join the journey, coaching them to be their best, while fostering interest and excitement in the work. It’s not just about having the right people with the right skills, the head of Product needs to foster an environment and process that invites partnership from engineering through the Product Manager’s effective communication around the “what,” “why,” and “when” of their priorities.
Facilitating cross-team collaboration: Great product doesn’t mean much if it can’t be effectively marketed, sold, and supported. Engineering isn’t the only team that product managers must work well with. An effective product leader makes sure their team does not work in isolation. They expect their product managers to influence Marketing, Sales, Support, and other functions by partnering with the leaders of these functions and to set an example of collaboration and paving the way for two-way relationships that benefit customers and the business.
Communicating well: Absolutely everything in this list is dependent on being a fantastic communicator. I often say that product leaders really only do three deceivingly simple things: They listen (to customers, data, colleagues, etc), they think (about priorities, investment levels, timing, visions, strategy, etc), and they communicate (to win support, create understanding, set goals, etc). Being an effective communicator means winning support for strategy because it is clear, relatable, and powerful. Being a great communicator means selling the org on taking the right risks, at the right time. Being a stellar communicator means getting the best talent to jump in the boat with you and give it their all. A mastery of communication results in strong ties to customers where trust leads to openness and partnership.

Curious to see my thoughts on other aspects of Product Management? See those posts here. To see the conversations on this topic from the r/productmanagement Reddit sub, head over here.