ISYS3438 Chap.12 Executive Communication and Delivery
Executive Communication and Delivery
Executive communication translates technical work without weakening its evidence. This chapter begins with audience knowledge, priorities and authority, then builds slides around one message and one supporting visual. It treats tone, pace, eye contact, gesture and timing as delivery mechanisms that reinforce structure.
The worked example compresses a dashboard report into a five-minute board route by keeping the problem, decisive patterns, recommendations and uncertainty while moving technical detail to supporting material.
What this chapter covers
- 01
audience analysis
- 02
message titles
- 03
slide readability
- 04
spoken structure
- 05
body language
- 06
timed rehearsal
Worked example · free
Compress a technical report for the board
- +1Open with the decision and business consequence.
- +1Use an overview and focused evidence for the decisive patterns.
- +1Translate formulas while keeping definitions and uncertainty available.
- +1End with an actionable recommendation and monitoring check.
Key terms
- Audience analysis
- Audience analysis identifies what listeners know, value and can decide.
- Message title
- A message title states the claim or point a slide supports.
- Presentation aid
- A presentation aid is a visible element that supports rather than duplicates spoken content.
- Actionable recommendation
- An actionable recommendation names an action, rationale, owner or next step and a way to evaluate it.
Executive Communication and Delivery FAQ
How much technical detail should executives see?
Show the metric definition, decisive evidence, uncertainty and consequence. Move software syntax and full formulas to supporting material unless the audience must evaluate the method directly.
How can I stay within five minutes?
Rehearse with a timer and remove material that does not change the requested decision. Keep context, decisive evidence and action. Speaking faster reduces comprehension and weakens delivery.
What should the last sentence do?
It should ask for a decision or commit to a next step, while making the evidence link clear. A polite closing can follow, but it should not replace the action.
Assessment move
Record a two-minute explanation of one chart for a technical peer, then record a one-minute version for an executive. Compare what changed and confirm that the metric, evidence and uncertainty survived. Practise message titles and final recommendations aloud until each can be understood without seeing the report. Profile the audience in operational terms.
Record what the executives already know, which decisions they control, the time available and the consequence of acting or waiting. Translate technical work into decision language without removing definitions, denominators or uncertainty. Put calculation syntax and exploratory detail in supporting material, but keep enough method visible for the audience to judge whether the recommendation is credible.
Design each slide around one message title and one main exhibit. Use readable type, strong contrast and restrained colour, then test the slide at presentation distance and in an exported recording. A title should state a supported finding rather than a topic such as “results.” Direct labels reduce travel to legends, and annotations should point to the exact evidence used in speech.
Remove decorative objects that compete with the decision path. Structure delivery as orientation, evidence and consequence. Tell the audience what question the chart answers, pause for reading, then explain the pattern and its boundary. Signpost transitions so a move from overview to subgroup or recommendation is explicit. Maintain steady pace and natural emphasis rather than filling silence.
Body language should support attention to the exhibit without blocking it or relying on a pointer that recording viewers cannot see. Rehearse in the actual format. Time every section, verify pronunciation and test whether charts remain legible after compression. Record one run and note verbal hedges, unexplained acronyms, repeated context and claims not visible on screen.
Cut lower-priority material rather than speaking faster. Prepare concise responses to questions about definition, sample, alternative explanation and implementation. Close with the proposed action, owner, timing, monitoring measure and condition that would trigger reconsideration. Executive confidence comes from a clear evidence trail, not from hiding uncertainty. Prepare a question map alongside the final deck.
Anticipate requests about metric definition, comparison period, data quality, alternative explanation, implementation cost and monitoring. Link each response to a backup exhibit or a concise documented answer. Rehearse moving to and from supporting material without losing the main decision thread. If a question exposes uncertainty, state what is known, what remains unknown and the next check instead of improvising precision.
This preparation improves delivery because confidence comes from traceable evidence and recovery, not memorised wording. It also identifies weak claims before recording, when the visual, recommendation or scope can still be revised. After presenting to a peer, ask for a thirty-second retelling of the recommendation, evidence and limitation. Do not prompt them.
Compare the retelling with the intended message and revise the order or emphasis where it diverges. Successful delivery is measured by an accurate decision trace, not applause, smooth animation or the number of slides completed.