Authority is granted; Influence is earned.
1Building Social Capital
Influence is built on trust. Trust is built by being reliable, being honest about what you don't know, and consistently delivering value to the team.
2Active Listening
To influence people, you must first understand them. What are the engineers worried about? What is the designer's vision? By listening more than you talk, you find the common ground.
3Taking the Blame, Sharing the Credit
When a product fails, the PM takes the blame. When it succeeds, the PM gives the credit to the team. This extreme accountability is what makes people want to follow you.
4Step-by-Step Breakdown
PMs are often called the 'CEO of the Product', but they rarely have direct reports. You have to lead through influence, data, and trust.
Lead by providing 'Context'. If the team understands the 'Why' (the user pain and business goal), they will lead themselves to the best solution.
Be a 'Servant Leader'. Your job is to remove obstacles for your team. If an engineer is stuck on a requirement or a designer needs data, you are the one who gets it for them.
What is the most effective way to influence an engineering team to work on a specific feature?
- →Tell them the CEO ordered it
- →Show them the data and user feedback that proves this feature will solve a major pain point
- →Offer to buy them lunch
- →Remind them that you are the Product Manager
What does 'Leading with Context' mean in practice?
- →Giving the team a 100-page manual on the product
- →Ensuring the team has all the information they need (vision, goals, user insights, constraints) to make their own high-quality decisions
- →Checking in with the team every 30 minutes
- →Writing the code for them
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Inclusive Facilitation
Leading through influence means making sure quieter voices on the team — not just the loudest engineer in standup — get heard when decisions are made. A PM who only gathers input verbally in real-time meetings systematically excludes people who think better in writing or need more processing time.
Pair live discussion with an async written doc (e.g., a shared decision doc) so every team member can contribute regardless of communication style.SEO Implications
- 1
Search Intent for 'PM Leadership Skills'
Readers searching this topic are usually early-career PMs anxious about not having formal authority. Content that names concrete tactics (leading with context, servant leadership) ranks better than abstract 'be a good leader' advice.
Best Practices
Lead With Context, Not Instructions
Share the user pain, the business goal, and the constraints openly, then let the team propose the solution. Teams that understand 'why' make better decisions without needing you in every conversation.
Remove Obstacles Proactively
If an engineer is blocked waiting on a decision or a designer needs user data, treat unblocking them as part of your job, not a favor. Servant leadership earns the trust that influence depends on.
Frequent Bugs
A PM tries to resolve a cross-functional disagreement by pulling rank ('I'm the PM, we're doing it my way'), which produces silent compliance instead of real buy-in.
Bring data and user evidence to the disagreement instead of authority, and if the team still disagrees, address the underlying concern directly rather than overriding it.
Real-World Examples
Unblocking a Stuck Engineer
An engineer is blocked because a requirement is ambiguous and the PM is in back-to-back meetings.
1. Notice the blocker early (daily check-ins, not just weekly syncs).
2. Get the engineer a decision within hours, not days — even a partial answer unblocks progress.
3. Follow up with the full context once available.