This template is designed to bring clarity and structure to technical discussions, ensuring critical decisions, code references, and action items are accurately captured. It helps prevent information decay, accelerates onboarding for new team members, and provides a reliable source of truth for all engineering activities, from daily standups to architectural reviews.
Meeting Logistics
Sprint Planning, Daily Standup, Architecture Review, Incident Post-Mortem
Specify the type of meeting to categorize notes effectively.YYYY-MM-DD HH:MM (e.g., 2023-10-27 10:00 AM PST)
Record the exact date and time the meeting took place.Jane Doe (Staff Engineer)
Note the person responsible for leading the meeting.John Smith (Dev Lead), Alice Brown (DevOps), Bob White (Data Eng)
List all participants, including their roles or teams.Finalize Sprint 5 backlog, review API gateway design, analyze recent production incident
Clearly state the primary objective or purpose of the meeting.Discussion Points & Key Takeaways
Database migration strategy, Microservice communication patterns, CI/CD pipeline improvements
Outline each distinct topic discussed during the meeting.Explored pros/cons of DynamoDB vs. PostgreSQL for new service. Decided to proceed with PostgreSQL due to existing team expertise and complex query needs.
Provide a concise overview of the conversation and key points raised for each topic.Decision: Use gRPC for inter-service communication. Rationale: Performance, schema enforcement, multi-language support.
Document explicit decisions, including the rationale and alternatives considered.Choosing synchronous REST API over async messaging for initial MVP due to simpler implementation, accepting potential future scalability re-work.
Detail any compromises or technical trade-offs acknowledged and accepted.Code & Resource References
https://github.com/org/repo/pull/1234 (Auth Service Refactor), `git diff feature-branch main`
Link directly to relevant code, pull requests, or specific code diffs discussed.Confluence: 'Payment Service Architecture v2', Miro board: 'Data Flow Diagram'
Reference any architectural documentation, diagrams, or design specifications.Blog post: 'Patterns for Distributed Transactions', AWS documentation on SQS
Include links to external articles, research, or vendor documentation pertinent to the discussion.Action Items & Owners
Investigate latency issues in `UserService.authenticate()` endpoint.
Clearly state the task that needs to be performed.Alice Brown (DevOps)
Assign the specific individual responsible for completing the action.2023-11-03
Set a realistic deadline for the completion of the action item.To Do, In Progress, Blocked, Done
Track the current state of the action item.Open Questions & Follow-ups
What is the error handling strategy for third-party API failures? Do we need a dedicated data governance policy for the new data lake?
List any questions that arose but were not fully resolved during the meeting.Schedule a follow-up meeting on Friday to discuss database indexing performance. John to research caching options for `/product` endpoint.
Outline immediate next steps or plans for future discussions.How to Use This Template
- **Select Template:** Open CraftNote, navigate to 'Templates', and select the 'Technical Meeting Notes' template.
- **Fill Logistics:** Begin by filling out the 'Meeting Logistics' section with details like meeting type, date, attendees, and the primary goal.
- **Capture Discussions:** As topics are discussed, use the 'Discussion Points & Key Takeaways' section to summarize conversations, document decisions, and note technical trade-offs.
- **Link Resources:** For any code, architecture diagrams, or external documentation mentioned, utilize the 'Code & Resource References' section to link directly to them.
- **Assign Actions:** Before concluding, clearly define all 'Action Items', assign 'Owners', and set 'Due Dates' to ensure accountability and follow-through.
Customization Tips
- **Adapt for Meeting Type:** For daily standups, focus on 'Discussion Points' (what was done, what will be done, blockers) and 'Action Items'. For architecture reviews, expand on 'Code & Resource References' and 'Technical Trade-offs'.
- **Integrate with Tools:** Customize fields to include direct links to your team's project management tool (e.g., Jira ticket IDs), version control (e.g., GitHub issue numbers), or documentation platform (e.g., Confluence page IDs).
- **Add Pre-meeting Prep:** Include a 'Pre-Read Materials' field in the 'Meeting Logistics' section to ensure attendees review necessary documents beforehand, improving meeting efficiency and focus.