Executive Communication
Lead with the decision and make the evidence easy to inspect. · Execution & Communication · Lesson 69 · 4 min
Executive Communication · 4 min
Situation
The recommendation arrives on slide seventeen.
An update describes interviews, technical discussions, and delivery history before revealing that a launch date must change. Executives leave unsure what decision is needed.
Senior audiences often need the consequence and ask first. Detail still matters, but it should support the decision rather than obscure it.
Mental model
Headline, decision, evidence, risk, ask.
Start with the main point. State the recommended action or decision. Provide the few facts that make it reasonable. Name the material risk and the support or approval required.
This is not permission to hide uncertainty. Label forecasts and assumptions so a concise message remains honest.
Weak update
Activity without a conclusion.
“We met with engineering, reviewed the API, and discussed several options. Design is making progress, but there are some dependencies and we may need more time.”
The reader cannot tell the impact, choice, or next action. The message makes them reconstruct the recommendation from incomplete clues.
Strong update
Put the choice in the first sentence.
“Recommend moving the automated-report launch by two weeks while keeping Monday's 12-account pilot manual.”
“The vendor API cannot yet supply the required historical data. Support can cover the pilot at four hours per week. Launching automation now would produce incomplete reports. We need approval today for the revised external date and named support coverage.”
Add the risk
Show the condition that could break the plan.
“The manual path is viable only at the pilot volume. If the pilot expands, we must narrow report frequency or delay expansion. We will review capacity after two report cycles.”
This statement helps leadership assess the proposal rather than treating the date change as an isolated delivery problem.
Calibrate detail
Make evidence available without narrating every step.
Link the underlying analysis or include a short appendix. Be ready to explain alternatives and rejected options when asked.
For a routine update with no decision needed, say that clearly and focus on meaningful changes. Do not manufacture an ask simply to fit a template.
Practice
Rewrite a technical status in three sentences.
“The queue backlog is growing and p95 processing time is above target.” Translate that into user impact, recommended action, and the decision required.
A strong answer
Connect the delay to the decision.
For example: “Large uploads are taking longer than our stated processing window. Recommend pausing expansion while engineering increases processing capacity and verifies recovery. We need agreement to delay the next cohort by two days, with timing reviewed tomorrow.”
The message names the user impact, gives a bounded recommendation, and makes the required decision visible.
Remember this
Make the consequence clear before the mechanics.
An executive should quickly understand what changed, why it matters, what you recommend, and what you need. Concision works when it preserves the decision's essential evidence and risk.