Stakeholder Management for VPs: The Art of Moving People Who Don't Report to You

There is a specific frustration that surfaces in almost every VP coaching conversation within the first two sessions. It sounds like this: "I have the right strategy. The work is solid. But I can't seem to get traction — people keep pushing back, or going around me, or just not moving."

The strategy usually is solid. The work usually is good. The problem is stakeholder management — or more precisely, the absence of it. When you were a Director, most of the people who needed to act on your work reported to you or to someone you had easy access to. At VP, the network of people whose cooperation you depend on expands dramatically, and most of them have no reporting obligation to you whatsoever.

This is what influence without authority actually looks like in practice: not inspiration or charisma, but the patient, deliberate work of building the conditions under which people who don't report to you choose to move in your direction.

Why Stakeholder Management Breaks Down at VP

Most leaders spend their early careers in an environment where influence mostly travels down the org chart. You get good at setting direction, building team buy-in, and holding people accountable. These are real skills — and they transfer poorly to lateral influence.

Lateral influence — moving peers, cross-functional partners, and adjacent leadership — operates on different mechanics entirely. There is no reporting line to rely on. There is no formal performance lever. And critically, the people you need to move have their own priorities, their own pressures, and their own reasons for not helping you.

The VP who manages this well doesn't wait until they need something to invest in these relationships. They don't assume shared organizational goals are enough to generate cooperation. And they don't mistake email communication for genuine stakeholder alignment.

Building Your Stakeholder Map

Effective stakeholder management starts with clarity about who actually matters to your outcomes — and that list is almost always larger and more complex than VPs initially recognize.

Start with two dimensions. The first is level of influence over your outcomes: how much can this person help or hinder your initiative succeeding? The second is current alignment: to what degree are their goals and yours already pointed in the same direction?

Plotting key stakeholders on this grid gives you a working map of where to invest. Four quadrants emerge:

• High influence, misaligned — your highest-priority relationships. These are the people who can derail your work and currently have reasons to. Understand their objections specifically. Find the real concern underneath the surface resistance. This work is often uncomfortable, but skipping it means these stakeholders will surface opposition at the worst possible moment.
• High influence, aligned — your coalition anchor points. Protect these relationships actively, not just when you need them. Keep these stakeholders informed and give them the tools to advocate for your work in rooms you are not in.
• Low influence, aligned — keep them warm with periodic updates. They are unlikely to help you significantly, but they are also unlikely to create friction.
• Low influence, misaligned — monitor, but don't over-invest. Their resistance has limited reach. If their influence grows, revisit.

The map is not static. Influence and alignment shift as organizational priorities evolve and as people's own circumstances change. Review it quarterly at minimum, and after any significant org change or leadership transition in your space.

The Buy-In Conversation Most VPs Get Wrong

When VPs need cross-functional support, the most common approach is to schedule a meeting and make the case for their initiative. Here is what that looks like from the peer's perspective: someone whose initiative you are being asked to support, using your team's time and resources, is explaining to you why their initiative is important.

This approach is almost never wrong in its logic. The initiative often is important. The case often is sound. But it lands as an ask with no obvious answer to the question the peer is silently asking: What does this mean for me?

Effective buy-in conversations start somewhere different. Before the meeting, the VP who understands lateral influence mechanics has done the homework: What is this peer being measured on this quarter? Where is their team under pressure? What have they been publicly advocating for in leadership forums? What organizational problem does my initiative actually solve for them?

The meeting then begins from that intersection. Not: "Here is why my initiative matters." But: "Here is how this connects to what you are working on — and here is specifically what I need from your team to make it work."

Coalition Building Happens Before You Need It

The VP who shows up in a peer's calendar only when they need something is starting every conversation at a deficit. Reciprocity is a real force in organizational dynamics — not as a transactional ledger, but as an accumulated sense of who gives as well as takes.

Building coalitions continuously — even when there is no live initiative requiring their support — is one of the most high-leverage investments a VP can make. In practice, this looks like:

• Showing up in their work, not just yours. Attend a peer's all-hands occasionally. Mention their team's wins in leadership forums. Flag an article or piece of market intelligence that is directly relevant to their priorities.
• Offering before being asked. If your team has capacity that could help a peer through a crunch, offer it. If you hear something in an ELT meeting that is directly useful to a peer, share it immediately — don't wait for the next scheduled touchpoint.
• Making the introduction. One of the most underused tools in lateral coalition building is the cross-functional introduction: connecting a peer to someone in your network who can help them. It costs you almost nothing and creates disproportionate goodwill.
• Being explicit about your support. When a peer needs something in a room you will be in, ask them beforehand: "What do you need from me in that meeting?" Most leaders are not asked that question. The ones who are remember it.

When a Stakeholder Consistently Resists

Not every stakeholder will become an ally. Some resistance is persistent — and understanding what is driving it is the first step to addressing it or routing around it strategically.

Persistent resistance usually comes from one of three places. First, a genuine values or strategic disagreement — they actually think your approach is wrong, and they may not be entirely wrong. Second, a resource constraint they haven't surfaced publicly — your initiative pulls from capacity they cannot afford to give. Third, a relational or political dynamic you are not fully seeing — there is history, competition, or loyalty to a different camp that makes supporting you feel costly.

The leadership mistake is to treat persistent resistance as obstruction and try to go around or above it. This occasionally works in the short term and almost always creates lasting damage. A stakeholder who was difficult becomes an active opponent. A nuisance becomes a liability.

The more effective path — and the harder one — is to name the pattern directly in a one-on-one conversation. Not as an accusation, but as an observation: "I've noticed we're not fully aligned on this. I want to understand your perspective better — what am I missing?" Most leaders are not asked that question either. The answer is often more useful than months of maneuvering around the resistance.

Managing Up While Influencing Across

Stakeholder management at VP is not only a lateral exercise. Your upline relationships — the SVP, the C-suite sponsor, the business unit leader who owns the budget — also require deliberate management, though through different levers.

Senior leaders care about outcomes, not effort. They want to know what you are working on, what risks exist, and what you need from them — in that order, and in as few words as possible. Managing up well means translating the complexity of your work into the three things your upline leader needs to know today, not a comprehensive briefing on everything happening in your function.

Managing across, by contrast, requires more relational investment and more time horizon. Lateral influence accrues slowly and degrades quickly. The VP who manages their upline brilliantly but neglects peer relationships discovers the gap when they need cross-functional cooperation for something that matters — and finds themselves starting from zero.

The full picture of influence without authority includes both dimensions: maintaining the credibility and visibility that allows you to shape decisions upline, and building the lateral relationships that allow you to move work across organizational boundaries. Neither alone is sufficient at VP and above.

What Strong Stakeholder Management Actually Looks Like

The VP who manages stakeholders well rarely has to fight for their initiatives. Major decisions don't surface surprising opposition because opposition was identified early and addressed or incorporated. Cross-functional projects don't stall because the right relationships were built before the project started. Upline leaders are generally not surprised because they are kept informed through deliberate, concise communication — not information dumps.

The result looks effortless from the outside. Initiatives move. Peers cooperate. Sponsors advocate. This is sometimes misread as charisma or politics — but it is neither. It is a set of disciplines practiced consistently over time:

• Knowing who your stakeholders are and keeping the map current.
• Investing in relationships before you need anything from them.
• Leading buy-in conversations from the peer's priorities, not your own.
• Naming resistance directly instead of routing around it.
• Managing upline through clarity and brevity, not volume.

For a deeper foundation on the mindset shift behind all of this — why results alone stop being enough and what organizational fluency actually requires — the full playbook is in the guide on influence without authority at the VP level.

Frequently Asked Questions