Product managers are in a strange position. They're responsible for the product's success, but they control none of the people who build it.
No direct reports. No budget authority. Just a roadmap, a Slack channel, and the ability to influence.
This sounds like a nightmare until you realize it's actually the right model — and one that teaches you the most durable leadership skills in tech.
Why the Authority Model Fails
When managers rely on positional authority, they get compliance, not commitment. Engineers who are told what to build ship it. Engineers who understand why they're building it make better decisions at every step: how to architect it, what edge cases to handle, when to push back on scope.
A PM who leads through authority gets a team that waits to be told what to do. A PM who leads through influence gets a team that brings them problems before they become bugs.
What Actually Works
Make the problem vivid, not the solution
Don't come to engineering with "build this." Come with the customer problem, the data that proves it matters, and the constraints. Let the team propose solutions. You'll often get a better answer than you would have specified, and the team will own it.
Protect engineering from noise
One of the highest-value things a PM does is be a human firewall. Every HiPPO opinion, every sales team escalation, every founder whim that doesn't actually reflect user needs — those should hit you, not your engineering team. Your credibility comes from your team trusting that the work they're doing matters.
Say no in public, yes in private
When you need to push back on scope, do it before the sprint. Relitigating a feature in a standup erodes trust and wastes time. Get alignment in 1:1s and planning meetings, then present a unified front.
Keep score of your predictions
PMs who track their own accuracy build credibility fast. If you said this feature would move retention by 15% and it moved it by 12%, say so. If you said it would take two sprints and it took four, say so. People trust forecasters who are honest about their forecasting, not forecasters who pretend they're always right.
The Long Game
The best PMs I've seen don't feel like managers at all. They feel like the person on the team who most clearly understands what the user needs, what the business needs, and what the engineering team is capable of — and synthesizes those into a direction that everyone can believe in.
That's not authority. That's earned trust. And it's much more powerful.