Meeting-to-Decision Memo Loop
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 Task: How do we turn this messy meeting into a decision memo? 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 Useful setup: Paste meeting notes, the decision needed, options discussed, constraints, names or roles of owners, and any unresolved objections. Why this matters: 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. Business problem: Important meetings often end with alignment theater: everyone agrees in principle, but the decision, owner, evidence, and next step remain unclear. 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. Workflow: 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. Quality bar: - Use only the context in this chat. - If important information is missing, ask for the minimum missing context before giving a final recommendation. - Separate facts from assumptions. - Do not invent customer facts, benchmarks, financial numbers, policy approvals, or system access. - Keep the answer useful for CEO / GM. Output: A concise decision memo with recommendation, evidence, open questions, owner, and next action. - BLUF recommendation or draft. - Evidence from my context. - Assumptions and missing information. - Risks, objections, or failure modes. - Recommended next action, owner, and stop condition. Evidence checklist: - Decision or non-decision - Evidence stated - Assumptions - Named owner - Deadline - Open objection 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.
Key takeaways
- How do we turn this messy meeting into a decision memo?
- A concise decision memo with recommendation, evidence, open questions, owner, and next action.
- Stop when the memo names the decision status, owner, next action, and missing evidence clearly enough that a reader can disagree with it.
- Decision or non-decision
- Evidence stated
Canonical URL: https://juanbeltran.ch/operating-loops/meeting-to-decision-memo-loop