How to Write an Executive Summary—What Should be Included?

Executive summaries should function less like compressed paperwork and more like a one-page, reader-specific story that pushes the reader toward a decision or toward reading the full document. The core claim is that most executive summaries fail to stick because they’re too dry, too long, or too generic—especially in a workplace shaped by cognitive overload and “TL;DR culture.” In that environment, a strong executive summary has to be engaging, conversational, and tightly limited to one page while guiding action and understanding.

The discussion starts with why executive summaries often get ignored: people receive enormous volumes of information and spend a large share of the workday reading and writing. A cited McKinsey analysis puts daily email volume at about 120 messages, with roughly one-third of the workday tied to email. Combined with longer annual work time since the 1980s, that pressure creates cognitive overload—when the brain effectively shuts down because it’s forced to juggle too many stimuli at once. The proposed cultural response is “TL;DR culture,” where readers expect fast, digestible, non-boring takeaways.

To make that expectation concrete, the talk points to “Idea in Brief” sections in Harvard Business Review as an example of how busy readers can either get the needed insight without reading the full article or decide to keep reading because the mini narrative makes the larger piece feel relevant. Another example is a broader shift toward more conversational workplace communication—less jargon, more story—framed through the contrast between “weekend language” (storytelling with friends) and “weekday language” (robotic, technical phrasing). The underlying message: when writing sounds like a negotiation between real people rather than a report of abstract terms, readers process it more easily.

From there, the talk defines what an executive summary is and why it exists. It’s a short, one-page story of a longer business document used across contexts like legal briefs, product descriptions, and market research reports. Its purpose is twofold: it sells the document (without which readers won’t invest time in an 80-page report) and it choreographs the reader’s next step—either making a decision immediately (buy, approve, proceed) or motivating the reader to read the full document for more detail.

Two principles anchor the approach. First, start with the reader: identify who is reading, why they’re reading, what power dynamics are in play (who decides, who pulls levers), and what stakes and urgency matter. Second, tell an engaging story—but “story” here means organizing problems and solutions in a way that’s memorable and retellable, not writing a dramatic narrative. The talk emphasizes “sexy stuff” inside that story: illuminating examples, compelling statistics, and clear conclusions.

A simple three-part template ties everything together: (1) the problem, (2) the solution, and (3) the benefit—framed as “what could be.” A hypothetical example about internal communication at a company (“Iconics”) illustrates how quotes and statistics can make the problem vivid, how signposting (“three things”) can keep the reader oriented, and how benefits like revenue impact and improved satisfaction give the reader a reason to act.

In the Q&A, the guidance extends to practical choices: different audiences may need different executive summaries (client-facing vs. internal manager-facing), presentations can use the same problem/solution/benefit structure with more slides for the problem, and the model can also help with abstracts and even emails. The overall takeaway is consistent: chunk information so readers can focus, keep the language accessible, and design the summary so it’s readable “in airplane mode”—understanding it without links or extra context.