Managing Up & Stakeholder Relationships

Key Dimensions

Dimension	Effective	Ineffective
Communication	Proactive, structured, audience-aware	Reactive, detail-heavy, one-size-fits-all
Trust	Built through reliability and transparency	Assumed or demanded
Alignment	You know your boss’s priorities and constraints	You operate in a silo and are surprised by decisions
Influence	Shape decisions before they’re made	React to decisions after they’re finalized
Visibility	Your team’s work is known by the people who matter	You assume good work speaks for itself (it doesn’t)
Expectations	Explicit, negotiated, documented	Implicit, assumed, discovered only when violated

Understanding Your Boss

The single most important skill in managing up is understanding what your boss actually cares about — not what they say they care about, but what they’re measured on, what keeps them up at night, and what they need from you.

Questions to answer about your boss:

Question	Why It Matters
What are they measured on?	Their incentives shape what they’ll support
What are they worried about?	Reduce their anxiety and you earn trust
How do they prefer to receive information?	Email? Slack? In-person? Slides? (Mismatch = friction)
What’s their decision-making style?	Data-driven? Consensus? Instinct? (Adapt your approach)
What’s their relationship with their boss?	Understanding the chain above you reveals hidden pressures
What have they been burned by before?	Past trauma shapes current risk tolerance
What do they not want to be surprised by?	“No surprises” is universal — but their definition of “surprise” varies

The “manager README” approach:

Some managers write a README about their working style — preferences, pet peeves, communication norms. If your boss has written one, read it carefully. If they haven’t, reverse-engineer it by observing: when do they get frustrated? When do they light up? What prompts them to reach out proactively?

Adapting to different boss types:

Boss Type	What They Need From You	What Frustrates Them
The detail-oriented boss	Thorough data, well-structured docs, anticipated questions	Vague updates, hand-waving, “trust me”
The big-picture boss	Executive summary first, details on demand	Long emails, getting pulled into weeds
The consensus-builder	Pre-alignment with stakeholders, options with tradeoffs	Unilateral decisions, surprises in meetings
The decisive boss	Clear recommendation with rationale, bias for action	Open-ended “what should we do?” without a proposal
The insecure boss	Visible loyalty, making them look good, no public disagreement	Being upstaged, hearing about your work from their peers first
The absent boss	Self-sufficiency, proactive updates, escalating only when needed	Constant asks for direction, inability to operate independently

Executive Communication

The pyramid principle (Barbara Minto):

Executives don’t have time for bottom-up reasoning. Lead with the conclusion, then provide supporting evidence on demand.

Bottom-up (how engineers think): “We analyzed 3 options. Option A has these tradeoffs… Option B has these tradeoffs… Option C has these tradeoffs… Therefore we recommend Option B.”

Top-down (how executives need to receive information): “We recommend Option B because it reduces latency 40% with minimal migration risk. We evaluated three options — here’s the tradeoff table if you want depth.”

The “5-15” report:

Takes 15 minutes to write, 5 minutes to read. A weekly status update format that many executives prefer:

1. Top 3 things going well (with metrics where possible)
2. Top 3 risks or blockers (with proposed mitigation)
3. Key decisions needed (with your recommendation)
4. Team health (one sentence — “Team is energized” or “Team is stretched thin on project X”)

Presenting to leadership:

Before the meeting:

• Pre-wire key stakeholders — never present a controversial proposal for the first time in a big meeting. Socialize it 1:1 first. The meeting should be for ratification, not discovery.
• Know the decision-maker — who in the room actually decides? Tailor your message to them.
• Anticipate objections — prepare answers for the 3 most likely pushbacks. If you can’t answer “what if this fails?” you’re not ready.

During the meeting:

• State your ask upfront — “I need a decision on X” or “I’m sharing this for awareness, no action needed.” Executives are annoyed when they don’t know why they’re in a room.
• Use the “so what?” test — for every slide, ask: “Does the audience need this to make their decision?” If not, cut it or move it to the appendix.
• Answer questions directly — “Yes, but…” is better than a 3-minute preamble. If you don’t know, say “I’ll follow up by Thursday.”
• Read the room — if the decision-maker is already convinced, stop selling. If they’re skeptical, address their concern directly rather than continuing your prepared slides.

After the meeting:

• Send a decision summary within 24 hours — “We decided X. [Person] owns next steps. Timeline: Y.”
• Follow through visibly — the fastest way to build executive trust is doing what you said you’d do, on time, every time.

Influence Without Authority

As an Engineering Manager, many of the people you need to influence don’t report to you: product managers, designers, other engineering teams, platform teams, architects, security, compliance.

The currency of influence:

Influence is not persuasion — it’s accumulated trust, credibility, and reciprocity. You build influence before you need it.

Currency	How to Build It	How to Spend It
Expertise	Demonstrate deep knowledge, share insights, help others solve problems	“Based on our experience with X, I’d recommend…”
Reliability	Deliver on every commitment, no matter how small	“We’ll take this on — we’ve always delivered”
Network	Build relationships across the org, connect people	“Let me connect you with [person] who can help”
Reciprocity	Help others first, without keeping score	“We supported your team last quarter — we need support now”
Information	Share relevant context proactively	“I have data that might change how we think about this”

The RACI model for stakeholder alignment:

Role	Definition	Key Behavior
Responsible	Does the work	Needs clarity on what “done” looks like
Accountable	Makes the final decision (one person only)	Must be explicitly identified — ambiguity here causes paralysis
Consulted	Provides input before the decision	Must be consulted genuinely, not performatively
Informed	Told after the decision is made	Don’t confuse with Consulted — they don’t get a vote

The common failure: No clear A (Accountable). When three people think they’re accountable, you get design-by-committee. When no one is accountable, decisions don’t get made.

Navigating disagreements with peers:

Step 1: Understand their constraints. Before you push your position, genuinely understand theirs. Product wants to ship fast because they have a board commitment. Security wants to slow down because they were burned by a breach. Both are rational given their context.

Step 2: Find the shared goal. “We both want to ship a reliable product to customers. The question is how to sequence security review without blocking the launch timeline.”

Step 3: Propose a solution that addresses both concerns. “What if we ship to 5% of users behind a feature flag while the security review runs in parallel? We meet the launch date and the security bar.”

Step 4: Escalate with data, not emotion. If you can’t align, escalate to your shared manager with a clear framing: “Here’s where we agree, here’s where we disagree, here’s what I recommend and why, here’s what [peer] recommends and why. We need a decision.”

Building Trust with Skip-Level Leadership

Your relationship with your boss’s boss (and above) matters for: your team’s visibility, your career, your ability to shield your team from bad decisions, and your access to strategic context.

What skip-levels want from you:

What They Want	What They Don’t Want
Crisp status without being asked	Detailed updates on every task
Early warning on risks	Surprises (“I just found out we’re 6 weeks behind”)
Solutions, not just problems	“This is broken, what should I do?”
Confidence that your area is handled	Having to dive into your area to check on things
Occasional strategic insight	Only operational updates

How to build the relationship:

1. Deliver consistently — the foundation. No shortcut.
2. Send the occasional proactive insight — “I noticed a pattern across our 3 teams that suggests we should rethink our on-call model. Here’s a one-pager.” This demonstrates strategic thinking without being asked.
3. Be helpful in their meetings — when you’re in a meeting with your skip-level, add value. Don’t just sit there. Ask a good question, offer a data point, connect dots they might not see.
4. Don’t skip your boss — never go around your direct manager to their boss without telling your manager first. This is a trust-destroying move that rarely works. If you need to escalate, tell your boss: “I’d like to share this directly with [skip-level] because [reason]. Are you comfortable with that?”
5. Be the person who gives honest assessments — skip-levels are surrounded by optimism bias. If you’re consistently honest about risks and timelines, you become a trusted sensor.

Managing Expectations

The expectation gap:

Most manager-to-senior-leader friction comes from misaligned expectations. The manager thought they were doing great; the VP expected something different. This is almost always a communication failure, not a performance failure.

How to manage expectations proactively:

1. Clarify success criteria at the start of every initiative — “What does success look like for this project? What would you be disappointed by?” Get this in writing.
2. Provide regular progress updates against those criteria — don’t wait to be asked.
3. Signal risk early — “We’re on track for the MVP scope, but the stretch goal for Q2 is at risk because of [reason]. Here’s my mitigation plan.”
4. Renegotiate when scope or context changes — “The original plan assumed we’d have 4 engineers. We have 3. Here are the options: (a) reduce scope, (b) extend timeline, (c) add a contractor. I recommend (a). What’s your preference?”
5. Under-promise, over-deliver (selectively) — this is a cliche because it works. Build 20% buffer into timelines. Deliver the buffer as “ahead of schedule” or use it to absorb surprises.

The “bad news” delivery formula:

Delivering bad news is a critical leadership skill. Most managers either sugarcoat (losing credibility) or dump it bluntly (causing panic). The formula:

1. State the fact — “We’re going to miss the June launch date by 3 weeks.”
2. Explain why (briefly) — “The payment integration is more complex than scoped — we discovered a regulatory requirement in the EU flow that requires additional work.”
3. Share what you’ve already done — “We’ve re-scoped the EU flow and are running parallel workstreams to minimize the delay.”
4. Present options — “We can launch on time without EU, then add it in a fast-follow. Or delay 3 weeks for full scope. I recommend the first option.”
5. Ask for input — “What are your thoughts? Is there context I’m missing?”

This formula works because it demonstrates ownership, proactivity, and judgment — even while delivering disappointing news.

Organizational Politics — The Reality

“I don’t do politics” is not a viable position for a senior leader. Politics is the process by which decisions get made in organizations with multiple stakeholders and limited resources. Ignoring it means other people make decisions about your team’s priorities, resources, and strategy.

Constructive political behaviors:

Behavior	Example	Why It’s Not Manipulation
Coalition building	Aligning with 2-3 peer managers on a shared infrastructure investment before the budget meeting	You’re building support for something you believe is right
Information sharing	Proactively sharing your team’s learnings with adjacent teams	You’re creating organizational knowledge
Framing	Presenting your AI platform work as “risk reduction” to a risk-averse VP	You’re translating your work into language that resonates
Timing	Proposing a new initiative right after a successful launch, not right after a failure	You’re reading context
Relationship investment	Having coffee with a peer from a different org quarterly	You’re building trust before you need it

Destructive political behaviors (things to never do):

• Information hoarding — using information asymmetry for personal advantage
• Credit-taking — presenting your team’s work as your own
• Sabotage — undermining a peer’s initiative to make yours look better
• Gossip — talking about people instead of talking to people
• Loyalty tests — forcing people to choose sides

When your boss is the problem:

Sometimes managing up means managing a boss who is bad at their job — disorganized, micromanaging, politically focused, or just absent.

If they’re disorganized: Create structure they don’t — write the agenda, send the summary, track the action items. You become their operating system.

If they micromanage: Proactively over-communicate until they trust you. Send updates before they ask. Share your reasoning before they question it. Most micromanagement is anxiety-driven — reduce the anxiety.

If they take credit: Document everything in writing (shared docs, emails). Create visibility for your team independently (demo days, blog posts, cross-team presentations). If it persists, address it directly: “I noticed the exec review attributed the platform work to the broader org. My team led that end-to-end and I’d like them to get recognition.”

If they’re absent: Treat it as a gift. You have autonomy. Use it to build your team’s capabilities, make decisions confidently, and create your own executive visibility. The risk: when something goes wrong, they’ll appear and want to control. Prepare for that by keeping them informed even when they’re not asking.

If they’re genuinely toxic: Escalate to HR or your skip-level. Document specific behaviors. If the org doesn’t act, start planning your exit — you cannot grow under a toxic boss, and staying too long damages your judgment and health.

The Stakeholder Map

For any major initiative, map your stakeholders:

Stakeholder	Interest Level	Support Level	Strategy
Champion	High interest, high support	Keep engaged, leverage their support	VP who sponsored the initiative
Blocker	High interest, low support	Understand their concerns, address directly	Security lead worried about risk
Ally	Low interest, high support	Keep informed, activate when needed	Peer manager who benefits
Bystander	Low interest, low support	Minimal investment, don’t antagonize	Teams not affected

The key insight: Most managers spend too much time convincing Champions (who are already on board) and ignoring Blockers (who can kill the initiative). Flip it: spend your political capital on Blockers.

Anti-Patterns in Managing Up

Anti-Pattern	What It Looks Like	Why It Fails
The mushroom	Never sharing bad news upward	Surprises destroy trust faster than anything
The yes-person	Agreeing to everything, never pushing back	Over-committed, under-delivered, not respected
The martyr	“My team is working so hard” without asking for help	Leadership doesn’t know you need resources if you don’t ask
The end-run	Going to your boss’s boss without telling your boss	Destroys your manager relationship permanently
The pessimist	Every update is a list of problems	Leadership stops listening, finds someone more solutions-oriented
The invisible	Assuming good work speaks for itself	It doesn’t. Your team’s work is invisible until you make it visible.
The complainer	Escalating problems without proposed solutions	You’re seen as someone who creates work, not someone who handles it

References

Books

• The Minto Pyramid Principle — Barbara Minto (executive communication, top-down structure)
• Influence Without Authority — Cohen & Bradford (the reciprocity model of influence)
• The First 90 Days — Michael Watkins (managing up in a new role)
• Crucial Conversations — Patterson, Grenny, et al. (high-stakes stakeholder conversations)
• An Elegant Puzzle — Will Larson (managing up as an engineering leader)
• High Output Management — Andy Grove (organizational leverage)
• The Culture Map — Erin Meyer (managing across cultural contexts — essential in Germany)

Research & Articles

• “Managing Your Boss” — Gabarro & Kotter, HBR (1980, updated 2005) — the classic paper
• “What Leaders Really Do” — John Kotter, HBR — leadership vs. management
• Lara Hogan — “Navigating Power Dynamics” (blog, practical framework)
• Will Larson — “Staff Engineer: Leadership beyond the management track” (influence without authority for ICs)

Talks

• Julie Zhuo — “The Making of a Manager” (talks on executive communication, expectation management)
• Charity Majors — “The Engineer/Manager Pendulum” (navigating organizational dynamics)
• Simon Sinek — “Leaders Eat Last” (trust-building with leadership, controversial but useful framing)