Stakeholder Communication

Why This Matters for Engineering Leaders

As an EM at MMS with 16 engineers, you have multiple stakeholder layers: your VP/CTO, product leadership, peer EMs, business stakeholders, and your own team. Each group needs different information at different cadences. Getting this wrong means either your leadership doesn’t trust you (too little info, too late) or they think you’re drowning (too much detail, too often).

BLUF: Bottom Line Up Front

The single most important communication principle for stakeholder updates.

The Pattern

[The bottom line -- decision, status, risk, or ask]
[Context that supports the bottom line]
[Details for those who want to go deeper]

BLUF by Communication Type

Type	BLUF Example
Status update	“Project X is on track for May 15 launch. One risk: vendor API integration is 3 days behind. Mitigation in place.”
Escalation	“We need to delay the release by one week. Root cause: critical bug found in payment flow during load testing. Proposed new date: April 22.”
Decision request	“I need your approval to hire a senior backend engineer. The current team is at capacity and the AI platform work requires specialized skills we don’t have.”
Bad news	“We missed the Q1 OKR for API response time. We achieved P95 of 350ms against a target of 200ms. Here’s our plan to close the gap in Q2.”

Why Engineers Struggle with BLUF

Engineers are trained to show their work: gather data, analyze, conclude. This is “bottom line at the end” – the exact opposite of what executives need. Executives want to know the answer first, then decide whether to dig into the reasoning. Reversing the order of your natural thought process is the highest-leverage communication change you can make.

Executive Updates

What Executives Actually Want to Know

Question	What They’re Really Asking
“How’s the project going?”	“Should I be worried? Do I need to intervene?”
“What’s the timeline?”	“Will we hit the date? If not, how bad is it?”
“What do you need?”	“What decision or resource am I blocking?”
“Tell me about the team”	“Do I need to worry about attrition or performance?”

The Executive Update Template

Use this structure for any steering committee, 1:1 with your VP, or written status report:

## Status: [Green / Yellow / Red]

### Headlines (3 max)
1. [Biggest win or progress point]
2. [Biggest risk or blocker]
3. [Key decision needed or upcoming milestone]

### Metrics
- [KPI 1]: [current] vs [target] -- [trend]
- [KPI 2]: [current] vs [target] -- [trend]

### Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation | Owner |
|------|-----------|--------|------------|-------|

### Decisions Needed
- [Decision 1]: [Options, your recommendation, deadline]

### Next 2 Weeks
- [Key milestone 1]
- [Key milestone 2]

Traffic Light Integrity

Color	Meaning	When to Use
Green	On track, no intervention needed	Everything is progressing as planned
Yellow	At risk, mitigation in progress	You’ve identified a risk and are handling it. Exec should be aware but doesn’t need to act
Red	Off track, need help	You need a decision, resource, or intervention from leadership

Critical rule: Never surprise your leadership with a Red. If a project goes from Green to Red in one update, you failed at stakeholder communication. Projects go Green -> Yellow -> Red. The moment you see Yellow, communicate it.

The “No Surprises” Principle

Your VP should never learn about a problem from someone else. If there’s bad news, they should hear it from you first. This is not about covering yourself – it’s about giving your leadership the context they need to respond effectively if asked.

Rule of thumb: If you’re debating whether to escalate something, escalate it. Under-communication is almost always more damaging than over-communication with executives.

Managing Up

What Managing Up Actually Means

It’s not sucking up. It’s understanding your manager’s goals, constraints, and communication preferences, and adapting your communication to be maximally useful to them.

The Manager Operating Manual

Know these about your manager:

Dimension	Questions to Understand
Communication preference	Slack or email? Detailed or headlines? How often?
Decision style	Do they want options + recommendation, or just the recommendation?
Risk tolerance	Do they want to know about every Yellow, or only Red?
Meeting preference	Do they prefer written pre-reads or live discussion?
What keeps them up at night	What are THEIR stakeholders asking about?
How they define success	What metrics matter to them?

Framing Problems vs. Solutions

Never bring just a problem. Always bring a problem + your analysis + your recommendation.

Level	What You Say	How It Lands
Junior	“We have a problem”	You’re creating work for your manager
Mid	“We have a problem and here are 3 options”	You’ve done some thinking but want them to decide
Senior	“We have a problem. I recommend Option B because [reasoning]. I’d like your input before proceeding”	You’ve thought it through, have a point of view, and are seeking alignment

The Escalation Framework

Severity	When	How	Example
Inform	FYI, no action needed	Async (email/Slack), next regular update	“We had an incident last night, resolved in 30 min, no customer impact”
Consult	Need input but you’ll decide	1:1 or async, within 24h	“I’m considering two approaches for the migration. Here’s my thinking…”
Escalate	Need their help or decision	Synchronous (call/meeting), ASAP	“The vendor is threatening to terminate the contract. I need you to intervene at VP level”

Status Reporting

Weekly Status Report (for Your Manager)

Keep it to a single Slack message or short email:

## Week of [Date]

**Wins:**
- [Achievement 1 -- with impact/metric]
- [Achievement 2]

**Risks:**
- [Risk + mitigation + owner]

**Needs:**
- [Decision or resource you need from them]

**Next week:**
- [Top 2-3 priorities]

Monthly Business Review (for Steering Committee)

More structured, with trends and strategic context:

1. Headline metrics (4-6 KPIs with trend arrows)
2. Accomplishments (tied to OKRs or strategic initiatives)
3. Risks (with Red/Yellow/Green and mitigation status)
4. Resource status (headcount, utilization, key hires)
5. Strategic outlook (what’s changing, what’s coming)

The “So What” Test

For every piece of information in a status report, ask: “So what? Why does this matter to the reader?” If you can’t answer that, cut it.

• “We closed 47 tickets this sprint” – so what?
• “We closed 47 tickets this sprint, clearing the backlog that was blocking the Q2 launch” – that matters.

Communication Cadence

Recommended Cadence by Stakeholder

Stakeholder	Cadence	Format	Content
Your manager	Weekly	1:1 + async update	Headlines, risks, decisions needed
Skip-level (VP/CTO)	Bi-weekly or monthly	Meeting or written brief	Strategic progress, team health, key decisions
Peer EMs	Weekly	Team sync or Slack	Dependencies, shared risks, coordination
Product counterpart	Daily/weekly	Standup + weekly sync	Sprint progress, blockers, scope questions
Your team	Daily + weekly	Standup + team meeting	Context, priorities, recognition
Business stakeholders	Monthly or quarterly	Business review	Outcomes, metrics, roadmap

Adjusting Cadence by Project Phase

Phase	Increase Communication To	Why
Launch / go-live	Daily updates to all stakeholders	High risk, fast-moving, decisions needed quickly
Crisis / incident	Real-time to leadership, hourly to business	Trust requires transparency when things break
Steady state	Standard cadence	No news is good news, but don’t go silent
Reorg / change	2x normal frequency	Uncertainty breeds anxiety; communication fills the vacuum

Anti-Patterns

1. The Information Dump

Sending your VP a 3-page status update with every detail. They stopped reading after the second sentence. Give headlines, link to details for those who want them.

2. The Green-to-Red Surprise

A project that was “green” last week is suddenly “red” this week. This means you either weren’t tracking risks or you weren’t communicating them. Either way, trust is damaged.

3. Translating Down Instead of Up

Using the same language and framing with your VP that you use with your engineers. Executives think in business outcomes, timelines, and risk – not sprint velocity, tech debt ratios, or PR cycle times.

4. Not Having a Point of View

Presenting “options” without a recommendation. Your stakeholders hired you for your judgment. Use it. “Here are three options. I recommend B because [reasoning].”

5. Over-Delegating Communication

Having a PM or TL present to the steering committee when you should be there. As the EM, you own the team’s narrative. Be present for important moments.

6. Only Communicating When Things Go Wrong

If your VP only hears from you when there’s a problem, they’ll start assuming every message is bad news. Share wins proactively. Build a “trust bank” so that when you do bring bad news, there’s goodwill to draw on.

7. Burying the Ask

Putting your decision request on page 3 of a 5-page document. If you need something from a stakeholder, lead with it. They can’t help you if they don’t know what you need.

References

• Larson, W. (2019). An Elegant Puzzle: Systems of Engineering Management. Stripe Press. – Chapter on managing up and stakeholder communication is excellent.
• Fournier, C. (2017). The Manager’s Path. O’Reilly. – Practical advice on communication at each leadership level.
• Military Communication Handbook. BLUF (Bottom Line Up Front). – The original source of the BLUF concept, used across NATO communications.
• Lencioni, P. (2002). The Five Dysfunctions of a Team. Jossey-Bass. – Chapters on trust and accountability directly connect to stakeholder communication.
• Reilly, T. & Rubin, J. (2022). Staff Engineer: Leadership Beyond the Management Track. – Chapter on “being visible” applies to how EMs communicate value upward.
• Stanier, J. (2020). Become an Effective Software Engineering Manager. Pragmatic Bookshelf. – Concrete templates for status reports and exec updates.