You own outcomes but rarely own people. This is the defining constraint of product management, and it's one that most aspiring PMs dramatically underestimate until their first roadmap negotiation hits a wall.
Engineering has their own manager. Design has their own manager. Data science has their own manager. You have a title and a backlog. The question is: how do you actually lead?
What Influence Is Not
Influence is not persuasion theater. It's not the ability to make a compelling deck or to argue well in meetings. Those are tools, and they're overused.
Real influence is the ability to shape how a team thinks about a problem before anyone has started arguing about solutions. It's upstream of the debate.
The Trust Ledger
Every working relationship has an implicit trust ledger. You build credit through small, consistent actions: showing up prepared, following through on commitments, acknowledging when you're wrong, giving credit generously. You spend credit when you need someone to take a risk with you — to try something uncertain, to delay their team's work for yours, to champion your proposal in a meeting you're not in.
Most PMs who struggle with influence have a credit problem, not a persuasion problem. They're trying to spend trust they haven't built.
Influence is a lagging indicator of credibility. You can't shortcut the credibility.
The Specific Moves
A few things that have consistently worked for me:
Make people feel heard before you make your case. Not performatively — actually understand what they're worried about. Engineers who push back on a feature usually have a real concern. Find it. Address it directly. The concern doesn't go away because you argued past it.
Give the "why" before the "what." Context changes how people receive requests. "Can you build X?" lands differently than "We're seeing Y happen to users, and we think X is the fastest way to address it. Can you build X?"
Be transparent about trade-offs. PMs who pretend there are no costs to a decision destroy trust faster than almost anything else. Name the trade-off. Own your reasoning for accepting it.
Build the relationship before you need it. The worst time to start building trust with an engineering lead is when you need them to prioritize your project. The best time was six months ago.
Authority is a shortcut for trust — a way of making people follow you without having earned it. The problem is that shortcuts taken in leadership are visible. People comply with authority. They commit to people they trust.
Build the trust.