6 Ways The Product Manager is the CEO of the Product (and 1 Way They are the CFO too)
The comparison has been around for a long time – the product manager is the CEO of their product. It’s become ingrained in our thinking and the way we talk about product management. For newcomers, it’s an exciting concept. Everyone wants to be the CEO, right? Make decisions. Create vision. Command respect.
But is it true? Is the product manager the CEO?
The short answer: it depends.
The product manager isn't an executive. She doesn't have final authority. She can't hire and fire people. She can't determine the budget and pull resources in most cases. In short, she isn't really the CEO in that way.
But you say above that the product manager is the CEO. What gives?
Many characteristics of a good CEO should be emulated by product managers. Ownership, leadership, drive, ambition, etc. So here is how the product manager really is the CEO of their product.
Chief Empathizing Officer
One of the most crucial characteristics of a good product manager is empathy. Empathy for users of our products. Empathy for our stakeholders. And empathy for anyone impacted by our work. With that, the first role of a product manager is to be the chief empathizer.
When I first came into my current role in developing a new application for university students and faculty, I knew I had to get a much deeper understanding of all our users. So I started doing frequent interviews. I would watch as they did their work. I would ask questions. I would then take what they were doing and do it myself, going through the whole process. Only after all of this was I able to really understand the pain points these users had. Some of the pain they didn't even realize. The pain had been around for so long that it had simply become "the process". Those were the things that I knew we could solve. The things users didn't even realize were terrible because they had always been terrible.
A product manager has to be able to understand the users and customers of their product. The product manager needs to really internalize the user experience and be their advocate throughout the product development process. Of course, this doesn't absolve the rest of the team or business from having empathy for users, but I'd argue that no one should embody that role more than the product manager.
Chief Experience Officer
I know this is an actual title in some places, which is excellent. Along the same lines as empathizing with users, the experience of the user should be first and foremost on our minds as product managers. We aren't simply designing tools or applications or software, but are ultimately creating experiences. No piece of software is used in isolation. No application is used without some context. We as product managers need to understand that context and understand the experience.
There is an excellent story about this over on the Inside Intercom blog. James Buckhouse does a masterful job in audio storytelling. It's short, so I'd encourage you to give it a listen. It's about truly capturing the human experience. And while geared toward designers, I'd say just as true for product managers. We have to own the experience, which means going beyond the pixels.
Chief Editing Officer
The product manager is the chief editor. If we look at an editor's role in writing, he is meant to be a gatekeeper between an author and an audience. To ensure that the message being conveyed is clear and concise. The best editors are often a bit harsh, forcing writers to think about their audience and shorten things so that the point is clear and the flow is logical.
This is crucial for product managers. A good product manager should be constantly editing their product. Ensuring that the features are core to the strategy of the product and company, and not just a laundry list that customers or management have asked for. The product manager should also constantly be forcing the team and business to think about the audience - the users of the product.
It's about what to include and what not to include. One of my favorite examples of this is Google Docs. It is an application I've used for years and probably will continue to use for years. Many of you probably feel the same. It is not nearly as powerful or robust as Microsoft Word. And that is partly the point. It doesn't have to do everything. It is a simple, online word processor that can do 95% of what most users need. Sure, there is a place for Word and likely always will be, but for simplicity and functionality, you can't beat Docs.
Chief Evangelizing Officer
I love this one because it plays so well to most product managers I've seen. No one else is going to be an advocate for your product like you are. No matter how much we think our products may sell themselves, we can never stop evangelizing the benefits of our products.
I'd also take this a step further to say that the product manager generally needs to be a consistent communicator. That goes for both the good and bad. Evangelizing typically connotes positivity and bringing people to our side because of the benefits of something. But no product manager should look at their product with rose-colored glasses. There are trade-offs to be made. Honest discussion about those things is crucial. That doesn't mean we have to lose our positivity, but be realistic about the positives and negatives.
Marty Cagan shares a great story about Lea Hickman at Adobe as they transitioned their creative suite from a purchase model to a subscription model. It was a monumental change to the way Adobe built and released software, and to how customers used it. One of the keys to making the move was the evangelizing that Lea, the product manager, did throughout. To get an entire company to buy into a massive change is no small feat. And it involved trade-offs across the board. But ultimately was the right decision.
Chief Expert Officer
Another key role for product managers is to be an expert in their product. Any questions about the product should be readily handled by the product manager. But it goes beyond knowing the product inside and out. The product manager also must know how their product relates to the larger business, the strategy of the company, and the broader market. The product manager has to keep a pulse of the industry and trends, and be the local expert for their team and stakeholders.
In fine, the product manager needs to be an expert in the problem (or problems) they are solving. It goes back to empathy and experience. The problems that users are facing need to be deeply understood by the product manager, so that she can deliver the right solutions.
Chief Experiment Officer
In order to get to the right solutions for users, a product manager has to experiment. This means uncovering problems, asking questions, creating hypotheses, and then testing those hypotheses through experiments. (For a handy guide, check out this article).
Experimenting is a lot of hard work. But it is a crucial part of the process. Taking solutions and actually testing them out before implementing them across the board. It's a way to understand what is happening when you make changes and homing in on the right things.
A favorite example of experimenting and learning is the story of Dropbox. They were able to do experiments throughout their initial phases in order to learn what users wanted, and what they didn't want, in order to build the right features. Experimenting is key to product success.
Chief Facilitating Officer
And if it's not enough for a product manager to be a CEO, we'll add CFO to the title as well. Why not, right? In this case, however, we're really taking about being the facilitator.
Gone are the days when a product manager served as a proxy for the business or the customer, being the gate between them and the development team. At least those days should be gone. A key role for a product manager isn't to be the go-between, but to actually bring the product team together with business stakeholders and users and actually facilitate the learning and interaction that comes from it.
In my experience, bringing the developers into the conversation adds tremendous value. Rather than me simply taking the message back, the development team gets to actually hear from the users and see their pain. That has, on more than one occasion, turned the entire conversation.
So while a product manager may not be the full-on CEO of their product, there are many ways that they are the CEO. Through empathizing with users, owning the experience, editing and evangelizing the product, being the expert, experimenting, and facilitating learning and communication, they are the leader that is accountable for success or failure. And while no one should go into product management believing they are going to be the actual CEO of something, embodying the traits of great CEOs will lead to success.
And with that kind of experience, it's not surprising that many product managers eventually make great candidates to take on the executive role. So if you want to be a CEO, don't make the mistake of thinking that becoming a product manager makes you the CEO. But don't be surprised when you get to an executive role at some point in the future after being a great product manager.
Building a Backyard
Over the past two months, we've been relentlessly working on building our backyard. And as I got ready to post some finished photos of it, I realized that I should write a little bit about the journey as well, since it has been non-stop work for weeks.
So before we did anything else, we knew we needed to get some concrete poured. And if you're going to do, might as well do it right, you know? So we went all in for a new patio, a parking pad, and a shed pad. Basically just making the whole yard concrete, as a few people joked. And it turned out great. We still have big plans for this space, but more to come on that later.
Fortunately, I didn't have to do it alone. Grandpa was here to supervise and to help lay pipe. And the kids were out most evenings cheering us on as we moved as quickly as possible. (We gave ourselves a week to do all the sprinklers and get the grading done before the sod came, so it was quite the race).
In our old house, the sprinklers didn't reach all of yard, so we had to do a lot of watering by hand. We wanted very much to avoid that, so we put in a lot of sprinklers. Like, a lot. Enough that a few minutes per zone would be enough to keep the lawn nice and green. It is overkill without a doubt. But I'd rather have that than the alternative.
We also got a smart controller, which I can't recommend enough. Being able to test out zones from your smartphone is awesome. We'll be replacing our other controller soon so that we can control all sprinklers from our smartphones.
Part of the kids excitement was also due to the fact that they knew that once grass got put in, they were going to get a playset. We purchased a kit a few months ago and it's been sitting in the garage. And a couple times a week the kids have been asking why it hadn't been put together. "That silly daddy, he hasn't built our playset yet." That's what I've been living with for months now.
A few more evenings of work though, and we had it all done. And following a terrible tradition of doing outdoor projects on the 4th of July, we put down the rubber mulch after the parade.
And with that, the first phase of the backyard is just about done. The grass is in. The playset is built. We planted lilac bushes along the back for privacy. Next up, we'll be putting in a fence and doing some additional finishing touches along some of the side and back.
But at least we now have a usable, fun space for the kids.
Don't Rush the Putt
I was on the golf course a few weeks ago. It was pretty warm, but it was likely the last chance we'd have to go before the weather got really hot, so we took advantage of a cool morning to hit the links.
Now I'm not a great golfer, so this isn't going to be a post describing best practices when it comes to golf. I tend to be all over the place for most of the time. But one area where I am pretty consistent is on the green. When it comes to putting, I may not be sinking 50 foot birdies, but I do tend hit generally good putts. The right distance. The right line. They don't always go in, but they tend to get me pretty close.
My key to that has always been taking my putts really slowly. I think about them. I visualize them in my head. When I get up next to the ball, I don't just hit it. I stand over it, gauging my swing and the green and all the other variables that go with putting. I go really slowly. It sometimes drives people a little crazy. But I don't care. I take my time and hit my putt.
How often are we rushing our putts?
All the time? It kind of feels like it.
As I contemplated a typical day at work, it generally consists of rushing from one meeting to the next. Rushing to get emails sent out. Rushing to gather information. Rushing to have quick conversations with folks to check in on things.
Everything is a rush.
I get it. Everyone is busy. We have lots to do. We have tons of things to cover in our meetings. We have so many responsibilities that we have to rush from one task to the next in order to make sure nothing is falling through the cracks.
But it's not just work. How often do we rush to get to work, or get home from work, or get to the store? We rush to have dinner in order to make it to evening activities, which can also be a flurry as we rush through them so we can get home in time for bed.
But how much are we missing as we rush?
I'd estimate that we're losing some of the most important details in our rush to get things done. This is happening to each of us individually as well as our teams and families and friends.
At work, I've noticed this in countless meetings I've been in lately. We have a packed agenda that we need to get through so we plow through as quickly as we can. There isn't time for a ton of conversation because we have items we need to get through. And if discussion starts to happen, it is generally shut down after a very short time as something that is better "taken offline."
And it isn't just other people. It is all of us. It is me. I don't think I could keep track of the number of days that I rush from one thing to the next, only to reach the end of a blurred day to wonder what had happened.
The cost of this kind of rushing is high. Recently another product manager and I realized that our teams had been working independently on very similar projects. Now there is certainly something to be said for process, coordination, and all of that. But I can't help but wonder if, as product managers, we had slowed down just a little and had some conversations in the various meetings we're in. Rather than sticking so tightly to agendas, what if we had just talked about things we had in the works. Would we have realized this sooner? I believe so.
And what about the cost to our families?
Are we missing the most important moments? When our son was born, I was working 70-80 hours per week. That continued for a time after that. I was constantly in motion, running as fast as I could to get ahead. It was pure chance I was home one evening around 5pm (early for me at the time), and was able to actually witness him taking his first steps. It caused me serious pause. What other moments was I missing out on in my rush?
And finally, what is the cost to ourselves?
How long can we keep moving at 100 miles per hour, rushing through life before it begins to take its toll? Another shot of caffeine to keep us moving. Not enough time for a decent meal, so we eat whatever is quick and easy. Not enough time to properly plan for our futures, so we have to take whatever comes because we don't have time to prepare.
So how can we slow things down?
I will be posting more about this soon, but I've started to block out time each day to slow down. To actually think. To work on important tasks that tend to get lost in the rush of everything else we have going on.
We can also start to take time in all of our meetings and interactions for actual discussion. Maybe even begin to plan for meetings that are just about discussion. I've been in meetings like this and found them to be the absolute most productive meetings I've participated in. No agenda, no bullet points to get through. Just discussion.
As we allow ourselves the necessary time to slow down, I think we'll find that we're able to get more done. More of the important things. We won't waste so much time being pulled in different directions. We'll be able to focus on thing things that are important.
I've started to find that as I try not to rush my putts at work, I'm actually getting much closer to the hole than I was before. I'm able to size up what I need to do and then execute better than ever before.
So take a minute, take a breath. Don't rush your putts.
My personal musings on a variety of topics.