Ask any VP what takes up most of their time and you'll get variants of the same answer: meetings to align with other departments, decisions that require buy-in from peers they don't control, and the ongoing work of keeping three or four cross-functional initiatives moving simultaneously. Research consistently places this category of work at 35–45% of VP-level time.
Now ask the same VP whether their company has ever given them explicit development support for cross-functional negotiation as a skill. The answer is almost always no. Most L&D programs at this level cover communication, leadership presence, strategic thinking, and delegation. The specific skill of negotiating with peer-level stakeholders who have competing priorities, different success metrics, and no formal obligation to accommodate your needs — that rarely appears as a named, developable competency.
This is one of the clearest mismatches in corporate leadership development, and it shows up consistently in Coachvyne's scoring data. Influence Without Authority is one of the lowest-average-scoring dimensions across all simulation types. It's also one of the dimensions that 360 feedback most frequently surfaces as a gap when directors are being evaluated for VP readiness.
Why "Influence Without Authority" Gets Treated as a Personality Trait
The most common way L&D programs handle cross-functional influence is to frame it as a personality or style dimension — some people are naturally good at building relationships, reading rooms, and bringing people along. Programs that take this approach offer advice like "build your internal network," "find common ground," and "understand the other party's perspective." All of this is true and none of it is wrong. It's also not quite enough.
The problem is that framing cross-functional negotiation as a relationship-building skill misses the structural elements that make it hard. A VP of Product who needs engineering resources for a Q4 initiative isn't just dealing with a relationship dynamic — they're dealing with a genuine resource constraint, a VP of Engineering whose team is already at capacity, a CFO who hasn't approved additional headcount, and a CEO who has signaled that both the product initiative and the engineering team's current commitments are high priority. That's a real negotiation with structural tensions. Liking each other won't resolve it.
Effective cross-functional negotiation at the VP level requires understanding the other party's actual constraints (not just their stated position), identifying the tradeoffs that are genuinely available (not just the ones you'd prefer), and framing proposals in a way that gives the other party a clear path to yes without requiring them to fail somewhere else. These are learnable skills. They're also skills that don't develop through relationship-building advice.
The Three Specific Failures We See in Simulation
The cross-functional negotiation scenario in Coachvyne puts the VP in a situation with a peer-level stakeholder who has competing priorities and is initially resistant to the VP's request. The scenario is designed to require active negotiation, not just persuasion. Here's what the scoring data shows about where VP-level leaders most consistently struggle.
Anchoring too early on a specific ask. Many VPs come into a negotiation with a specific request framed as the ask, rather than starting by surfacing the underlying need. "I need four engineers for six weeks" is an anchor that immediately puts the other party in a position of defending their capacity. "We need to hit X outcome by Q4 and I'm trying to understand what paths exist to get there" opens the negotiation differently. Leaders who anchor early tend to get into a positional dispute rather than a problem-solving conversation, and they're often surprised when the other party doesn't move.
Underweighting what matters to the other party. VPs consistently describe their needs with more precision than they describe the other party's needs. In simulation sessions, we see leaders who can articulate their own situation in detail but who haven't thought carefully about what success looks like for their counterpart — not just what the VP thinks matters to them, but the operational pressures, the competing commitments, the stakeholders that VP has to answer to. When a negotiation goes poorly, it's almost always because one party has made an offer that doesn't adequately account for the other party's actual constraints.
Failing to distinguish between what's possible and what's preferable. In a resource-constrained environment, the range of viable agreements is often narrower than either party realizes going in. VPs who push hard for what's preferable without having mapped what's actually possible tend to create friction and deteriorate the relationship without moving the outcome. The skill of identifying the zone of possible agreement — the range of outcomes that both parties could accept — before proposing anything specific is genuinely valuable and under-practiced.
What Good Cross-Functional Negotiation Actually Looks Like
High-scoring leaders in cross-functional negotiation simulations share a few consistent behaviors that are worth naming precisely.
They front-load information gathering before proposing. Rather than arriving with a solution and trying to close it, they spend the first third of the conversation asking questions about the other party's situation, constraints, and priorities. This is uncomfortable for many VPs because it feels like wasted time when they already know what they need. But the information gathered in that phase consistently changes the shape of the proposal they make, and the proposals that emerge from genuine information-gathering close faster.
They name the tension explicitly. High-scoring VPs are willing to say "I understand we're in a situation where both of our teams are stretched and I'm asking you to stretch further — I want to be honest that I recognize that's a real ask." This kind of explicit acknowledgment is rare in peer-level negotiations because it feels like weakening your own position. In practice it tends to have the opposite effect — it signals that you understand the other party's reality, which reduces defensiveness and opens space for creative problem-solving.
They bring a range, not a point. The most effective negotiators in simulation sessions present options, not a single ask. "Here are three ways we could approach this, with different resource implications for your team" gives the other party agency in how they contribute and often surfaces a path that the VP hadn't anticipated. Single-point asks put the other party in a binary yes/no position, which is the least favorable negotiating structure for a resource-seeking VP.
Why Standard L&D Programs Miss This
We're not saying existing L&D programs are bad at building VP capability. Many of them do excellent work on leadership presence, strategic communication, and manager effectiveness. What they miss — almost universally — is the scenario-based practice component for cross-functional negotiation specifically.
You can't develop negotiation skill from a workshop. You can learn frameworks, understand principles, and gain awareness of your tendencies. But the actual capability — the ability to read a real-time negotiation, identify the zone of agreement, and make a proposal that moves things forward without creating resentment — requires practice in situations that replicate the actual pressure of the conversation.
Consider a director being promoted to VP at a 300-person professional services company. She was well-regarded as a manager — her 360 feedback showed strong scores on team leadership, communication, and strategic thinking. She struggled in the first year as a VP specifically in cross-functional alignment work: she was consistently frustrated that her peers didn't "just agree" with what she needed, and she escalated more than her predecessor had. Her 360 after year one showed the gap. What she'd never received was practice on the structural mechanics of peer-level negotiation — how to surface constraints, how to frame packages, how to get to yes with someone who has equal authority and different priorities.
That's not a personality gap. It's a skill gap that looks like a personality gap because we haven't built the practice infrastructure to develop it explicitly.
Building This Into a Development Program
For L&D directors thinking about how to address this gap directly: cross-functional negotiation needs to be treated as a named skill with named behavioral competencies, not a subcomponent of "relationship building" or "executive presence." The behavioral indicators are specific and scoreable: how early do they anchor, how much time do they spend on information gathering before proposing, how precisely do they characterize the other party's constraints, do they bring options or a single ask.
Practice needs to include a realistic counterpart — someone or something that will push back, surface constraints, and decline inadequate proposals. A role-play with a well-briefed colleague can work. A simulation with a scenario-driven interlocutor works better, because the social dynamics of practice with a colleague (the reluctance to be genuinely adversarial, the knowledge that it's pretend) tend to soften the scenario in ways that reduce the learning value.
The goal isn't to produce VP-level leaders who are skilled negotiators in the formal contract-negotiation sense. It's to produce leaders who can navigate resource-constrained peer-level conversations without either capitulating or escalating — who have a repertoire of moves for situations where the answer is "no" or "not right now," and who can find the viable agreement space faster than they currently do.
That capability is teachable. It's just not being taught, and the gap is showing up as execution friction in almost every cross-functional organization above a few hundred people.