Writing Concise Executive Summaries

Many accountants email the balance sheet and income statement to their CEOs and think,   “Job done.”  But here’s the problem: Your CEO is not necessarily trained in reading financial statements. Even if they were, you've just given them an assignment to "figure it out" If your boss doesn’t understand the numbers, then you haven’t communicated. You’ve just forwarded a report.  🚨 A financial statement without context is just data.   📊 Your job is to turn that data into insights.  How to Present Financials the Right Way  📌 1️⃣ Give a One-Page Summary 🔹 Highlight key figures—Revenue, Profit, Cash Flow, and Key Ratios.   🔹 Include clear takeaways (e.g., “Revenue grew 10%, but margins dropped due to rising costs.”).   🔹 Avoid technical jargon—simplify complex metrics.  📌 2️⃣ Answer the Big Questions   Your CEO doesn’t want numbers—they want meaning. Help them understand:   🔹 What changed? (“Profit dropped 5% due to higher shipping costs.”)   🔹 Why did it happen? (“Fuel prices increased 20% this quarter.”)   🔹 What should we do next? (“We should renegotiate supplier contracts.”)  📌 3️⃣ Use Visuals   🔹 Graphs > Tables—a well-designed chart can explain in seconds.   🔹 Use color-coded trends (e.g., 🔴 Negative, 🟢 Positive).   🔹 Keep it clean—no clutter, no distractions. 📌 4️⃣ Speak the CEO’s Language   🔹 Skip the accounting terminology—focus on impact.   🔹 Tie financials to business goals:     - Sales grew 15% → “We’re expanding market share.”     - Cash flow dipped → “We need to tighten collections.” ✅ Financial statements don’t speak for themselves—you do.   ✅ Numbers are useless without insights.  If your CEO isn’t making better decisions because of your reports, then your job isn’t done.  💡 Don’t just report numbers—explain them. That's how you add value and impact.

𝟴𝟬 𝗣𝗮𝗴𝗲𝘀 𝗼𝗳 𝗥𝗲𝘀𝗲𝗮𝗿𝗰𝗵. 𝟮 𝗣𝗮𝗴𝗲𝘀 𝗼𝗳 𝗔𝘁𝘁𝗲𝗻𝘁𝗶𝗼𝗻 In public policy, most reports are 60–80 pages long. But here’s the uncomfortable truth: Most decision-makers only read the first 2. And sometimes? Just the executive summary. As a research analyst, that realization changed everything about how I structure my work. Here’s what I’ve learned about making sure your research drives action, not just collects dust: ✅ Write for the reader, not for the writer. Don’t write to show how much you know, write to show what they need to decide. ✅ Lead with what matters. Start with the “So what?” before the “What.” Policy leaders want outcomes, not background theory. ✅ Use a “3-30-3” format. Your report should offer: → 3 seconds of clarity (title/executive summary) → 30 seconds of insight (key charts/headlines) → 3 minutes of direction (recommendations & next steps) ✅ Assume scanning, not reading. Use bolded insights, clear section headers, and takeaway boxes. They’re not cosmetic, they’re functional. ✅ One page = one message. If a page has three ideas, it has no anchor. Keep it focused. Make it memorable. 🧠 Research doesn’t create impact. Readable research does. We’re not in the business of writing reports. We’re in the business of helping people make better decisions, faster. 💬 Tag a peer who’s ever had to condense 6 weeks of work into 6 bullet points. And if you want more behind-the-scenes frameworks on how research drives real-world change, follow for more. LinkedIn LinkedIn News India #PublicPolicy #ResearchToImpact #ResearchCommunication #ExecutiveSummaries #PolicyDesign #DecisionSupport #LinkedInForAnalysts

Most resumes start with an “Executive Summary.” You know the one — a vague paragraph about being results-oriented, strategic, passionate, collaborative… The problem? None of that tells me the one thing I really need to know: What value are you going to bring to this business, in this role, right now? Instead of an “about me” blurb, use the opening of your resume to make your value proposition crystal clear. What problem do you solve? How do you create impact? Why should they hire you over the next person in the pile? If you can answer that in the first 3–4 lines, you’re already miles ahead. Forget the generic executive summary. Start with your pitch. PS – Think of it as the first 30 seconds of an interview. Grab attention by leading with value, not adjectives.

I've been writing finance reports for over 30 years. Most people do it wrong. They start with background. Build up slowly. Save the conclusion for page 47. There's a better approach. It's called the Minto Pyramid. It flips everything upside down: 𝗟𝗲𝘃𝗲𝗹 𝟭: 𝗔𝗻𝘀𝘄𝗲𝗿 𝗳𝗶𝗿𝘀𝘁 Lead with your conclusion. Don't make readers wait. "We need to cut the capital budget by £2.3m" beats "Following extensive analysis of Q3 variances..." 𝗟𝗲𝘃𝗲𝗹 𝟮: 𝗞𝗲𝘆 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝗶𝗻𝗴 𝗽𝗼𝗶𝗻𝘁𝘀 Give 3-4 reasons why your answer is right. The budget cut is needed because: • Revenue is 8% below forecast • Two major projects are delayed • Cash reserves are at minimum threshold 𝗟𝗲𝘃𝗲𝗹 𝟯: 𝗗𝗮𝘁𝗮 𝗮𝗻𝗱 𝗱𝗲𝘁𝗮𝗶𝗹𝘀 Now show the evidence. Tables, charts, calculations. This is where most finance professionals start. It's where you should finish. 𝗪𝗵𝘆 𝗜𝘁 𝗪𝗼𝗿𝗸𝘀 Barbara Minto developed this at McKinsey in the 1970s. She found that busy executives need the answer immediately. If they agree with it, they move on. If they question it, they drill into your supporting points. If they still have doubts, they check your data. 𝗙𝗼𝗿 𝗳𝗶𝗻𝗮𝗻𝗰𝗲 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻𝗮𝗹𝘀 Use it everywhere: • Board papers (conclusion in the executive summary) • Emails (answer in the first line) • Budget reports (variance explanation before the tables) Stop burying your conclusions. Put them first. Your readers will thank you.

I shared my standard OM outline with lenders and asked if they'd provide feedback on what's most important to them. Here's the lender-approved format: 1) Executive Summary ‣ Tell the entire story in a page or 2. This includes an overview of the transaction, location, business plan, sponsorship, timing, key underwriting metrics, etc. ‣ This will be easier to digest if its broken into subsections instead of a giant wall of text. 2) Financing Request ‣ Loan purpose (acquisition, construction, etc.) ‣ Loan amount ‣ Loan term ‣ Loan metrics (LTC, LTV, DY, etc.) ‣ Who or what entity is the Guarantor? ‣ Sources and Uses table 3) Investment Highlights ‣ In this case, the "investment" is the lender's debt investment in this deal, so in addition to common highlights like property and location, the highlights can include lender-focused items like strength of the sponsor, conservative loan metrics, etc. 4) Risks & Mitigants ‣ Every deal has challenges and lenders will appreciate that you're highlighting them. 5) Property Overview ‣ Past – When was the property built, renovated, originally purchased (for a refi), historical occupancy, initial tenancy date, etc. ‣ Present – Current size, condition, occupancy, rent roll, parking, professional photos, site plans, floor plans, etc. For construction, you need to also include the status of architectural drawings, permitting, GMP, etc. ‣ Future – Renovation/construction plan, projected costs, timeline, renderings, etc. 6) Location Overview ‣ Important demand drivers, e.g., proximity to public transportation, major nearby employers, etc. ‣ Maps (regional and neighborhood) ‣ Meaningful neighborhood amenities 7) Market Overview ‣ Demand metrics, e.g. tenants in the market (if commercial), population/job growth, etc. ‣ Rent/vacancy stats ‣ Rent comps + map ‣ Sale comps + map ‣ Development pipeline 8) Financials ‣ Historical operating statements ‣ In-place and stabilized pro forma ‣ Stabilized valuation ‣ 5 to 10-year annual cash flow ‣ Assumptions 9) Sponsor Overview ‣ Company overview + history ‣ Similar past projects / track record ‣ Key principals + background ‣ Prior debt and equity partners ‣ For construction, include the rest of the development team (GC, architect, etc.) ‣ If there's an institutional LP, they should be included. Additional Notes: ‣ Attach a corresponding Excel model with working formulas (not hard-coded) when sending the OM. Lenders will need to take data from the OM and put it in their own format for their IC memo. It's much easier and faster to grab this data from tables in Excel. ‣ Lenders are going to want more information on the sponsor(s) like guarantor financials, have they had any past foreclosures, etc. You don't need to include this information in the OM given the sensitive nature, but be prepared to provide it separately. Anything else you'd add? 'Like' and Repost if this may benefit any of your connections.

Writing an executive summary is a necessary skill for every designer. I’ve seen countless links to dozens of art boards, deep dives into processes, and click-through prototypes, often without a clear introduction on the ‘why’. For someone outside of the workstream, this can be an overwhelming amount of information to digest in a short period of time. While it may sometimes be done with good intentions, it’s equally important that the information lands correctly. Think of executive summaries as a pitch for a project. They are often the first one or two paragraphs or set of bullet points someone reads before digging into the rest of the content. People are busy, and as much as you’d like to assume the audience will have the necessary context, it’s better to set up the information upfront rather than having to answer the same questions repeatedly. Here’s a good starting point: 1. Define the problem 2. Explain the opportunity/value proposition and audience. 3. Summarize key findings related to the problem (ideally top 3) 4. Outline what success looks like and how it’s measured 5. State what you’re going to do about it (what is the plan and timing) With the above in place, take stock of your work. You might observe: 🫣 It’s not present 🧐 The information may be present but obscured or scattered about. 😳 You don’t have clarity on the five points I outlined above If any of the above is true then you might want to reconsider sharing your work and run it back with your direct working team to align/define these things. Your audience will thank you for it (in good feedback and buy-in).

Your evaluation was rigorous. Your report killed it. You designed the methodology carefully. You interrogated the findings until you were confident they were right. Then you wrote a 80-page document. It buried the most important finding on page 34, and.. submitted it to a stakeholder who read the executive summary on a flight and never opened it again. The evaluation was good. The report undid it. And this isn't a personal failing. It's a sector-wide one. The development sector produces thousands of evaluation reports every year. Most of them change nothing. The writing is why. Not the data. Not the methodology. Not the sampling strategy or the theory of change. The writing. 𝗖𝗹𝗲𝗮𝗿. 𝗖𝗼𝗻𝗰𝗶𝘀𝗲. 𝗖𝗼𝗺𝗽𝗲𝗹𝗹𝗶𝗻𝗴. 𝗣𝗶𝗰𝗸 𝗮𝗻𝘆 𝘁𝘄𝗼, 𝗺𝗼𝘀𝘁 𝗲𝘃𝗮𝗹𝘂𝗮𝘁𝗶𝗼𝗻 𝗿𝗲𝗽𝗼𝗿𝘁𝘀 𝗺𝗮𝗻𝗮𝗴𝗲 𝘇𝗲𝗿𝗼. They're dense where they should be direct. Cautious where they should be bold. Written to demonstrate expertise rather than to communicate it. And the people who needed to act on the findings... the minister skimming between meetings, the programme manager already stretched thin, the donor trying to decide whether to renew, they encountered a wall of jargon, a forest of tables, and a recommendation section so hedged and generalised it could apply to any programme anywhere. So they didn't act. Or they acted on instinct instead of evidence. Because the report didn't give them a choice. Here's how to do better... 1. Write for a real audience, not an abstract one ↳ Not “stakeholders” ↳ The specific person who will use this ↳ The minister with 5 minutes ↳ The programme manager under pressure ↳ The donor deciding on funding If you don’t know who you’re writing for, you’ll default to writing for yourself. 2. Start with the decision, not the methodology ↳ What needs to change because of this report? Write to that. 3. Lead with the answer ↳ Don’t make people work for the insight Page 1 should tell them what matters 4. Design for use, not submission ↳ A report is not the final product A decision is ---- Want insights like this directly in your inbox? Sign up for my mailing list. It's FREE! 👉 https://lnkd.in/ec8mqV2M

That email you sent to the CEO got read. It also got deprioritized because you made them do work. I've sent the bad version too many times. They all had one thing in common: too much explaining. Children explain. Adults inform. The info dump email: "Hi Bill, wanted to follow up on the Humana contract discussion. They're pushing for a risk-based model but the terms are aggressive. I've been going back and forth with their team on quality thresholds and shared savings splits. We could accept their benchmarks, or counter with adjusted targets, or maybe propose a hybrid. I put together a few scenarios..." WAY too much backstory, no clear decision, no urgency, no deadline. The exec skims it, means to reply later, and never does. The direct decision brief email: "Hi Bill, I need a call on the Humana risk-based contract before their Friday deadline. The ask: Approve 60/40 shared savings split with adjusted quality benchmarks. Why it matters: Their current offer puts us underwater if utilization spikes. This counter protects margin while keeping the deal alive. Tradeoffs are in the attached one-pager. Can you approve or flag concerns by Thursday EOD?" One decision, defined stakes, clear deadline. The 4-line exec email: 1. The ask (one sentence, one decision) 2. The deadline (specific date, not "when you get a chance") 3. The stakes (why it matters now) 4. The context (one attachment, not five paragraphs) Executives don't need (or frankly want) more information. They want less thinking in their lives. It's your job to give them them what they want. If they can't say yes in under 30 seconds, you didn't send an email. You sent them work.

My co-author, Colin Bryar, and I wrote, read, and reviewed thousands of business narrative documents during our combined 27 years at Amazon. Based on our experience, here are tips to follow and common pitfalls to avoid. 1. Write for a generalist executive audience. Picture your reader as intelligent but unfamiliar with the specifics of your domain. Imagine a new senior leader who just joined the company. This will make it easy for anyone in your company to understand your business unit or function’s plans, metrics, results, problems, and opportunities. 2. Skip the suspense. Building suspense works in mystery novels, not in business narratives. Get to the point directly. Make sure to use concise, direct language. Every sentence should add value and distill complex ideas into a document that enables high-quality decision-making. 3. Let data tell the story. Replace adjectives with data. Instead of saying “sales accelerated,” say, “Sales in February were $150MM, a 22% increase versus January, 15% year-over-year, and 3% above plan.” Weasel words like “many” or “significant” are meaningless without context. If you can’t quantify something, explain why not and outline how you’ll get better data to quantify it in the future. 4. Anticipate and include counterarguments. Inform the reader what you considered and rejected, along with the reasons. Provide more than one option or solution when possible, and explain why you chose the recommended approach. This demonstrates that you've thought through alternatives. 5. It’s Word, not PowerPoint. Don’t just copy a Powerpoint and paste bulleted text into a Word Doc. Use full sentences and a narrative flow to tie together related data, thoughts and concepts. True narrative writing creates logical connections between ideas, shows cause and effect, and builds toward conclusions. 6. Provide insights, not a data dump. One of the most common errors made by inexperienced managers and writers is to writing documents describing activity and data, but failing to provide insights and information. Don’t try to write about everything. Summarize, distill, and provide insights. 7. Less is more. The best way to destroy the benefits of writing business narratives and conducting meetings with narratives is to bring a long document to the meeting. For a one-hour meeting, the page limit is six pages. For a 30-minute meeting, the page limit is three pages. If narratives exceed these limits, the readers will not be able to carefully read the entire document during the 15-20 minute silent reading time at the beginning of the meeting. Readers are forced to skim, and your discussion and decision-making will be based on partial information. If you would like to learn more about writing an Amazon-ready narrative, our new online course on writing narratives has launched: https://lnkd.in/gYSnerCD

You’re doing this wrong. Here’s why. When asked for updates, most high performers 'explain'. But Leaders always opt for 'framing'. Explaining sounds like a long story: - what happened - why it happened - how hard it was - every detail you touched Framing sounds like: “Here’s the decision. Here’s the impact. Here’s what I need.” If you want to be seen as Director-level, start speaking in 'decision language'. Because the room doesn’t reward the most detailed person. It rewards the 'clearest' person. 𝐇𝐞𝐫𝐞’𝐬 𝐡𝐨𝐰 𝐭𝐨 𝐫𝐞𝐟𝐫𝐚𝐦𝐞 𝐲𝐨𝐮𝐫 𝐧𝐞𝐱𝐭 𝐮𝐩𝐝𝐚𝐭𝐞 (5 𝐰𝐚𝐲𝐬): 1. 𝐅𝐫𝐨𝐦 𝐚𝐜𝐭𝐢𝐯𝐢𝐭𝐲 → 𝐨𝐮𝐭𝐜𝐨𝐦𝐞   “I worked on X” → “X is now at Y result (and it changes Z).” 𝐈𝐧𝐬𝐭𝐞𝐚𝐝 𝐨𝐟: “I worked on the Q1 report and updated the deck.” 𝐒𝐚𝐲: “Q1 deck is finalized and aligned with Finance. Outcome: we can sign off the forecast tomorrow and unblock the exec review.” 2. 𝐅𝐫𝐨𝐦 𝐬𝐭𝐨𝐫𝐲 → 𝐬𝐢𝐠𝐧𝐚𝐥   “Let me give context…” → “The key point you need is this: ___.” 𝐈𝐧𝐬𝐭𝐞𝐚𝐝 𝐨𝐟: “Quick context—last week we had delays because Vendor A…” 𝐒𝐚𝐲: “Key signal: Vendor A is now the bottleneck. If we don’t switch by Friday, launch moves by 2 weeks.” 3. 𝐅𝐫𝐨𝐦 𝐞𝐟𝐟𝐨𝐫𝐭 → 𝐫𝐢𝐬𝐤   “This took longer than expected” → “Risk: ___ / Mitigation: ___ / Decision needed: ___.” 𝐈𝐧𝐬𝐭𝐞𝐚𝐝 𝐨𝐟:“This took longer than expected because the data was messy.” 𝐒𝐚𝐲: “Risk: reporting accuracy drops if we ship with incomplete data. Mitigation: run a 24-hour validation. Decision needed: approve a 1-day shift or accept reduced confidence.” 4. 𝐅𝐫𝐨𝐦 𝐩𝐫𝐨𝐛𝐥𝐞𝐦𝐬 → 𝐨𝐩𝐭𝐢𝐨𝐧𝐬   “We’re stuck because…” → “We have 3 options. I recommend B because ___.” 𝐈𝐧𝐬𝐭𝐞𝐚𝐝 𝐨𝐟: “We’re stuck because stakeholders keep changing requirements.” 𝐒𝐚𝐲: “We have 3 options: A) Freeze ... B) Add ... C) Split ..... I recommend B to protect quality and avoid rework.” 5. 𝐅𝐫𝐨𝐦 𝐚𝐬𝐤𝐢𝐧𝐠 𝐩𝐞𝐫𝐦𝐢𝐬𝐬𝐢𝐨𝐧 → 𝐫𝐞𝐪𝐮𝐞𝐬𝐭𝐢𝐧𝐠 𝐚 𝐝𝐞𝐜𝐢𝐬𝐢𝐨𝐧   “Can I…?” → “Decision required: approve ___ by ___ so we can deliver ___.” 𝐈𝐧𝐬𝐭𝐞𝐚𝐝 𝐨𝐟: “Can I move resources from Project X to help this?” 𝐒𝐚𝐲: “Decision required: reassign 1 analyst from Project X for 10 days so we can hit the regulatory deadline. If approved today, we stay on track.” Here's a bonus: Try this 15-second Director-level structure: 𝐃𝐞𝐜𝐢𝐬𝐢𝐨𝐧: ___ 𝐈𝐦𝐩𝐚𝐜𝐭: ___ 𝐍𝐞𝐞𝐝: ___ (owner + deadline) ♻️ Save & Reshare this. Someone in your circle is just looking for how to replace storytelling with director language. Their boss is too busy for all the details.