Writing Meeting Notes That Are Easy to Review

How I Structure My Meeting Notes as a Program Manager at Amazon One of the most underrated skills in program management is note-taking. With so many meetings, decisions, and action items flying around, having a solid system for capturing and organizing information is critical. Over the years, I’ve developed a structure that keeps me on top of things—and ensures nothing slips through the cracks. Here’s how I approach my meeting notes: 1️⃣ Start with the Basics I always document the essentials upfront: • Meeting Name & Date • Attendees • Objective or Agenda (Why are we here?) This helps me quickly orient myself when reviewing notes later. 2️⃣ Use Action-Driven Sections My notes are broken into three sections: • Decisions Made: Clear and concise. What was decided, and why? • Action Items: Each action includes an owner, due date, and a quick description of what’s expected. No ambiguity. • Key Discussions: I summarize important points—nothing overly detailed, just enough to provide context. 3️⃣ Keep Notes Digital and Searchable I use tools like OneNote to keep everything organized and searchable. By tagging projects, teams, or topics, I can quickly find past notes without digging through endless files. 4️⃣ Review and Share Afterward After the meeting, I do a quick review of my notes, clean them up if needed, and share them with attendees. It’s a great way to confirm alignment and ensure everyone is clear on next steps. This system helps me stay organized, track progress, and reduce the chances of things falling through the cracks. How do you structure your meeting notes? #ProgramManagement #Leadership #Amazon #Productivity #Meetings

The note taking feature in the ChatGPT Mac app has way more potential than the built-in prompt captures. Copy and paste this prompt after it creates the first round of notes, and it gets 10x better: TASK Create full meeting notes from the available transcript. # Summary - 3–6 bullets on outcomes, decisions, and any dates/numbers. # Key Takeaways - 5–10 bullets anyone skimming should know. # Action Items - Table: Task | Owner | Due (YYYY-MM-DD, America/Chicago) | Notes - Map “I/I’ll” to the speaker’s name. If Owner/Due missing, use TBD (suggest one in parentheses). # Full Notes — Categorized - Group everything said into clear topics you infer (e.g., Goals, Scope, Timeline, Budget, Risks, Ideas, Blockers, Parking Lot). - Under each topic, list short bullets: - [Speaker]: fact/claim/ask/decision/number/date. Include timestamps if present [hh:mm:ss]. - Keep duplicates only if they add new nuance; otherwise, dedupe. - Include ALL concrete details relevant to work. If in doubt, include it here. RULES - Plain English. Short lines. No fluff. - Use real names consistently; resolve pronouns (“I,” “they”) to speakers when clear. - Pull exact figures, dates, commitments; convert relative time to dates in America/Chicago when possible. - Don’t invent facts. Mark unclear items as TBD and note the ambiguity.

Good decisions die in messy docs. If you want clarity and speed, compress it. One page. Five sections. No fluff. 1. Context – Why we’re here and what’s at stake. 2. Options – The real alternatives we considered. 3. Risk – Trade-offs, uncertainties, and what could break. 4. Choice – The decision, and the “why” behind it. 5. Follow-Ups – Who owns what, and by when. This format does 3 things well: Forces clear thinking. Speeds alignment. Leaves a record for future you. If your team debates endlessly or revisits decisions over and over, try the one-page memo for your next meeting. You’ll feel the difference.

Most PMs do not know how to take good notes. They write notes during meetings, copy bullet points, and record what people said. Later, they wonder why the same arguments keep coming back and why everyone remembers things differently. Many project problems are not tool problems. They are note-taking problems. Decisions get made, but they are not written clearly. The reasons behind them get lost. Assumptions stay in people’s heads. A few weeks later, teams argue about what was meant instead of getting the work done. Good notes are not meeting transcripts. They are how teams remember why decisions were made. They reduce confusion, prevent rework, and help teams move faster without losing alignment. After years of running complex programs, here are 12 simple ways PMs can take better notes: 1. Write notes for future decisions, not past meetings 2. Capture decisions clearly, not just discussion 3. Always include the why behind a choice 4. Separate facts from assumptions and opinions 5. Track open questions explicitly 6. Record trade-offs, especially what was not chosen 7. Assign actions to named people 8. Use simple language that still makes sense later 9. Keep one idea per line 10. Review notes regularly 11. Convert notes into actions quickly 12. Write notes so someone else could pick them up and run Strong PMs do not rely on memory. They design for clarity. Because your notes are not admin work. They are part of the delivery system. If you use tools like Microsoft Copilot, let them handle the raw capture and summaries. But remember this: AI can record meetings, not judgment. The thinking still has to come from you. ↳ Save this if you have seen the same decisions argued twice → Follow RAJESH MATHUR for practical delivery leadership lessons

If you need “the minutes” from a meeting you were actually in, your system’s already broken. Why? Because real work doesn’t need your recap. It needs decisions. When a meeting ends and nobody can tell you what got locked in, that’s not collaboration. That’s called project amnesia. How do you know that you’re project has this dreaded disease? Someone asks, “Wait… what did we decide again?” two days later. Tasks are aimless, with no owner and no due date. You schedule a follow-up… just to understand the last follow-up. Ugh! Stop writing meeting minutes and try this instead. 1. Open with outcomes (3 bullets, max) • Start every meeting with what you hope to accomplish. • Something like: “By the end of this meeting, we’ll pick the vendor, approve the budget, and lock the date.” • Everyone knows what they'll walk away with once the end is defined. 2. Make a decision log in real time • It's a shared doc that's visible to everyone in the room. • It has simple headers: Decision → Owner → Deadline → Risk (if any) • If it doesn’t get logged when you are in the room, it didn’t happen. 3. Use the O/A/D rule • Every discussion should include an owner, action, and deadline—before you move on. • Owners voice their commitment out loud. • Deadlines use actual dates, not vague timelines like “next sprint.” 4. Apply the disagree & commit rule • Have a debate (but only for 5 minutes). • Then make the call, use the decision log, and move on. • No revisiting it next week unless something critical changes. 5. 60-second close • At the end, someone reads the decision log out loud. • Ask if anything's unclear, and if it is... fix it right there. • Then post the decision log to your project workspace. 6. 24-hour recommitment • Send out an automatic summary of the decision log to the team. • Decisions, owners, deadlines, and nothing else. • No extra stuff. Just the log. We need to stop clinging to meeting minutes and start capturing commitments. When you run meetings like this, nobody hunts for minutes. They’re busy shipping what you decided.

To my fellow EAs - let's talk meeting minutes. A few tips below: 🛠 Before the Meeting: - Know the agenda: Get a copy ahead of time. You'll anticipate key points. - Set up a simple template: — saves you from scrambling. - Clarify roles: Know who’s leading the meeting and who the key decision-makers are. 🗒 During the Meeting: - Capture major points, not every word: Focus on decisions made, key discussions, and assigned tasks — not side conversations or exact quotes. - Use bullet points: They're faster to write and easier to read later. - Identify action items clearly: Write what needs to happen, who’s responsible, and by when. - Mark follow-ups: If something is undecided, flag it for next time. - Stay neutral: Don’t add personal opinions or interpretations. 🛠 After the Meeting: - Clean up right away: Don’t wait — fresh memory = better notes. - Summarize clearly: Reword any messy notes into clean, short sentences. - Send it out quickly: Ideally the same day or the next morning, while things are still fresh for everyone. - Highlight key decisions and tasks: Bold or bullet them so people can skim easily. 🧠 Bonus Quick Tips: - Bring a laptop if you type faster than you write (I prefer writing) - If you’re unsure about something (like a decision), ask during the meeting: "Just to confirm, are we agreeing to [this decision]?" - Develop shorthand: "AI" for Action Item, "D" for Decision, "F/U" for Follow-Up. What would you add?

I developed a simple system for making LLMs better at summarizing meeting notes. I'd encourage you to use it. I use symbols to add important context to the notes I am writing, identifying what I view as important or warranting further research rather than relying on the LLM to figure that out on their own. Its a great example of us working together and me micromanaging my little intern as is fit to do. Please steal this. I am including the prompt I use for meeting note summarization. --Prompt-- Please summarize the raw meeting notes included after the "//" below according to these guidelines: Executive Summary: Start with a brief overview of the meeting's main objectives and outcomes. Important Points: List all important points marked with '*'. Organize them clearly under this section. Key Sections: Split the notes into sections based on the topics discussed. Elaborate on each key point within its respective section. Action Items: Include all action items marked with '^', specifying who is responsible for each action. List them under 'Action Items'. Follow-Up Questions/Research: List any follow-up questions or items needing further research marked with '?', under 'Follow-Up Items'. Verbatim Quotes: Incorporate any verbatim quotes noted by double quotes ("") in relevant places throughout the summary in italics. Include all quotes, as verbatims are important! Style Guidelines: Conciseness: The summary should be as concise as possible while maintaining the meaning of the notes. Language: Avoid using flowery or superfluous words. Tone: Write in a neutral, colloquial tone. Recommendations: Suggest any additional meetings or actions if necessary. // <meeting notes>

Still Writing Meeting Notes by Hand? Try This Instead. AI can turn long transcripts into clear, structured summaries in seconds—if you know what to ask. Here’s the prompt I use after every meeting: “You are an expert in summarizing meetings. Format the summary with key discussion points, decisions made, action items with names + deadlines, and any open issues.” Include these in your AI instructions: A 2-line overview Bullet points (not paragraphs) Quotes or insights worth saving Follow-up owners + due dates This works for team check-ins, client calls, even brainstorming sessions. Want my favorite AI summary template? Reply “notes” and I’ll send it over. #AIProductivity #MeetingEfficiency #WorkSmarter

Had a fascinating chat with a course alumna that reminded me why I'll never stop evangelizing for PMs screensharing their notes during meetings. (You don't need anything special: a text file, the description field of a Jira ticket, or Slack message draft.) She told me that after taking my course, she started defaulting to screen sharing and writing things down live. What's interesting is that her team now asks her to share her screen: "Can you write that down so we can see you're receiving what I'm saying?" She shared a perfect example where her team was trying to align on pricing with sales. There were whole email chains where someone was like, "Yeah, we're going to take off this customization," and everybody's like, "Okay, fine, we're aligned." Then she screenshared a quick table she spun up. In her words "I was like, 'Okay, here's a table of what it means to take it off.' And he's like, 'No, that's not what I was expecting, I was expecting three times that.'" This practice is surprisingly powerful for several reasons: - It shows people you're actively listening - Creates documentation people actually reference - Keeps meetings focused without feeling forced - Provides clarity that emails and verbal discussions often miss As a PM, it's really about keeping the meeting on track and in a way controlling the meeting while directing it in a way that doesn't feel like you're controlling anybody. Try this in your next meeting. Again - I use whatever is already open: a Google doc, the description field of a Jira ticket, or Slack message draft. At the end of the meeting casually and humbly ask "did I capture this correctly? am I missing anything?" Even after years of doing this, I'd still be surprised when someone said "that's not what I meant" when seeing their words reflected back. I'm always amazed at how much engagement this gets from even the highest-ranking leaders in the meeting, and how much trust it builds with anyone who works with me.