Meeting Agenda: [Topic/Stakeholder] Meeting

Date: [YYYY-MM-DD]
Time: [Time with timezone, e.g., 2:00 PM PT]
Attendees: [Names]


Post-Meeting Summary

Add this section after the meeting concludes

Key Learnings

Platform or Technical Insights:

  • [Major insight about architecture, systems, or implementation]
  • [Pain points or limitations discovered]
  • [Unexpected findings or technical details]

Feature Requirements:

  • [Feature specifications clarified]
  • [User stories or acceptance criteria defined]
  • [Integration points identified]

Quick Wins Identified:

  • [High-impact, low-effort opportunity]
  • [Automation or optimization opportunity]
  • [Improvement to existing feature]

Answers to Key Questions

Reference question numbers from below and provide concise answers

Q1-5: [Topic Area]

  • Q1: [Original Question] - A: [Answer with key details]
  • Q2: [Original Question] - A: [Answer with key details]

Q6-10: [Topic Area]

  • Q6: [Original Question] - A: [Answer with key details]

Decisions Made

  • [Decision about tool or platform]
  • [Agreement on feature scope]
  • [Technical approach approved]

Next Steps

  • [Owner Name]: [Action item] (Due: [YYYY-MM-DD])
  • Brainforge: [Follow-up task] (Due: [YYYY-MM-DD])
  • Joint: [Collaborative task] (Due: [YYYY-MM-DD])

Meeting Objectives

  1. [Objective 1]
  2. [Objective 2]
  3. [Objective 3]

Demos and Walkthroughs Requested

  • [Demo name]
    • [What to see or validate]
    • [Questions to explore during demo]
    • [Expected outcome]

Questions to Ask

[Topic Area 1: e.g., Platform Architecture]

  1. [Question text]

    • [Sub-bullet for context or why asking]
    • [Sub-bullet for what you want to learn]
  2. [Question text]

[Topic Area 2: e.g., Feature Requirements]

  1. [Question text]

  2. [Question text]

[Topic Area 3: e.g., Data and Integrations]

  1. [Question text]

Key Discussion Topics

Strategic topics or decisions that need conversation, not just Q and A

[Topic 1]

  • Context: [Why this topic matters]
  • Options: [Choices or alternatives to discuss]
  • Goal: [Desired outcome from discussion]

[Topic 2]

  • Context:
  • Options:
  • Goal:

Resources Mentioned or Requested

To be filled out during or after meeting

Access and Credentials

  • [System access needed]
  • [API keys or credentials]
  • [Repository or code access]

Documentation

  • [Architecture diagrams or technical docs]
  • [Feature specifications or mockups]
  • [Existing code or examples to reference]

Data and Samples

  • [Data exports for validation]
  • [Sample items for pilot testing]
  • [Historical data for modeling]

Notes

Space for additional notes during the meeting

Technical Discoveries

Concerns or Red Flags

Quick Win Opportunities

Decisions Made (if not captured above)

Quotes or Verbatim


Follow-up Actions Summary

Quick reference, detailed action items are in Next Steps section above

OwnerActionDue DatePriority
[Name][Task][YYYY-MM-DD]High/Medium/Low
[Name][Task][YYYY-MM-DD]High/Medium/Low

Meeting Success Criteria

By end of this call, we should have:

  • [Specific outcome 1]
  • [Specific outcome 2]
  • [Specific outcome 3]
  • No major surprises that would change timeline or scope