Skip to content
ORGANIZATIONAL AWARENESS

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

Your direct reports move when you ask. Your peers and senior partners are a different matter, and many VPs are underprepared for it.

April 2026 · 11 min read Part of: Cross-Functional Influence
VP leading cross-functional stakeholder meeting

A specific frustration comes up early in many VP coaching conversations, often 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 sharply, and most of them have no reporting obligation to you.

This is what cross-functional influence looks like in practice: patient, deliberate work that makes people who don't report to you willing 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, but they transfer poorly to lateral influence.

Lateral influence (moving peers, cross-functional partners, and adjacent leaders) works differently. There is no reporting line to rely on and no formal performance lever. And 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 real stakeholder alignment.

"The leaders who are hardest to work with are often the ones who are most confident in their logic. They believe a well-constructed argument should be enough to move people. It isn't — not at this level."

Building Your Stakeholder Map

Effective stakeholder management starts with clarity about who matters to your outcomes. That list is usually larger and more complex than VPs first expect.

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 meetings you do not attend.
  • 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 Many 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.

The logic is usually fine. 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. Instead of "Here is why my initiative matters," the opening is: "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."

Pre-buy-in checklist

  • What is this stakeholder's top priority this quarter?
  • Where does my initiative intersect, even partially, with that priority?
  • What is the specific ask? (Time, resources, a decision, a voice in a meeting?)
  • What's the minimum viable support I need versus what I ideally want?
  • Have I given this peer something of value recently: a referral, a heads-up, support on their own initiative?

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. It works less as a transactional ledger than as an accumulated sense of who gives as well as takes.

Building coalitions continuously, even when there is no live initiative that needs a peer's support, is one of the most useful investments a VP can make. In practice, this looks like:

  • Showing up in their work as well as 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 right away instead of waiting 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 little and builds a lot of goodwill.
  • Being explicit about your support. When a peer needs something in a meeting you will attend, 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 drives it is the first step to addressing it or working around it.

Persistent resistance usually comes from one of three places. First, a real values or strategic disagreement: they think your approach is wrong, and they may not be entirely wrong. Second, a resource constraint they haven't raised publicly: your initiative pulls from capacity they cannot afford to give. Third, a relational or organizational 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 sometimes works in the short term and often creates lasting damage: a stakeholder who was difficult becomes an active opponent.

The more effective and harder path is to name the pattern directly in a one-on-one conversation, as an observation instead of an accusation: "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 more than 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 over a longer period. Lateral influence accrues slowly and degrades quickly. The VP who manages their upline well but neglects peer relationships discovers the gap when they need cross-functional cooperation for something that matters, and has to start from zero.

The full picture of cross-functional influence 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 instead of information dumps.

From the outside, the result can look effortless and is sometimes mistaken for charisma or maneuvering. It comes from 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 the mindset behind all of this (why results alone stop being enough and what organizational fluency requires), see the guide on cross-functional influence at the VP level.

Frequently Asked Questions

What is stakeholder management at the executive level?

At the executive level, stakeholder management means building and maintaining relationships with peers, upline leaders, and cross-functional partners whose cooperation you depend on but cannot command. It goes beyond project-level coordination: it is an ongoing practice of understanding what each stakeholder values, keeping them appropriately informed, and creating the conditions for your initiatives to move forward without friction. VPs who do this well rarely encounter surprise resistance; VPs who neglect it find themselves constantly re-selling work that should already have support.

How do you map stakeholders as a VP?

Effective stakeholder mapping starts with two dimensions: level of influence over your outcomes and level of alignment with your agenda. Plot each key player on that grid, then prioritize accordingly. High influence and misaligned requires your most deliberate attention: these are the people who can derail your initiatives and currently have reasons to. High influence and aligned stakeholders are your coalition partners, so protect those relationships and draw on them. Revisit the map quarterly, because alignment and influence shift as organizational priorities evolve.

How do you get buy-in from peers who don't report to you?

Peers grant buy-in when they see a clear connection between your ask and their own goals. Before any pitch, do the homework: understand what each peer is measured on, what pressures they are under, and where your initiative intersects with their interests. Lead with that intersection, and frame your request in terms of how it helps them as well as why it matters to you.

What is the difference between managing up and managing across?

Managing up means cultivating your relationship with senior leaders: keeping them informed, shaping their perception of your work, and ensuring you understand their priorities. Managing across means doing the same with peers at your level across different functions. Both matter at VP, but the lateral relationship is harder because there is no reporting line to enforce cooperation; everything depends on trust, reciprocity, and perceived mutual benefit.

How do you build coalitions across functions as a VP?

Coalition building starts before you need anything. Invest in peer relationships continuously: attend their forums, offer your team's resources when they are under pressure, flag relevant information proactively. When the moment comes to ask for support, the relationship exists. The ask lands in a context of mutual trust and reciprocity, not as a cold pitch from someone who only shows up when they need something.

Working on your stakeholder relationships?

We work with VPs and SVPs on the organizational skills that affect whether leaders advance.

Book a Free Call
Book a Free Call