The Product Manager Is Not the CEO. That Analogy Has Damaged the Craft for Two Decades.

The product manager, we have been told for two decades, is the CEO of the product. It appears in onboarding decks, conference keynotes, and LinkedIn posts with the confidence of something tested and found true. It has not been. It is a flattering fiction that sets up every PM who believes it for a specific and recurring disappointment, and it has quietly done more damage to the craft than any org restructure or layoff ever could.

A CEO has authority. A PM has influence. A CEO hires and fires. A PM persuades and earns trust from people who do not report to them. A CEO is accountable to a board. A PM is accountable upward, downward, and sideways simultaneously, usually without formal power over any of the people or processes they are responsible for shaping. The confusion this generates is not a character flaw in the PM. It is a category error installed at the point of hiring, and organizations pay for it in quiet, cumulative ways they rarely trace back to the source.

I want to offer a replacement. Not a rebrand. An honest map of what a great PM actually is, what it costs when organizations do not know how to read one, and what the companies that have gotten this right have in common.

The right analogy

Think about a music album. Not a playlist, not a collection of singles. The album as a single coherent artistic statement. Someone is in that room who is not playing an instrument, not engineering the sound, not managing the tour logistics. They are listening to whether the second track lands right after the first. They are asking whether the closer is earning its place. Their job is the whole record, not any single part of it, and they have the standing to say, before anyone else does: this is not right yet.

That is the creative director. And that, when an organization genuinely understands what it has hired, is the product manager.

The orchestra conductor analogy, which has become the fashionable replacement for the CEO myth, is still not right. A conductor coordinates. A conductor executes someone else's composition. The creative director does something more specific and more valuable: they hold creative custody of the whole. They are the person who knows, before a single note is recorded, whether the album will feel like one thing or like a committee made it.

"You cannot lock the creative director out of pre-production and then ask them why the film does not have a point of view."

One important clarification before going further: not every PM is capable of this. Many are administrators with product titles. Many create process where they should be creating clarity. Many confuse coordination with strategy and survive for years doing so without anyone naming it. The argument here is not that every PM deserves a seat at the strategy table. The argument is that organizations consistently fail to distinguish between a structurally weakened PM function and a genuinely weak PM, and they pay for that failure in the coherence of their products.

The driver and the passenger

Before naming what needs to change, it is worth being precise about why the gap between leadership vision and PM execution exists in the first place. Because in most organizations, it is not a power problem. It is structural.

Consider a car. The driver knows a speed bump is coming. They have been watching the road. They adjust their grip, ease off the accelerator, brace without thinking. The passenger in the back seat has none of this. The same bump that is a minor adjustment for the driver is a jolt that arrives from nowhere for everyone sitting behind them.

This is the founder and the product team in most early-stage companies. The founder is not withholding. They are simply operating from a vantage point that is structurally unavailable to everyone else in the vehicle. They are in board meetings absorbing things that cannot yet be shared. They are watching the road for what is coming. The team is not failing to pay attention. They are sitting in the wrong seat.

The PM's job, understood correctly, is to be the translation layer between that vantage point and the people building the product. Not to invent the vision. To carry it down the chain with enough fidelity and enough lead time that the people below can brace for what is coming instead of being thrown by it. This is quiet, invisible work. It shows up six months later in a product that moves in one direction rather than several. Nobody marks the date when it happens. Nobody throws a party when a disaster is avoided.

Which is precisely why it gets undervalued. When a server goes down, the engineer who fixes it is a hero by end of day. When a PM holds the coherence of a product steady across six months of competing priorities, the payoff is a product that feels like one thing rather than a committee's compromise. Prevention leaves no artifact. Coherence is invisible until it is gone.

The three restrictions that break the instrument

The damage to product organizations rarely happens in one dramatic decision. It accumulates through three restrictions that compound on each other until the person holding the role is no longer capable of doing what the role was designed for.

The first is exclusion from the strategy stage. The PM is brought in at execution, handed a decision already made, and asked to deliver it brilliantly. The problem is not that execution is beneath them. The problem is that their most valuable contribution, the ability to see the whole picture and identify where the plan breaks down before a single line of code is written, is only useful before the commitment is made. By the time they are in the room, the window has closed. The organization has hired a creative director and asked them to show up for the edit.

The second is the absence of everyday transparency. Not the dramatic kind that belongs in a board deck. The operational kind: the reasoning behind a priority call, the honest context for why this quarter looks different from the last, the strategic anxiety the leadership is managing that explains the sudden change in direction. Without that context, the PM cannot translate faithfully. They fill the gap with their best interpretation, and that interpretation travels downward through the organization as if it were fact, compounding at every level until the junior engineer is building something that is three translations removed from the original intent.

The third is being measured only on shipping, never on thinking. When the only visible output is a closed sprint or a launched feature, the PM learns, correctly, that the thinking is not valued. So they stop doing it visibly. They stop asking the uncomfortable question in the product review about whether this feature belongs in the product at all. They optimize for the metric they are being measured on. Slowly and quietly the album stops being an album and becomes a playlist. Nobody called a meeting to make that happen. It happened because the wrong things were being counted.

What the companies that got this right actually did

The most cited thinker in product management, Marty Cagan, has spent years making a version of this argument in the language of organizational design. His framing is precise: good leaders give teams strategic problems to solve, not requirements to build. The distinction sounds small. It is enormous. A team handed requirements is a delivery function. A team handed a strategic problem is a creative function. The PM at the center of a delivery function is a coordinator. The PM at the center of a creative function is a creative director. Most organizations say they want the second and build the conditions for the first.

At Netflix, Gibson Biddle ran a product organization on a principle that encoded this understanding directly: the PM's job is to delight customers in hard-to-copy, margin-enhancing ways. The phrase hard-to-copy is doing significant work in that sentence. It is not a feature specification. It is a creative brief. It assumes the PM is thinking at the level of the whole product over time, not the next sprint. More importantly, Netflix's quarterly meetings were not just strategy reviews. They were, by Biddle's own account, exercises in building judgment. The culture was about helping individuals make great decisions about products independently, without the suffocating process that accumulates when organizations do not trust their people to think. The PM was not a coordinator inside that culture. They were a judgment-holder.

The Airbnb case is the most instructive precisely because it is the most misread. When Brian Chesky announced at Figma's Config 2023 that Airbnb had moved away from traditional product management, the product community treated it as a threat. What Chesky actually said was more specific: product managers should not be doing the job of a designer. During the pandemic he had shortened Airbnb's release cycle dramatically, releasing only 80 percent of the product twice a year, and had pulled most product decisions back to himself. What he eliminated was not the PM function. He eliminated the version of it that had drifted furthest from creative custody: the PM who had become a middleman between designers and engineers without holding any coherent vision of their own. He was, in his own way, making the creative director argument. Protect the role from dilution or it stops being the role.

Apple's PM philosophy, shaped in the image of Steve Jobs who never carried the title but embodied the function more completely than anyone in the industry's history, frames the role as editor-owner-storyteller: someone working at the intersection of what is technically possible and what is humanly meaningful, translating between engineers who think in systems and customers who think in experiences. Editor. Not executor. The edit is a creative act. It requires having held the vision of the whole long enough to know what does not belong in it.

Creative people cannot be managed like everyone else

Most PMs did not arrive at this role accidentally. They were drawn to it because it was the one place in a company where they could touch everything at once. Engineering, design, strategy, customer behavior, business logic, all in the same week. The role was built for people who were too curious to stay in one discipline, too design-aware to be pure engineers, too technical to be pure designers, too operational to be pure strategists.

That capacity for synthesis, for holding the whole picture without losing the details, is the same gift that makes a great creative director, a great editor, a great consultant. People from consulting backgrounds often develop it through training. PMs carry it more organically, because they have lived inside the product rather than parachuting in to assess it. The difference is that the consultant leaves. The PM stays and builds on what they understand. That continuity is worth something. Most organizations do not know how to protect it.

Creative people break under the kind of management that works perfectly well on everyone else. A deadline-driven, output-measured, visibility-obsessed management culture is right for a great many roles. For someone whose primary contribution is coherence and synthesis, that same culture is like asking a composer to clock in and clock out. The instrument stops working. Not because the person is difficult. Because the conditions destroyed the thing that made them useful.

The Glassdoor reviews accumulating across Indian product organizations are not a mystery. They are a symptom. The complaints about lack of clarity from leadership are not really about information. They are about creative suffocation dressed up in professional language. That is what it feels like to be the right instrument in the wrong hands.

Three things that need to change, and the contract that goes with them

Bring PMs into the strategy stage, not just the execution stage. This is the most specific and most violated of the three. If the direction has already been decided before the PM is in the room, the organization has not involved a creative director. It has hired a coordinator and given them a better title. The PM's most valuable contribution is exactly the question they ask before the commitment is made: is this the right thing to build, does it make the whole product better or just add another feature, does the second track land right after the first. That question is worthless after the decision. It is everything before it.

Give PMs a meaningful degree of transparency. The operational kind: the reasoning behind priority calls, the strategic context that explains why this quarter looks different, the honest answer to what leadership is worried about. The PM who understands the why can carry the vision faithfully. The PM handed the what without the why will fill the gap with interpretation, and that interpretation will travel downward through the organization compounding at every level.

Measure PMs on thinking, not just on shipping. Create the conditions for the uncomfortable question. Notice when the product feels coherent and ask why. The answer, almost always, is that someone was listening to the whole thing and had the standing to say when something was off. That work deserves to be seen.

But the contract runs both ways. A PM given strategic involvement, real transparency, and the standing to be heard owes the organization their complete creative commitment. The creative director who is finally let into the studio has no excuse for a bad album. Reciprocity is not optional. It is the foundation of the whole arrangement.

Product management is one of the most interesting and least understood crafts in any organization. The person who can hold the complete picture of what is being built, translate it faithfully across every level of the team, and say with conviction when something is not right yet, is not a luxury. They are the difference between a product that works and a product that merely functions.

The organizations that know how to use that person produce things that feel genuinely considered. The organizations that do not keep wondering why their products feel like committees made them.

They did. That is exactly what happened. And it will keep happening until someone in the building is given the strategic problems to solve, the context to solve them with, and the standing to say: this is not right yet.

That is the PM's job. It has always been the PM's job. We just keep giving them a different one.