apply-upward-influence

Apply Upward Influence

Build an effective working relationship with your own manager, align proactively on priorities, and influence decisions and resources through understanding your manager's goals and pressures — rather than waiting for direction or escalating needs reactively.

Why This Is Best Practice

Adopted by: Gabarro & Kotter's "Managing Your Boss" (HBR, 1980) is one of the most-reprinted articles in Harvard Business Review history and is taught in MBA programs at HBS, Wharton, and Stanford GSB as foundational management practice; Hill & Lineback's "Being the Boss" (2011) is Harvard Business Review Press's top-selling leadership book for new managers; McKinsey's leadership development programs explicitly include upward relationship management as a skill domain; the US Army's leader development doctrine includes "mission command" — operating effectively within the intent of the next level up — as a foundational leadership competency Impact: McKinsey's research on leadership effectiveness (2015, 189 leaders) found that the most effective leaders spent 25–40% of their relationship investment managing upward and laterally — not only downward; DDI's Global Leadership Forecast (2018, 25,000 leaders) found that leaders who proactively managed their relationship with their own manager had 30% higher team engagement scores and were 2× more likely to receive high-quality support for their team's resource needs; Gabarro & Kotter's original research found that managers who failed to manage the boss relationship systematically had their team's performance constrained by resource starvation, blocked decisions, and misaligned priorities Why best: The default management posture is to focus entirely downward — on the team — and treat the relationship with one's own manager as largely passive (wait for direction, respond to requests, escalate only when blocked); this posture systematically disadvantages the team because resource allocation, priority setting, and career advancement decisions all flow through the manager's manager; proactive upward relationship management converts this process from a lottery into a managed system

Sources: Gabarro & Kotter "Managing Your Boss" (Harvard Business Review, January 2005 reprint); Hill & Lineback "Being the Boss" (HBS Press, 2011); Cohen & Bradford "Influence Without Authority" (Wiley, 2005); McKinsey "Decoding Leadership" (2015)

Steps

1. Map your manager's goals, pressures, and working style

You cannot manage a relationship you don't understand. Before you can align effectively, map:

Goals and priorities:

• What are your manager's top 3 objectives for the year?
• What would make them look good to their manager?
• What decisions do they need to make in the next quarter that your team's work affects?

Pressures and constraints:

• What organizational dynamics are they navigating? (budget, stakeholder conflict, strategy uncertainty)
• Where do they feel under-resourced or exposed?
• What problems do they wish would go away?

Working style:

• How do they prefer to receive information? (brief verbal summary, detailed written update, dashboard)
• Do they prefer to be involved early or only at decision points?
• What level of directness do they expect and welcome?

If you don't know, ask directly: "I want to make sure I'm giving you information in the way that's most useful to you. How do you prefer to stay informed about [team work]?"

2. Provide information before they have to ask

The most powerful upward influence practice is also the simplest: surface relevant information proactively before your manager has to ask for it.

When your manager asks "what's the status of X?" they are expressing information deficit — they needed this information and didn't have it. This creates anxiety, reduces trust, and prompts more check-ins. When you surface the information before they need it, you signal organizational awareness and reduce their cognitive load.

Weekly written update (most effective format):

[Team name] — Week of [date]
Priority summary: [2-3 bullets on key work moving forward]
Risks/decisions needed: [anything that requires their awareness or action]
Results: [any completed work worth noting]

Sent at the same time each week, this becomes a reliable signal rather than an interruption when problems arise.

What to include:

• Progress on priorities your manager cares about
• Risks you are managing — including ones you haven't resolved yet
• Decisions you need from them, clearly framed (not open-ended)

What NOT to include:

• Operational details they don't need
• Problems without your proposed approach
• Information that makes you look good but isn't relevant to their priorities

3. Bring problems with your proposed solution

The most costly upward interaction pattern: escalating a problem with no recommendation. This transfers the cognitive burden to your manager, requires them to gather context they don't have, and signals that you lack the judgment to propose a path forward.

The practice:

Instead of: "We have a problem with the vendor timeline and I'm not sure what to do."
Use: "The vendor timeline slipped 3 weeks. I see two options: 
(1) descope feature X and ship on time, or 
(2) take the 3-week delay and ship complete. 
My recommendation is option 1 because [reason]. Do you agree?"

This framing: gives them the information, gives them your judgment, and requires only a yes/no/different-option response — not problem-solving from scratch.

4. Align on priorities before conflicts emerge

The highest-value upward alignment conversation happens before work is in flight, not after it has already conflicted with something your manager assumed was happening.

Monthly priority alignment (10–15 min agenda item in your one-on-one):

"I want to make sure my team's priorities match what you need from us. 
Here's what I think our top 3 priorities are this month. 
Does that match your view, or should we shift anything?"

This is especially critical when your manager is under pressure, because they may have shifted priorities in response to stakeholder demands without explicitly telling you. Surfacing this proactively prevents discovering the misalignment when the deliverable is due.

5. Build credibility through small commitments before large asks

Influence is a function of credibility, and credibility is built through delivered commitments over time. Before making a large ask (additional headcount, budget, organizational change), build a track record of small commitments kept:

• Make explicit commitments: "By our next meeting, I'll have [X]."
• Deliver them, or proactively communicate early if you can't.
• Each kept commitment is a credibility deposit.

When you need to make a significant ask, your track record of reliability is the primary evidence that you will use the resource well. Managers who are unreliable on small commitments have their large asks discounted or denied not because the ask is unreasonable but because the manager is not trusted to execute.

6. Advocate for your team — not for yourself

Upward influence done in service of your team's needs produces organizational outcomes and builds trust. Upward influence done in service of your own advancement signals self-interest and generates resistance.

Frame advocacy upward in terms of organizational outcomes:

"We need an additional engineer to hit the Q3 deadline. Without it, 
we'll miss the launch window and [specific organizational impact]. 
With it, here's what we can deliver [specific outcome]."

Not:

"I really need more resources — my team is stretched."

The first frame connects the ask to outcomes your manager cares about. The second frame makes the manager weigh your desire against the organization's competing needs — a less favorable comparison.

Rules

• Send a weekly written update before they ask — proactive information delivery reduces anxiety, builds trust, and positions you as a reliable partner rather than a managed subordinate
• Bring problems with your proposed solution — transferring a problem without a recommendation transfers your cognitive load to your manager; they hired you for your judgment
• Align on priorities monthly before conflicts emerge — assuming priorities are stable until told otherwise is how you discover misalignment at delivery, not at planning
• Build credibility through small commitments before large asks — your track record on small things is the evidence base for large requests
• Advocate for the team, not for yourself — resource and decision requests framed in organizational outcomes get a more favorable hearing than those framed in personal need

Common Mistakes

• Avoiding the manager relationship: treating your manager as a necessary burden rather than a key organizational relationship; the team pays the cost in under-resourced, under-supported work.
• Escalating only when blocked: by the time a problem requires escalation, the manager's options for helping are limited; early signal while options are still open is more valuable.
• Inconsistent communication pattern: updating your manager heavily when things are going well and going silent when they're difficult; the inverse is what builds trust — consistent communication with early risk flags.
• Making asks without context: "I need X" without explaining why, what it enables, and what the cost of not having it is; incomplete asks are denied by default.
• Trying to hide problems until resolved: managers who discover problems late feel ambushed; early "here's a risk we're managing, here's our approach" is almost always received better than a late "we have a problem."

When NOT to Use

• When your manager is behaving in ways that are genuinely unethical or abusive — the appropriate path is HR, not influence; upward influence is for managing a functional relationship, not tolerating harmful behavior.
• As a substitute for doing the actual work — no amount of upward communication management compensates for a team that consistently misses deliverables; the foundation is delivery, the upward relationship amplifies its impact.