power and influence in organizations

Product managers have no authority over the people whose work determines their product's success. No engineer, designer, analyst, or stakeholder reports to the PM. Every outcome the PM is accountable for depends on people they cannot command.

This is not a bug in the organizational design — it is the feature. The PM's accountability without authority forces a discipline of genuine persuasion that strengthens product decisions. But it requires explicitly building influence rather than assuming it comes with the title.

Two types of power

Positional power: Derives from role, title, and formal authority. Managers have positional power over their direct reports. Executives have positional power over the broader organization. This power enables commands — "do this because I said so" — and is backed by the ability to hire, fire, and allocate resources.

PMs have minimal positional power. They can escalate to leadership. They can control the backlog. But they cannot mandate priorities from engineering or compel design to produce what they want.

Personal power: Derives from expertise, credibility, relationships, and character. This is the PM's primary lever. Personal power is earned, not assigned. It compounds over time as you demonstrate sound judgment, deliver results, and build trust.

The key insight: personal power is more durable than positional power. A VP who loses the confidence of their team has formal authority but diminished actual power. A PM who has deep credibility with engineering and design can move mountains despite having no formal authority.

The five bases of power

John French and Bertram Raven identified five bases of social power. PMs have access to all five, though positional ones are limited:

Legitimate power (positional): The authority that comes from role. The PM has some — they own the backlog, they can escalate, they set product direction. Limited but real.

Reward power (positional): The ability to offer something valuable in exchange for compliance. PMs can offer: credit and recognition, visibility, interesting problem assignments, and advocacy for team members' growth. These are meaningful rewards even without budget authority.

Coercive power (positional, should be avoided): The ability to punish. PMs who rely on this — threatening escalations, creating conflict — burn through relationship capital rapidly. Avoid.

Expert power (personal): The most important source of PM power. Deep knowledge of the product domain, the user, the competitive landscape, and the data gives you credibility that others defer to. When you know more about the customer's problem than anyone in the room, your recommendations carry weight because they are demonstrably well-founded.

Referent power (personal): The power of being liked, respected, and trusted as a person. People do things for those they respect and admire, even when they are not required to. This is built through consistent integrity, genuine interest in others' success, and being the kind of person colleagues want to work with.

Building influence as a PM

Influence is not manipulation. Manipulation involves misleading people or exploiting cognitive biases for self-interested ends. Influence is the legitimate use of information, reasoning, relationships, and reciprocity to align people around good decisions.

Practical strategies that work:

Build subject matter expertise relentlessly. The PM who knows the customer's problems better than anyone, who can quote the retention data from memory, who has read the competitive landscape in depth — this person's recommendations are trusted because they are earned. Expertise is the single most important influence foundation.

Demonstrate consistency between words and actions. If you say you will do something, do it. If circumstances change, communicate proactively. Consistency builds trust at a rate that eloquent arguments cannot.

Use social proof. "The engineering lead at [similar company] tried this approach and here is what happened" is more persuasive than your own advocacy for the same approach. Document and share examples of outcomes from comparable decisions.

Build goodwill through reciprocity. Help engineers solve problems that are not strictly "PM problems." Advocate for design team resources in leadership conversations. Solve stakeholder problems that fall outside your direct scope. Reciprocity is not calculation — it is a genuine investment in the people you need to work with.

Make disagreement safe. If people fear that disagreeing with you will cost them relationship capital, you will stop receiving honest feedback and eventually make poor decisions in a vacuum of agreement. Actively invite challenges to your positions. Give credit when someone's pushback improves your thinking.

The organizational politics reality

Influence in organizations is also shaped by formal and informal political structures that go beyond technical merit. Some truths worth accepting:

Organizational context matters more than argument quality. The same recommendation may succeed when a trusted leader is present and fail when political opposition controls the room. Influence requires reading the room, not just having the right answer.

Relationships precede influence. You cannot influence people you do not have a relationship with. Building relationships before you need them — not just during escalation crises — is the most important preventive influence investment.

Perceived alignment with organizational goals matters. Recommendations that are explicitly connected to what the CEO or leadership team cares about get more traction than equally good recommendations that are not. This is not manipulation — it is communication.

Losing gracefully is part of the influence game. Sometimes you will lose a product argument that you were right about. The PM who accepts this loss gracefully — and is later proven right — builds more long-term influence than the PM who wins through persistence but damages relationships in the process.