The P&L Trap: When Product Managers Become Accountants Who Can't Sign Cheques

PMs are increasingly expected to own revenue without owning any of the levers that actually drive it. This is not a career evolution. It's a responsibility trap dressed up as empowerment.

Photo by Carla Quario on Unsplash

I sat in a quarterly review last month where a PM was grilled for twenty minutes about why revenue was flat. Not product metrics. Not user behaviour. Not adoption curves. Revenue.

She didn’t set the pricing. She didn’t control the sales team’s targets. She didn’t approve the marketing spend. She couldn’t hire engineers to ship faster. But she was accountable for the number on a spreadsheet that resulted from all those things she couldn’t touch.

This is happening everywhere now. And I think we need to talk about how broken it is.

The accountability without authority problem

Here’s the pattern I keep watching unfold. Company decides PMs should be “more business-oriented.” Leadership reads a blog post about product-led growth or sees a job description from Stripe. Suddenly PMs are expected to own P&L, build financial forecasts, set pricing strategy, and project revenue with the confidence of someone who actually controls any of those variables.

Except they don’t control them. Sales has their own targets and incentives. Marketing allocates budget based on their own priorities. Finance sets pricing constraints. Engineering capacity is negotiated, not granted. The PM sits in the middle of this, responsible for an outcome that emerges from a system they can influence but never direct.

“Ownership without authority isn’t empowerment. It’s a setup.”

I’ve seen this movie three times at different companies. It ends the same way. The PM either burns out trying to control the uncontrollable, or learns to play a sophisticated blame-deflection game that helps no one. Neither outcome makes the product better.

Revenue is a trailing indicator of doing the right things

This is the part that keeps getting lost. Revenue doesn’t come from focusing on revenue. Revenue comes from solving real problems for users in ways they’ll pay for. It comes from reducing friction in activation. It comes from building features that increase retention. It comes from finding the pricing model that aligns value delivered with value captured.

These are product problems. They involve understanding user behaviour, running experiments, making bets, learning from failures. They require patience and iteration and occasionally accepting that the thing you built isn’t working.

None of that maps cleanly to a quarterly revenue forecast.

When you make PMs accountable for revenue directly, you create an incentive to optimise for revenue directly. Which sounds sensible until you watch what happens. Dark patterns in onboarding. Aggressive upsells that damage trust. Features built for the pricing page rather than for users. Short-term wins that erode the foundation you’re standing on.

I worked with a team once that hit their revenue targets for six straight quarters while their NPS cratered. They were technically succeeding while systematically destroying the product’s future. The metrics said growth. The users said goodbye.

The cancer cell problem

There’s a quote I keep coming back to. “Growth for the sake of growth is the ideology of the cancer cell.” I think about this every time someone asks a PM to justify a product decision purely in revenue terms.

Not everything valuable shows up in this quarter’s numbers. Some things matter because they build trust. Because they reduce support load. Because they make the product more resilient. Because they create optionality for future directions you can’t predict yet.

Technical debt reduction doesn’t have a revenue line item. Neither does accessibility work. Neither does the refactor that makes the codebase maintainable for the next five years. These are investments in sustainability, and they’re invisible to a P&L mindset.

“The best product decisions often look like bad business decisions in the quarter you make them.”

When PMs are forced to justify everything through revenue, this kind of work becomes impossible to prioritise. You get a product that’s optimised for extraction rather than value creation. That works until it doesn’t.

What PMs should actually own

Here’s where I land on this, and I’ll admit I’m still working it out.

PMs should own outcomes. Specific, measurable, user-centric outcomes. Activation rates. Retention curves. Task completion. Time to value. The metrics that indicate whether the product is actually solving the problem it claims to solve.

Revenue is downstream of these things. If you’re moving the right outcome metrics, revenue follows. If you’re not, no amount of financial forecasting will save you.

This means PMs need to be skilled at identifying which metrics actually correlate with revenue. That’s a real capability, and it’s undervalued. The PM who can say “if we improve day-7 retention by 5%, here’s what that means for LTV” is doing more valuable financial work than the PM who’s building spreadsheets full of projections they can’t actually influence.

But it also means PMs need permission to focus on those leading indicators rather than being held directly accountable for the trailing ones. That requires leadership to understand the difference. Which, increasingly, they don’t seem to.

The resourcing gap nobody mentions

There’s another dimension to this that gets conveniently ignored. If you want PMs to own revenue, they need resources to influence it. Headcount. Budget. Authority to make pricing changes. Access to sales and marketing data. The ability to run experiments without six layers of approval.

Most PMs have none of this. They’re expected to own revenue while requesting permission to change a button colour.

I talked to a PM last week who’s accountable for a £2M revenue target. She has three engineers, shared with another product. She can’t adjust pricing without a six-week legal review. She can’t see the sales pipeline. She can’t influence marketing spend.

What exactly is she supposed to do? Will really hard?

The question I keep asking

If PMs are going to own revenue, then give them the actual authority to influence it. Let them set prices. Let them control budget. Let them hire. Let them fire. Make them mini-GMs with real power.

But if that’s not on the table, and it usually isn’t, then stop pretending that putting revenue on their OKRs is anything other than accountability theatre. It’s a way for leadership to distribute responsibility without distributing power. It protects executives when numbers are missed. It does nothing else.

I don’t know how to fix this systemically. The trend seems entrenched. The job descriptions keep demanding P&L experience. The interview questions keep focusing on revenue impact.

Maybe the answer is for PMs to get better at pushing back. At articulating why outcome ownership is more valuable than revenue ownership. At making the case for leading indicators over trailing ones.

Or maybe the answer is that the role is being redefined into something it was never meant to be, and those of us who care about products need to find a different title.

I’m not sure yet. But I know the current setup isn’t working. The PMs I talk to are exhausted, playing a game where the rules keep changing and the scorecard measures things they can’t control.

That’s not product management. That’s organisational theatre with extra spreadsheets.