Meetings
Overview
Meetings are for decisions, alignment, and unblockers when text is not enough.
Why It Matters
Poor meetings waste time, but good meetings can move a team faster than endless messaging.
Core Concepts
- A meeting needs a purpose.
- Decisions should be captured.
- The output should be clear.
Mental Models
Meet only when synchronous discussion creates more value than async communication.
Best Practices
- Share context beforehand.
- Timebox discussion.
- End with owners and next steps.
Common Mistakes
- Scheduling without a goal.
- Letting meetings drift.
- Leaving decisions undocumented.
Trade-offs
Meetings cost focus time, but they can reduce ambiguity faster than messages when the topic is complex.
Decision Framework
| Need | Meeting? |
|---|---|
| Simple status update | Usually no |
| Trade-off discussion | Yes |
| Decision requiring alignment | Yes |
Examples
- Use a short sync to unblock a design choice, then document the outcome.
Checklists
- Is there a clear purpose?
- Are the right people invited?
- Is the output documented?
Senior Engineer Notes
Senior engineers make meetings useful by preparing, focusing discussion, and capturing outcomes.