Writing Meeting Notes That Support Decision Making

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.

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

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.

𝗧𝗵𝗲 𝗣𝗠 𝘄𝗶𝘁𝗵 𝗽𝗲𝗿𝗳𝗲𝗰𝘁 𝗺𝗲𝗲𝘁𝗶𝗻𝗴 𝗻𝗼𝘁𝗲𝘀 𝗶𝘀 𝘀𝘁𝗶𝗹𝗹 𝗺𝗶𝗱-𝗹𝗲𝘃𝗲𝗹. 𝗧𝗵𝗲 𝗣𝗠 𝘄𝗶𝘁𝗵 𝘁𝗵𝗿𝗲𝗲 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗹𝗼𝗴𝘀 𝗷𝘂𝘀𝘁 𝗺𝗮𝗱𝗲 𝗗𝗶𝗿𝗲𝗰𝘁𝗼𝗿. Both document religiously. Only one documents what matters. Two PMs at the same company. Same promotion cycle. PM A documented everything: → Every meeting with detailed notes → Every status update color-coded → Every task logged in three different tools → 20 hours a week on documentation PM B documented three things: → Critical decisions with rationale → Risks that actually threatened delivery → Tradeoffs that impacted business outcomes When leadership asked why the project shifted direction in Q3, PM A sent 47 pages of meeting notes and status reports. PM B sent one decision log: → The constraint: vendor delay pushed launch into compliance window → Three options considered with cost/timeline impact → The tradeoff: delayed feature set, kept launch date → Business impact: $400K saved, market window preserved Leadership read it in 90 seconds. 𝗛𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲: 𝗕𝘂𝘀𝘆 𝘄𝗼𝗿𝗸 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻: → Proves you're working hard → Shows activity 𝗦𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻: → Proves you think critically → Demonstrates business judgment Senior leaders don't read your meeting notes. They need to see how you think under pressure. Document the moments where you chose between bad and worse. Document the calls you made when the data was incomplete. Document the tradeoffs that kept the project moving. That's the documentation that gets you promoted. What's one decision from your current project worth documenting? Follow Brian Ables, PMP, for practical tips and strategies to grow your career. ♻️ If this changed how you think about documentation, share it with other PMs.

We’ve all seen variations of this comic on LinkedIn. They’re “funny” — but they also show a problem: we’re using AI with an old, document-centric mindset. Five bullets → AI inflates to 12 pages → AI compresses back to five bullets. That’s not intelligence; it’s content ping-pong. We’re optimizing for length, not for decisions. A better way: in a case like this, AI should act as a decision co-pilot, not a text generator. Instead of “write 12 pages,” ask AI to: 1. Clarify intent & audience. “What decision must be made, by whom, and by when?” 2. Build a 1-page Decision Brief: recommendation, three supporting reasons, risks/mitigations, options considered, next steps. 3. Link evidence, don’t paste it: connect to the data and surface the few charts or numbers that matter. 4. Generate fit-for-purpose outputs: • exec email (≤200 words with clear ask) • one-slide visual for the meeting • optional appendix with traceable sources 5. Push back when inputs are weak: ask for gaps, assumptions, and thresholds that would change the recommendation. 6. Automate the loop: monitor the underlying data and update the brief if something material changes. Try this prompt: “Turn these 5 bullets into a 1-page Decision Brief for [audience]. State the recommended action, key reasons, risks, alternatives, and next steps. Produce: (a) a 200-word exec email with a clear decision request, (b) a single summary slide, and (c) links to supporting data. Ask me any clarifying questions first.” Write less. Decide faster. Deliver clarity. #AI #AgenticAI #DecisionIntelligence #Productivity #FutureOfWork #Leadership #Communication

Your CEO just spent 90 minutes talking through a decision. You took seven pages of notes. Now you have to turn that into something the team can actually execute. Nobody taught you how to translate verbal chaos into executable clarity. This is the Verbal Processor—one of the 12 CEO Archetypes in the CoS Operating System™. Here's how to build the capture system that makes this sustainable: 1. Real-Time Documentation Open a shared doc during the conversation. Type while they talk. They'll see you capturing and self-correct in real-time. 2. The Decision Line Draw a line in your notes when they shift from exploring to deciding. Everything above the line = context. Everything below = action. 3. The 24-Hour Memo Within 24 hours, send a one-page summary: "Here's what I heard. Here's what we're doing. Here's what we're not doing." 4. The Confirmation Loop End with: "If I don't hear from you by 5 pm, I'm moving forward with this interpretation." 5. Pattern Documentation Track which topics require verbal processing vs which they decide quickly. Build your meeting strategy around this. Verbal Processor CEOs don't need you to shortcut their thinking. They need you to be the system that captures it, translates it, and protects the team from the turbulence. That's not note-taking. That's decision architecture. Which of these five would have saved you the most time in your first 90 days with a Verbal Processor? #ChiefofStaff #OperatingSystems