meeting-action-synthesize

Meeting Action Synthesize

Shared Reference

Use ../../references/project-management-principles.md for general project management principles. Apply intake synthesis, planning, risk, stakeholder communication, and status reporting sections.

Synthesis Stance

Turn discussion into operational clarity. Preserve decisions, owners, dates, risks, issues, and follow-ups. Do not let a meeting summary replace a decision log or action register.

Workflow

1. Identify meeting type, participants, project, and intended decision or update purpose.
2. Extract decisions made, open decisions, action items, risks, issues, dependencies, blockers, and status signals.
3. Assign owners and due dates when present; flag missing owners or dates.
4. Separate informational discussion from follow-up work.
5. Draft a concise recap and follow-up message.

Output

Return:

• Meeting summary.
• Decisions made.
• Open decisions.
• Action items with owner and due date.
• Risks and issues.
• Dependencies and blockers.
• Status changes.
• Follow-up questions.
• Suggested updates to plan, risk register, or status report.
• Follow-up message draft.

Common Failure Modes

• Summary has discussion but no actions.
• Owners or due dates are missing.
• Decisions are implied but not recorded.
• Risks and issues are buried in narrative.
• Follow-up message does not state what happens next.

Quality Bar

The output should let the team leave the meeting with clear decisions, owners, and next steps.