C1 Level · Business Writing
A CEO receives 200+ emails a day. A board member sits in 8+ hours of meetings weekly. An executive has 4 minutes to understand whether your proposal deserves 40 minutes of their time. They're not lazy — they're time-constrained. An executive summary is not a courtesy. It's a survival tool.
A well-written summary tells an executive:
Research shows executives spend an average of 1.5 minutes per document. In that time, they need to decide: Is this important? Do I need to read the whole thing? Can I delegate? The summary determines their decision.
An executive summary is not a condensed version of the document. It's a standalone argument. Someone should be able to read only the summary, understand the recommendation, and make a decision.
Most people write conclusions at the end. Executives read summaries in reverse. Use the "pyramid principle": Start with your conclusion, then justify it.
Why?
Evidence for each point:
Key principle: Each section should answer the question "So what?" If a reader skims, they should still understand the logic.
Strong language:
Weak language to avoid:
Full Report: Remote Work Productivity Study
Over the past 18 months, our HR department conducted an analysis of remote work patterns and their correlation with productivity metrics. The study examined 320 employees across four departments (Sales, Engineering, Finance, Marketing) with a mix of fully remote, hybrid, and office-based work arrangements.
Our baseline findings showed that remote employees logged 8.3% more billable hours weekly than office-based peers, though this may reflect incomplete tracking of office breaks. Interestingly, hybrid workers reported the highest stress levels (68% reported moderate-to-high stress) compared to fully remote (42%) and office-based (55%) cohorts.
Collaboration metrics are mixed. Virtual meetings are 22% longer on average than in-person meetings, suggesting less efficiency in achieving consensus. However, asynchronous communication channels (Slack, email) show 40% more documented decision-trails, which reduces rework. Engineering teams report 18% faster feature delivery in fully remote settings, while Sales reports 12% decline in deal velocity with fully remote arrangements.
Attrition data is instructive. Remote workers have 31% lower voluntary attrition than office-based workers over the study period. Exit interviews consistently cite flexibility and commute time as retention drivers. However, remote employees report 27% less sense of team belonging and identify fewer internal advancement opportunities during the study window.
Real estate costs are significant. Our current office footprint supports 450 employees. Modelling suggests a shift to 70% remote/30% office hybrid would reduce annual real estate costs by $3.2M, though this assumes permanent lease adjustments. Implementation would require office consolidation and hot-desking policies.
We surveyed employee preferences: 64% prefer hybrid arrangements, 22% prefer fully remote, and 14% prefer office-based. By department, Engineering skews remote (71% prefer), while Sales prefers office proximity (58% prefer at least 3 days/week).
Risks of full remote transition include client relationship impact (particularly in Sales), team culture dilution (noted by current office workers), and potential compliance complications in certain regulated teams (Finance is concerned about audit trail management in fully remote settings).
Write a one-page executive summary (100-150 words) for the CEO.
The CEO needs to decide: Do we shift to hybrid/remote? Do we maintain current office model? The summary should present the key insight and a recommendation.
After weeks of research, you've internalized all the nuance. The CFO also knows context that you don't — she knows the board is nervous about retention costs, or that competitors have already gone remote. Your job in the summary isn't to share everything you know. It's to answer the question your reader actually has.
Detail helps when: It closes an objection the reader might have ("Yes, but what about compliance?" — you've addressed it). It supports an unexpected recommendation (remote model works because engineering benefits outweigh sales risk).
Detail hurts when: It buries the recommendation. It presents trade-offs as uncertainties instead of choices. It includes nice-to-know data instead of need-to-know data.
Different executives read differently. A CFO wants financial impact first. A product-focused CEO wants business model implications. An operational executive wants implementation feasibility. Before writing the summary, ask yourself: What does this specific leader care about most? What's their background? What decisions are they currently making?
You've probably read a summary that felt like a condensed version of the full document — all the background, pros and cons equally weighted, no recommendation. This fails because it puts the decision-making burden on the reader. A good summary shoulders the burden: "Here's what I recommend, and here's why."
Reflection questions: