Cross-Functional Leadership: How PMs Lead Without Authority

The PM Paradox

Here’s the core tension of product management: you own the outcome but don’t manage any of the people building it. Engineers report to engineering managers. Designers report to design leads. You report to nobody’s org chart. Yet you’re responsible for shipping.

This is what makes product management both the hardest and most rewarding role in tech.

The Five Sources of PM Influence

1. Expertise

Know your market, users, and data better than anyone else. When you walk into a room with superior data analysis and user research, people listen.

2. Vision

Articulate a compelling “where we’re going” that excites the team. Strategic thinking translates into a clear vision that engineers want to build toward.

3. Trust

Deliver on promises. Be consistent. Share credit. Trust is earned over months and lost in minutes. Your stakeholder management practices build this over time.

4. Clarity

Write clear PRDs. Run efficient meetings. Remove ambiguity. Teams follow leaders who make their lives easier, not harder.

5. Empathy

Understand what motivates each person on your team. Engineers want technical challenges. Designers want user impact. Respect their craft and they’ll respect your direction.

Practical Techniques

The Decision Log

Document every major decision with context, alternatives considered, and reasoning. This shows your strategic thinking and creates transparency.

The “Disagree and Commit” Framework

When there’s no consensus:

1. Give everyone a chance to voice their position
2. Make the call and explain your reasoning
3. Ask the team to commit to executing, even if they disagree
4. Set a review point to evaluate the decision with data

The Weekly 1:1 (Informal)

You don’t manage the team, but you should still have regular informal check-ins with your engineering lead, design lead, and key individual contributors. These build the relationship that makes formal decisions smoother.

The Pre-Alignment Meeting

Before any big meeting (sprint planning, roadmap review, exec review), meet individually with key stakeholders. No surprises. By the time the meeting starts, alignment already exists.

Leading in Different Contexts

At a Startup

Fewer politics, more action. You can ship fast but need to wear multiple hats. Leadership is about speed.

At an Enterprise (Like Jio)

More stakeholders, more process, bigger impact. At the AI Impact Summit 2026, I coordinated multiple teams as a hybrid PM/PgM. Enterprise leadership is about alignment across scale.

With Remote Teams

Over-communicate. Document everything. Use async tools well. The PM who writes clear specs and decisions in docs leads better than the PM who relies on hallway conversations.

When Leadership Gets Hard

• When you’re wrong: Admit it publicly and quickly. The team respects honesty over infallibility
• When priorities shift: Explain the why. Teams handle change well when they understand the reasoning
• When there’s conflict: Address it directly. Unresolved tension kills velocity
• When you’re new: Listen for the first 30 days. Earn trust before pushing change

---

More PM leadership: OKR setting or PM interview prep. Subscribe.