Product Managers Rate Themselves Lowest on the Calls Their Bosses Get Paid to Make

Product managers rate themselves strongest on daily work and weakest on commercial judgment. Why that gap persists, and what it means for founders.

Matthew Stublefield

6 min read

Workflow diagram, product brief, and user goals are shown

Ask 5,906 product managers to rate their own skills and a pattern shows up fast. In the words of the company that asked them: "PMs rate themselves highly on the work they do every day, and lowest on the commercial calls their bosses get paid to make."

That company is Productside, which trains product managers, and this is the fourth edition of its skills benchmark, covering PMs across 24 industries.

That's from the announcement of the 2026 PM Skills Benchmark Report, published in mid-October. It also found that 60% of product managers now use AI every day, and that when asked to tie that AI use to business value, their confidence dropped to its lowest point on the whole AI scorecard.

I don't read this as a criticism of product managers. I read it as a description of how most product organizations are built, and it has a direct consequence for any founder who's counting on the product team to answer a hard direction question.

Which skills trail, and why

Productside published more detail from the previous edition of the same benchmark, covering more than 5,700 PMs. The areas where PMs fell furthest below the benchmark were pricing, competitive analysis, and end-of-life planning – deciding when to retire a product and how. Those, Productside wrote, are "the exact skills that separate a PM from a Director," and they're "hardest to develop purely on the job, because most organizations don't give PMs structured exposure to them."

The AI data follows the same shape. In Productside's State of AI Maturity report, product managers rated themselves 7.5 out of 10 on prompting and experimenting with AI, and 5.9 on value mapping and strategic assessment. Twenty-eight percent rated themselves between 1 and 4 out of 10 on connecting AI to actual business value. Using a tool every day builds fluency with the tool. It doesn't, on its own, teach anyone to tell what that tool is worth to the business, which is a commercial question wearing a technical costume.

It's the same gap twice. PMs are strong at the work they repeat every week, because repetition builds skill. They're weaker at the calls that come up once a quarter or once a year, are usually made by someone more senior, and can't be practiced at the same rate.

The boss gap

Productside also looked at how skills change across a career, and the pattern explains why the gap persists. In its earlier benchmark, it described a progression. Early-career PMs focus on requirements, process, and launches. Mid-career, the attention shifts to competitive analysis, pricing, and forecasting. For those aiming at Director or VP, it's strategy, leadership, end-of-life planning, and running the product process itself, where Directors outperformed individual contributors by an average of 29%.

In other words, the commercial skills arrive late, and they arrive mostly through promotion. A PM learns pricing by eventually being the person who sets prices. That's a slow way to build a skill a company may need from its product team much sooner, and it means that in a lot of organizations the people closest to the customer are the furthest from the commercial decisions.

It also explains the self-assessment. The PMs in Productside's data aren't underrating themselves out of modesty. They're accurately reporting that they haven't done this work very often.

It isn't for lack of trying

Two other surveys suggest the gap is structural. In Product Focus's 2026 survey of 677 product people, mostly in Europe, 34% said they had no clear primary metric they were held accountable for. And in ProductPlan's State of Product Management 2026, confidence that teams outside product understood the product strategy averaged just 3 out of 5.

Put those together and you get a lot of product managers working without a clear commercial target, inside organizations where the strategy isn't widely understood, and rarely in the room for pricing, competitive, or end-of-life decisions. It would be strange if they rated themselves highly on commercial judgment. Nobody's given them the reps.

What this means for a founder

Here's where it matters if you run the company. When growth flattens and the question becomes which market to go after, what to build next, or what to stop doing, the natural move is to hand it to the product team. They know the product, they talk to customers, and it's their job.

But the question you're handing them depends on exactly the skills this data says they're least confident in: sizing a market, understanding how competitors will respond, pricing, and deciding what to retire. A product team that's excellent at shipping can still struggle to make a defensible direction call. That isn't a question of intelligence. It's work most of them have rarely been asked to do, with information they've rarely been given.

That's how a company ends up with a strategy that's really a roadmap: a list of things the team is good at building, ordered by who asked loudest. A cheap yes leads to an expensive no, and "let's have product figure out the strategy" can be one of the cheapest, because it feels like delegation and is often the decision being deferred.

How the gap closes

The encouraging part of Productside's data is that this is learnable. Productside reported that PMs who'd been through training scored 14% stronger across all fifteen skills, and the gap was widest in end-of-life planning. Productside sells training, so take the figure with that in mind, but the direction makes sense. These skills grow with exposure and practice, like anything else.

I've seen it happen. When I came in to help Stride's Career-as-a-Platform team, which had been struggling to ship, part of the work was a four-day intensive with the business analyst, the junior PM, the head of design, and key executives on strategy development, measuring success, conflict resolution, and execution cadence. Then I modeled it with them sprint after sprint until it stuck. The capability was there. The exposure hadn't been.

If you want your product team to make better commercial calls, a few things help.

Give them a primary metric. Product people without a clear number they're accountable for can't build judgment about what moves it. Pick one, and make it a business outcome rather than a delivery count.

Bring them into the rooms where commercial calls get made. Pricing reviews, competitive losses, decisions to retire something. Watching those calls get made, with the reasoning out loud, is how the skill transfers.

Separate the big direction call from the roadmap. Asking a product team to set the strategy and execute it at the same time usually means the execution wins. For a high-stakes question like a new market, it's often worth getting an outside read, with the evidence shown, that the team can then own and build against.

Be honest about what you're asking for. If the question is really about which market to bet the company on, say so, and give it the time and information that kind of decision needs.

The product managers in this data are telling their bosses something useful, in a form that's easy to overlook because it arrives as a self-assessment. The calls they're least sure about are the ones the company's direction depends on. That's worth taking seriously before you hand them one.

–Matthew

More Field Notes

  1. Consulting Operations

    We Won Awards for Checkout Speed. Customers Waited Longer.

    A metric that covers part of the work moves the rest out of sight. A Kmart stopwatch and England's emergency rooms show where to look.

  2. Consulting Operations

    AI Agents Raised Pull Requests 36%. Shipped Work Didn't Keep Pace.

    A Harvard study of 718 companies found AI agents raised code output far faster than shipped work. Why, and what a founder should measure instead.

  3. Consulting Operations

    I Cancelled the Test Before We Built It. The Math Said It Couldn't Win.

    A test that can't produce a readable result shouldn't be built, and the time to decide what would make you stop is before the results come in.

Want help running a sharper practice?

The reading and synthesis behind your client work, handled – a living deliverable kept current, so more of your time goes where your name is actually on the line.