Skip to content
Core craftenterprise

Influence without authority

Owning outcomes across teams you don't manage.

The short version

In any large org, a PM is accountable for outcomes they do not control, delivered by teams that do not report to them. Influence is the skill that closes that gap. It is not persuasion tricks; it is mapping who matters, understanding what each person actually needs, building a case in their language, and being the kind of partner people want to say yes to.

Why it matters

The bigger the company, the more your success sits in other people's hands, engineering, legal, finance, partner teams, your manager's peers. Positional authority barely exists for a PM; influence is the actual operating mechanism. It is not a soft skill, it is the job.

The mistake is treating influence as something you turn on when you need something. It compounds the opposite way: you invest in relationships and credibility before you need them, so that when the ask comes, you have already earned the yes.

How to do it

01
Map the stakeholders. List everyone involved; note who lets it happen, helps it happen, or makes it happen, and who is a supporter, blocker, or neutral.
02
Understand their needs first. Drop the us-versus-them frame. What are their goals, metrics, pressures? How does your work make their problem easier?
03
Do the homework. Read their OP plans, roadmap, tenets, MBRs before a big ask. Look for disconfirming data, not just support for your view.
04
Build the case in their language. Customer problem (with data) → your proposal → how it helps them → exactly what you need. Acknowledge the risk you are asking them to take.
05
Match their influencing style. Some are convinced by data, some by mission, some by collaboration. Present in the way that resonates with them, not with you.
06
Follow through. Be an organized, responsive, low-friction requester who delivers. Reputation is the cheapest influence there is.

When you hit resistance

✕

Treat pushback as input to build on, not a threat to defend against, it usually makes the idea better.

✕

Ask, don't assert: "Help me understand the issue. What would close the gap?" in their language.

✕

Hearing "no" is a chance to learn what the no was about, offer a scrappy pilot or proof of concept and come back.

✕

Escalate as a shared, data-driven document both teams own, never as a surprise. A good escalation earns trust; it does not burn it.

In a startup

There are fewer teams and shorter lines, so influence is mostly relationship + clarity. But the muscle still matters with investors, partners, and early hires you cannot command.

In an enterprise

This is where the craft is decisive: dozens of autonomous teams with competing priorities. Map vertical and horizontal influence, get traction lower in the org before going up, and bring the derivation, not just the conclusion, so people can follow you.

Quick check

0/2

Optional, find the right answer for each to complete the concept. Keep trying; nothing is gated.

1. Why is influence without authority core to the PM role?

2. What is the right way to escalate a cross-team disagreement?

Continue the path

Next concept →

Metrics & outcomes

Related perspective →

Working with engineering