Technical Presentation Tactics for Executives

- A frequently cited Microsoft study suggests the average human attention span has fallen to eight seconds, underscoring the need for concise and impactful presentations. For presentations to uninterested audiences, you may only have seven seconds to capture their attention. - Frameworks like PREP (Point, Reason, Example, Point) and BLUF (Bottom Line Up Front) are designed to structure communication for executives by stating the main argument immediately. The BLUF model is considered by some to be the most critical communication framework for engineers when speaking with senior leaders. - The "What? So What? Now What?" framework is another tool to translate data into a clear narrative for leadership, forcing the presenter to explain the significance of the information and propose a course of action. - A tragic example of failed technical communication is the 1986 NASA Challenger disaster, where engineers presented slides with dense, complex data about O-ring malfunctions that failed to convey the critical risk to decision-makers. - Up to 73% of data-heavy presentations reportedly fail to lead to a decision because they are structured for analysis rather than for an executive audience that prioritizes recommendations. Leading with data can even reduce a presenter's credibility with executives, as it may signal a lack of understanding of their priorities. - When presenting to executives, a common guideline is the 10/20/30 rule: no more than 10 slides, lasting no longer than 20 minutes, and using a font size of at least 30 points. - An effective tactic for translating technical concepts is to use analogies, such as comparing a data lake to a real lake that collects water from various sources, to make the information more relatable to a non-technical audience. - Studies have shown that when facts are presented as part of a story, people are 22 times more likely to remember them, highlighting the power of narrative in technical presentations.