Communicating with Executives: How to Get C-Level Leaders to Listen

How to speak and write to senior leaders so they listen and decide: the BLUF structure, example scripts, common mistakes and a pre-meeting checklist.

You prepared 15 slides to update a director on your project. By slide three, they ask, "So will it be done on time, and what do you need from me?" The remaining slides go unused, and you feel you missed your chance. This happens a lot, because senior leaders have little time and many decisions to make every day. Communicating with them works differently from talking to teammates.

What executives want from you

C-level leaders, VPs and directors usually do not need every step. They want the big picture, the impact, and the decision to be made. If you deliver those three things briefly, they see you as structured and trustworthy. If you ramble, they may cut you off and your credibility drops without you noticing.

Three rules for communicating with executives

1. Lead with the conclusion (BLUF: Bottom Line Up Front)

Do not tell the story in chronological order. Give the conclusion first, then the reasons.

• Does not work: "Yesterday I met team A and they said... then we tried... and in the end the problem was..."
• Works: "Project X will be two weeks late because the vendor missed its delivery. I have two options for you to consider."

2. Use evidence, not feelings

Words like "fairly", "probably" and "I feel" force the executive to ask follow-up questions. Use the numbers or evidence you actually have.

• Does not work: "Customers are fairly unhappy."
• Works (hypothetical example): "Our satisfaction score fell from 45 to 32 this quarter. Most complaints are about delivery time."

3. End with a clear ask

Say clearly what you need them to do and by when.

• "I would like approval for extra budget for a backup vendor by this Friday."
• "Could you speak with team B's lead about staffing?"
• "This is for your information only. No decision needed today."

Example: a five-line executive update email

• Subject: Project X two weeks late, vendor decision needed by Friday
• Line 1: Summary: Project X will finish two weeks behind schedule.
• Line 2: Cause: the main vendor delivered equipment late.
• Line 3: Option A: wait for the current vendor, no extra cost, two weeks late. Option B: use a backup vendor, extra cost, only three days late.
• Line 4: Recommendation: the team recommends option B because a key client is waiting.
• Line 5: Ask: approve option B by Friday.

Notice that an executive who reads only the subject and the first line already knows what happened and what is needed. The rest is there for anyone who wants detail.

Common mistakes

• Hiding bad news at the end: executives want to know about problems early. The later they know, the fewer options remain.
• Bringing a problem without options: offer at least two and say which one you recommend.
• Too much technical jargon: translate it into business impact such as time, cost, risk or customers.
• Guessing when you do not know: "Let me check the numbers and send them by this afternoon" is better than giving wrong information.

Executives do not want every detail. They want a clear insight and the point where a decision is needed.

Where to start: a pre-meeting checklist

1. Write your conclusion in one sentence. If you cannot, you are not ready to walk in.
2. Keep the summary to one page. Put the rest in an appendix for questions.
3. Prepare three scenarios: best, base and worst, with the impact of each.
4. Anticipate questions: "What is the impact?" "Why not the other option?" "Do you need more people or budget?"
5. Rehearse with a timer so your opening takes only a few minutes, then open the floor to questions.

Read more about working with your boss in Managing Up and Presenting to leadership. If you want to draft a script or an email to an executive and make it tighter, try the Plants.work AI Career Assistant. Or, for a view from someone experienced in working closely with executives, talk to a mentor on Plants.work.