Ownership without authority: Why product managers keep failing in the same way

In football, the manager picks the tactics. Formation. Style of play. Who starts and who sits on the bench. That is the theory. But in most clubs, the manager does not pick the team. Not really. The transfers are decided by a director of football in a different building, working from a different set of priorities, often with a different timeline. The manager gets the players they get. They build a system from whatever arrives. And then they are judged, entirely and publicly, on match results.

When the results are poor, the manager gets sacked. The director of football stays.

If you have spent any time in product management, you recognise this arrangement immediately.

The accountability fiction

Product managers are told they own the product. It is in the job description. It is in the interview. It is repeated in onboarding, in all-hands meetings, in blog posts written by executives at companies that have never actually given a PM real authority over anything consequential. Own the roadmap. Own the outcomes. Own the customer experience.

But ownership implies control. And most PMs control almost nothing.

They do not control engineering allocation. That is decided by an engineering lead or a VP of Engineering based on technical priorities, hiring constraints, and relationships with other parts of the organisation. They do not control design bandwidth. Designers report to a design lead who has their own roadmap, their own capacity problems, and their own opinion about what matters. They do not control sales behaviour. Sales teams sell what closes deals, including features that do not exist and timelines that no one in product has agreed to.

The PM owns the outcome. The PM controls none of the inputs.

I call this the authority gap. The distance between what a PM is accountable for and what a PM can actually decide. In most organisations, that gap is enormous. And it is the single most reliable predictor of PM burnout, PM failure, and PM attrition.

At Adobe, I watched a product manager do everything right. Her PRDs were meticulous. Her user research was thorough. Her prioritisation was sharp and well-reasoned. She had identified a feature that users had been requesting for over a year, validated the business case, and built a clear plan for delivery.

But the engineering lead had a different roadmap. His priorities were infrastructure and technical debt, both legitimate. He was measured on system reliability, not feature delivery. So her feature kept getting pushed. Quarter after quarter, it slipped. The stakeholders asked her why it had not shipped. She could not say "because engineering chose not to build it" without creating a political problem. So she absorbed the accountability. She smiled in the status meetings. She adjusted the timeline.

She quit within a year. Not because she was bad at her job. Because her job, as it was structurally designed, was impossible to do well.

The inputs you do not control

The Adobe story is not unusual. It is the default. I have seen the same pattern at five different organisations, and the specific details change while the structure stays identical.

At Freshworks, I watched a talented PM present a quarterly plan to leadership. It was a good plan. Thoughtful. Grounded in data. Clear on outcomes and success metrics. But I kept counting the dependencies. Engineering allocation: not his decision. Design bandwidth: not his decision. A commitment from sales to stop pre-selling features that did not exist: very much not his decision.

His plan depended entirely on decisions made by people who were not in the room, who had not been consulted, and who had their own priorities. He owned the outcome. He controlled none of the inputs. And every person sitting in that meeting knew it, including him.

Nobody said anything.

That silence is the sound of the accountability fiction being maintained by mutual agreement. Everyone in the room understood that the plan was structurally dependent on cooperation that had not been secured. But naming it would have required someone to ask uncomfortable questions about how authority was actually distributed. And in most organisations, authority distribution is the conversation nobody wants to have.

Ownership without authority is the most common lie organisations tell their product people. It is not always intentional. Sometimes it is org charts designed without thinking about decision rights. Sometimes it is inherited from a structure nobody updated. But the effect is the same. Someone is told they own something, works hard, plans carefully, and then discovers the plan depends on decisions they cannot make.

Why talented PMs keep leaving

The pattern is consistent enough that I have stopped being surprised by it. A PM joins with energy and capability. They are told they own the product. They build relationships, do the research, write the strategy. And then they hit the authority gap.

Some PMs respond by becoming politicians. They spend more time influencing sideways and upward than they spend on the product. This works for a while. But it is exhausting, and it turns the role into something that is no longer about product work. It is about organisational manoeuvring.

Some PMs respond by becoming order takers. They stop proposing their own roadmap and start asking leadership what they want built. This is safe. It is also the death of the product function, because an order-taking PM is just a project manager with a more expensive job title.

And some PMs, the good ones, leave. They leave not because they cannot do the job but because the job, as designed, will not let them do what they were hired to do. The accountability fiction pushes out exactly the people organisations most need to keep.

I have mentored enough junior PMs to see this cycle repeat. The ones with the most product instinct are the ones most frustrated by the authority gap, because they can see what needs to happen and they cannot make it happen. The ones who stay longest are often the ones who have learned to manage expectations down rather than push decisions up. They survive. But survival is not the same as impact.

What honest organisations do differently

The authority gap is not a management failure. It is a design flaw. It exists because organisations assign accountability without assigning the corresponding decision rights. The fix is not motivational. It is structural.

The few teams I have seen get this right did something specific. They defined, in writing, what the PM could decide without approval, what required consultation, and what required escalation. Not as a philosophical statement about giving people permission (which usually means giving them nothing). As a practical document that everyone in the cross-functional team had read and agreed to.

But most organisations will not do this. Because writing down decision rights forces you to confront who actually has power. And in most organisations, the gap between who is supposed to have power and who actually does is something everyone can feel but nobody wants to document.

The football manager who cannot pick the team learns to work with what they have. Some become great at it. But the best managers eventually go to clubs where they have authority over the squad. They go where the structure matches the accountability.

Product managers do the same thing. They leave for organisations where ownership means something. And the organisations they leave behind wonder why they cannot retain good PMs, without ever examining whether the role they designed was one a good PM could succeed in.

The question is not whether your PMs are talented enough. It is whether you have built a structure that lets talent matter.