Navigating Upward Influence

Throughout this course, you have built the skills to deliver tough feedback to direct reports, mediate conflict between peers, and communicate major losses with clarity and empathy. Now you are flipping the dynamic entirely. Whether you are requesting headcount, pushing back on an unrealistic deadline, or surfacing a problem no one wants to hear about, your ability to influence upward directly determines how well you can advocate for your team.

The single biggest mistake People Managers make when communicating with executives is treating the conversation the same way they would a team meeting. With your direct reports, you have the luxury of context-setting, exploring ideas collaboratively, and thinking out loud. Executives operate in a fundamentally different mode. Their calendars are compressed, their cognitive load is enormous, and they are making decisions across multiple teams and priorities simultaneously. If you do not adapt your communication style accordingly, your message will get lost — not because it lacks merit, but because it was not packaged for the audience.

The first principle of managing up is to lead with the conclusion, not the journey. Executives want to know the answer before they hear the analysis. This approach is sometimes called the pyramid principle — put the recommendation at the top and let the supporting evidence flow underneath.

Closely tied to this is the principle of speaking in outcomes, not activities. Executives are far less interested in what your team is doing than in what your team is producing. Furthermore, you should always anticipate their questions and come prepared. Senior leaders are trained to probe, challenge, and stress-test ideas. If you walk into a conversation without having thought through the obvious counterarguments, you will lose credibility fast. Before any significant upward conversation, ask yourself what they will push back on, what data they might request, and what risks they will want addressed. You do not need to preemptively answer every question in your initial message, but you need to have the answers ready. The manager who responds to a tough question with "I haven't thought about that yet" is in a very different position from the one who says "Great question — here's how we've accounted for that." Preparation is the foundation of executive presence.

One of the most important (and most uncomfortable) applications of upward influence is advocating for your team's resources. Whether you need additional headcount, a larger budget, or simply relief from an unsustainable workload, the conversation requires you to balance assertiveness with strategic framing. You are not complaining; you are making a business case.

The key to effective resource advocacy is framing the request around organizational risk or opportunity, not team strain. Telling a senior leader "My team is burned out and we really need another person" may be true, but it positions the request as a personnel comfort issue rather than a business imperative. Compare that with "At our current capacity, we can deliver Project A or Project B by Q3, but not both. Adding one senior engineer would allow us to deliver both, which protects approximately $400K in projected revenue." The second version quantifies the trade-off, connects the request to a metric the executive values, and gives them a clear decision to make rather than an emotional appeal to absorb. When you translate team needs into business language, you move from asking for a favor to presenting a strategic investment.

Equally important is your ability to negotiate boundaries when leadership asks for more than is realistic. Senior leaders often push ambitious targets — not out of malice, but because they are operating at a level of abstraction that can obscure ground-level constraints. When you receive a request like "I need your team to take on this additional initiative by end of quarter", your job is not to simply say yes or no. It is to respond with a structured trade-off. Something like "We can absolutely take that on. To hit that timeline, I'd recommend deprioritizing the internal tooling project, which would push that deliverable to Q3. Alternatively, if both are critical, we'd need to bring in contract support for approximately six weeks. Which approach would you prefer?" This response demonstrates commitment, strategic thinking, and respect for the executive's authority to make the final call — while ensuring your team is not set up to fail.

To see what this looks like in practice, consider the following exchange where Jessica, a People Manager, responds to a new demand from her VP, Ryan.

• Ryan: Jessica, leadership wants your team to own the new partner onboarding workflow. We need it live by end of Q2.
• Jessica: I appreciate you bringing this to me directly. My team can absolutely own that. Right now we're committed to delivering the client migration tool by the same deadline, which supports about $300K in renewal revenue. To take on the onboarding workflow at the same quality bar, I see two options: we push the migration tool to mid-Q3, or we bring in a contract developer for eight weeks to run both in parallel. I'd recommend the second path since it protects the renewal revenue. What's your preference?
• Ryan: I didn't realize the migration tool was tied to that revenue number. Let me check the budget for a contractor and get back to you by Thursday.
• Jessica: That works. I'll send you a one-page summary of both options with timelines and cost estimates so you have everything you need for that conversation.

Notice how Jessica never says no. She immediately signals willingness to take on the work, then frames the constraint around a business metric rather than team workload. She presents two clear options, states a recommendation, and leaves the decision with Ryan. His response shows exactly the outcome you are aiming for: instead of seeing a resistant manager, he sees a strategic partner who just gave him the information he needs to make a smart call. Jessica's final line reinforces her credibility by offering to do the preparation work that makes his decision easier.

A critical mindset shift underlies all of this: saying yes to everything is not loyalty — it is a failure of leadership. When you accept every request without surfacing constraints, you are not protecting your relationship with your senior leader; you are quietly setting your team up for burnout and missed targets. And when those targets are missed, the credibility hit falls on you. The managers who earn the most trust from leadership are the ones who are honest about capacity, transparent about trade-offs, and reliable in their commitments.

In the previous lesson, you learned how to deliver hard news downward to your team. Delivering bad news upward to leadership is a different challenge entirely. When you tell your team about a cancellation, you are the authority figure offering context and support. When you tell your executive that a project is off track, a key hire fell through, or a client relationship is deteriorating, you are the messenger. The goal is to deliver the truth in a way that preserves your credibility and positions you as someone who solves problems, not someone who simply surfaces them.

The first rule is to surface bad news early. Nothing erodes executive trust faster than a late surprise. A manager who flags a risk two months before a deadline has time, options, and credibility. A manager who reveals the same problem two days before the deadline has none of those things. Once you have committed to early transparency, the next consideration is how you handle accountability. If the bad news involves something within your sphere of responsibility, own your part without spiraling into self-blame. Take ownership in one sentence, and then immediately shift the conversation to what you are doing about it.

This leads to the most important rule of all: always pair the problem with a proposed path forward. Executives do not want to receive problems as open questions. They want to see that you have already started thinking about solutions. The structure is straightforward: name the issue, give the essential context, and then present one or two options for resolution. For example, "The vendor integration is three weeks behind schedule due to unexpected API changes. I see two paths: we can bring in a specialist contractor to accelerate the work and recover two of those three weeks, or we can adjust the launch date to April 15th and maintain our current team. I'd recommend the first option because it keeps us aligned with the marketing campaign. I'd like your input before we proceed." This approach transforms you from a bearer of bad news into a leader who manages problems proactively.

Coming up next, you will step into a role-play scenario where you negotiate directly with a senior executive who is pushing for significantly more output without additional resources. This is your opportunity to practice framing trade-offs, advocating for your team with data, and maintaining your credibility under pressure — all skills that separate reactive managers from influential leaders.