Meeting-to-Decision Memo Loop

By Juan Beltrán, Industrial B2B AI Transformation Executive.

How do we turn this messy meeting into a decision memo? Use this after a leadership, sales, transformation, or project meeting where the discussion was useful but the decision, owner, and next step are still fuzzy. Meeting-to-Decision Memo Loop Decision to make: How do we turn this messy meeting into a decision memo? Decision owner: Meeting owner or decision sponsor. Working-session setup: - Timebox: 20 min working session - People in the room: Decision sponsor, subject owner, and one credible challenger. - Preparation: Light prep: bring the notes or draft already in front of you. Context: [Paste your notes, excerpts, draft, meeting transcript, CRM fields, proposal text, public research, or examples here.] Context I should provide: - Meeting notes - Decision needed - Options discussed - Constraints - Owners or roles - Open objections - Deadlines Safety boundary: - Use only information I provide in this conversation. - Do not infer personal, confidential, regulated, pricing, customer, employee, or supplier facts. - If the material belongs in an approved enterprise environment, tell me before analyzing it. Instructions: Act as an executive chief-of-staff. Turn the meeting notes below into a decision memo. Do not invent consensus. Separate decisions, open issues, assumptions, risks, and next actions. If the meeting did not produce a real decision, say that clearly and propose the smallest follow-up needed. Run the session in this order: 0. Inspect the context. If a missing fact could materially change the recommendation, ask no more than five focused questions and wait. If I ask you to continue, mark each missing fact as unknown. 1. Extract the actual decision: Identify whether a decision was made, implied, deferred, or avoided. 2. Separate facts from interpretations: Mark what was stated as evidence, what was inferred, and what still needs confirmation. 3. Name owners and deadlines: Assign each next action to a role or person and state the required date or trigger. 4. Write the memo: Produce a concise BLUF memo that a senior stakeholder can read in three minutes. 5. Draft the follow-up: Write a short email that confirms decisions, actions, and unresolved questions without sounding bureaucratic. Evidence rules: - Separate supplied facts, interpretations, assumptions, and unknowns. - Reference the exact note, excerpt, metric, or example supporting every material claim. - Show the strongest credible counterargument to the recommendation. - Do not invent customer facts, benchmarks, financial numbers, policy approvals, or system access. - Do not turn missing evidence into a confident recommendation. - Keep the answer useful for CEO / GM. Output contract: A concise decision memo with recommendation, evidence, open questions, owner, and next action. Return: 1. BLUF: the decision, recommendation, or draft in plain language. 2. Evidence table: claim, supplied evidence, confidence, and gap. 3. Assumption ledger: what is assumed and how to verify it. 4. Counterargument: the strongest reason the recommendation may be wrong. 5. Decision record: decision status, accountable owner, next action, and due date or trigger. 6. Evidence still needed: only the gaps that could change the decision. 7. Stop condition: state when the work is complete and when it must pause. Evidence checklist: - Decision or non-decision - Evidence stated - Assumptions - Named owner - Deadline - Open objection Human operating ritual: - Send the memo within 24 hours. - Ask the decision owner to correct the BLUF, not the formatting. - Do not hide unresolved conflict in polite language. Do not use this loop when: Do not run it as confirmation theatre after the decision has already been made. Stopping condition: Stop when the memo names the decision status, owner, next action, and missing evidence clearly enough that a reader can disagree with it.

Canonical URL: https://juanbeltran.ch/operating-loops/meeting-to-decision-memo-loop