Managing Up: What Executives Actually Want to Hear

Early in my career, I'd walk into executive meetings with 15-slide decks full of sprint metrics, technical details, and Gantt charts. Executives would nod politely and then ask, "So are we on track?" I'd realize I'd spent 20 minutes not answering the only question that mattered.

The executive translation layer

Executives don't care about your sprint velocity. They care about three things: Are we on track? What are the risks? What do you need from me?

Everything else is supporting detail. Lead with answers, follow with evidence.

Instead of: "We completed 47 story points this sprint, which is above our rolling average of 42, and we have 3 tickets carrying over due to a dependency on the API team."

Say: "We're on track for the August release. One risk: the API dependency could slip the payments feature by a week. I'm working with the API team lead to mitigate, but I may need you to escalate if it's not resolved by Friday."

Frameworks I use

BLUF (Bottom Line Up Front). Military communication style. The first sentence of every email or update should be the conclusion. Details follow for those who want them.

Red/Amber/Green with commentary. RAG status works when you're honest. The PM who marks everything green and then surprises leadership with a delay loses trust permanently. I'd rather flag amber early and resolve it than pretend everything's fine.

Risk register, updated weekly. I maintain a simple risk log that executives can scan in 30 seconds. Risk, likelihood, impact, mitigation, owner. That's it.

The credibility balance

You need engineers to trust you understand the technical reality. You need executives to trust you can translate that into business impact. That translation skill — not project tracking, not Jira expertise — is the core PM competency.

Learn to speak both languages fluently. Your career depends on it.