Last updated: August 2026
You’ve been in enough rooms to know the truth: half the product managers out there are glorified project coordinators who slow everything down.
They create process for process’s sake. They gate decisions that don’t need gating. They turn a simple feature discussion into a three-meeting odyssey through roadmap reviews and stakeholder alignment sessions that accomplish nothing.
And if you’re leading a product organization, you feel this acutely. You’re trying to move fast with fewer resources, and some of your PMs are the bottleneck.
So the question isn’t whether product management as a function has value. The question is: how do you tell the difference between PMs who accelerate your team and PMs who just add overhead?
In this article
- The Bottleneck You Can’t Afford
- What Strong PMs Actually Do
- Process vs. Velocity
- The Only Question That Matters
- Frequently asked questions
The Bottleneck You Can’t Afford
Here’s the pattern. Your team waits for PM approval before moving forward. Decisions stack up because only the PM has context. Engineers build features without understanding the commercial impact because the PM hasn’t translated strategy into something actionable.
The PM becomes a single point of failure. Everything routes through them. And velocity dies.
This is what skeptics see when they argue that PMs don’t add value. They’re not wrong about the pattern. But they’re misdiagnosing the cause.
The issue isn’t the PM function. It’s how the PM operates.
What Strong PMs Actually Do
A strong product manager doesn’t manage work. They remove what blocks work from happening.
When your team is stuck waiting for data, a good PM gets that data. When there’s confusion about what success looks like, a good PM defines it. When decisions stall because information is missing, a good PM ensures that information arrives before it becomes a blocker.
They don’t sit between your team and progress. They clear the path ahead so your team can move faster.
Think of it as a support system for your entire project pipeline. Not a gatekeeper. A path clearer.
Process vs. Velocity
Weak PMs focus on process and control. They implement frameworks because frameworks feel like leadership. They create approval gates. They position themselves as decision-makers who need to review everything.
Strong PMs focus on velocity and clarity. They implement just enough structure to prevent chaos. They push decision-making authority to the people closest to the work. They make sure teams have what they need to move fast.
It’s a different philosophy entirely. One treats the PM as the center of all product work. The other treats the PM as the support system that keeps product work flowing.
The Only Question That Matters
If you’re hiring product managers or evaluating the ones you have, ask this: Are they removing obstacles or creating them?
Because velocity comes from teams who can make swift decisions and execute without friction. If your PM creates friction, you have the wrong PM. If your PM removes friction, you’ve found someone genuinely valuable.
Most teams I work with discover the issue isn’t whether they need product management. It’s whether their PMs are actually operating at the level the business requires. When senior product leaders can’t articulate their strategic impact or translate product work into commercial language their executives understand, that’s not a product management problem. That’s an operating model problem.
If you’re trying to figure out whether your product organization is structured for velocity or just structured for meetings, let’s talk. Book a call and we’ll map out where the friction is actually coming from.
Frequently asked questions
Do product managers actually add value?
The value of product management as a function isn’t really the question. What matters is how a given PM operates, whether they clear the path so the team moves faster or become a single point of failure that everything routes through. Telling those two apart is where the real judgment comes in.
How do I tell a good product manager from a bad one?
Ask one question: are they removing obstacles or creating them? A strong PM gets the data the team is waiting on, defines what success looks like, and makes sure information arrives before it becomes a blocker, while a weak one builds approval gates and positions themselves to review everything.
Why do some PMs slow teams down instead of speeding them up?
They treat process as the job, adding frameworks and approval gates because those feel like leadership, and they set themselves up as the decision-maker who has to review everything. When only the PM holds the context, decisions stack up behind them and velocity dies.
What does a strong product manager actually do?
A strong PM doesn’t manage work, they remove what blocks it. They push decision-making to the people closest to the work and keep just enough structure to prevent chaos, acting as a support system for the pipeline rather than a gatekeeper.
My PMs feel like a bottleneck. Is that a product management problem?
Often the problem isn’t whether you need product management, it’s whether your PMs are operating at the level the business requires. When senior product leaders can’t articulate their strategic impact or translate product work into commercial language executives understand, that points to an operating model problem, and pinpointing where the friction actually comes from usually takes an outside look.