Meeting Summaries That Actually Get Read

5 min

What you will learn

Structure meeting summaries so busy stakeholders read and act on them
Distinguish between what was discussed and what was decided
Write summaries that drive accountability, not just document conversations

1 of 6

Meeting Summaries That Actually Get Read

Here is a frustrating truth: you spend 20 minutes writing a detailed meeting summary, and nobody reads it. They skim the first two lines, look for their name, and close the email. Then they message you asking "what was decided?"

This happens because most meeting summaries are written like transcripts — they recount the discussion chronologically, burying the important conclusions in paragraph seven. Busy people do not have time for that.

This lesson teaches you to write summaries that get read because they put the important information first.

←→navigatespacecontinue

Knowledge check

1 of 1

You attended a 1-hour strategy meeting with extensive discussion. Which of the following should appear FIRST in your summary?

Key takeaway

Nobody reads a three-page meeting summary. The most effective summaries lead with decisions and action items, include only enough context for someone who was not there to understand what matters, and end with clear next steps.

Practice Exercise

Hands-on practice — do this now to lock in what you learned

Open an AI assistant and try this:

Find notes from your most recent meeting. Restructure them using the inverted pyramid format: decisions first, action items second, discussion context third. Time yourself — how quickly can you identify what was actually decided vs. what was just discussed?

Open in ChatGPT

Or try it in:Claude Gemini Perplexity

+10 XP when completed

Write your prompt attempt here (optional)

Meeting Summaries That Actually Get Read

This lesson teaches you to write summaries that get read because they put the important information first.

Knowledge check

1 of 1