Running Effective Engineering Meetings

By Michael Samuel Naeem · January 8, 2025 · 6 min read

The average engineer spends 10–18 hours per week in meetings. Half of that time produces no decision, no action item, and no information that couldn't have been a three-paragraph doc. I've sat in hour-long "syncs" that ended with "let's take this offline" — meaning the meeting had no purpose. Effective meetings are short, have agendas, produce outcomes, and respect that every attendee's time is worth more than the organizer's convenience.

Meeting types that earn their time

Everything else should justify its existence quarterly.

Standup that doesn't suck

Format: Round-robin, timed.

Yesterday: Shipped payment retry (PR #412). 
Today: Starting webhook signature verification.
Blockers: Need API rate limit decision from PM.

Rules:

• No laptops (optional but effective)
• No problem-solving — "I'll sync with you after"
• Blockers get an owner and a time, not a discussion
• Cancel standup if nothing to coordinate (async update instead)

For distributed teams, async standup in Slack/Linear works better than a video call where half the team is muted doing other work.

Design review structure

Before the meeting:

1. Author publishes design doc (problem, options, recommendation)
2. Reviewers comment async for 24 hours
3. Author addresses comments, updates doc

During the meeting (45 min):

• 5 min: Author summarizes problem and recommendation
• 25 min: Discuss unresolved comments and tradeoffs
• 10 min: Decision — approve, revise, or defer
• 5 min: Document action items

The doc is the artifact. The meeting is for disagreement and decision, not presentation.

Retrospectives that change things

Bad retro: "what went well? what didn't?" → vague answers → same problems next sprint.

Good retro structure:

1. Data first: Metrics (incidents, velocity, escaped bugs) — 5 min
2. Individual write: Everyone writes 1 keep, 1 change, 1 try — 5 min silently
3. Discuss top themes: Vote on items — 20 min
4. Action items: Max 3, each with owner and due date — 10 min
5. Review last retro actions: Did we do them? — 5 min

If retro action items never get done, the team stops participating. Follow through or stop having retros.

Meeting hygiene

Every meeting invite needs:

• Agenda (what decisions will be made)
• Pre-read links
• Expected outcome ("decide X" not "discuss X")

During:

• Timekeeper (not the facilitator)
• Notes taker (rotate role)
• Parking lot for off-topic items

After:

• Action items with owners sent within 30 minutes
• No action items = meeting probably didn't need to happen

Killing unnecessary meetings

Audit quarterly:

• Meetings with < 50% attendance → reschedule or cancel
• Recurring meetings with no action items for 3 sessions → cancel
• "Status sync" that duplicates written updates → async
• Meetings you attend but never speak in → decline

Declining meetings is a skill. "I don't think I can contribute to this — can you share notes?" is professional.

The async alternative

Replace meetings with:

• Design docs for decisions (comment async, meet only if unresolved)
• Recorded Loom for demos (watch at 1.5x, comment in doc)
• Slack threads for quick alignment
• Written weekly updates for status

My team's rule: if a meeting could have been a doc, the person who called the meeting writes the doc next time instead.

Meeting types and their formats

Different meetings need different structures — one format doesn't fit all:

Decision meetings without pre-circulated proposal default to the loudest voice winning. Require written context before scheduling.

The written decision record

Every decision meeting produces a record:

## Decision: Migrate from Postgres to CockroachDB

**Date:** 2024-12-27
**Participants:** alice, bob, carol
**Decision:** Proceed with CockroachDB for new services; existing Postgres unchanged
**Rationale:** Multi-region requirement for EU expansion; CockroachDB native geo-distribution
**Dissent:** bob preferred Vitess — noted, not blocking
**Action items:**
- [ ] alice: POC by 2025-01-15
- [ ] carol: cost model by 2025-01-10
**Review date:** 2025-02-01

Decisions without records get re-litigated. The doc is the decision — the meeting was the discussion.

Remote meeting hygiene

Remote meetings fail differently than in-person:

• Camera optional, engagement required — async reactions in chat count
• Record by default — absent stakeholders watch at 1.5×
• No hybrid without remote-first design — in-room side conversations exclude remote attendees
• 5-minute buffer between meetings — no back-to-back Zoom marathons
• Shared doc as primary surface — not screen share of presenter's notes

Meeting norms (team agreement):
- Agenda required 24h before — no agenda, meeting cancelled
- Hard stop at scheduled end — remaining items become async
- Action items in shared doc during meeting, not after
- "Could this be a Slack thread?" asked before scheduling

Failure modes

• No agenda — meeting meanders, no decisions made
• Status meeting that duplicates written update — wasted time for all attendees
• Decision without pre-circulated context — loudest voice wins, not best argument
• No action items recorded — same discussion repeats next week
• Recurring meeting with no output for 3 sessions — zombie meeting, cancel it

Production checklist

• Agenda required before scheduling — no agenda, no meeting
• Decision meetings require written proposal circulated 24h before
• Action items with owners sent within 30 minutes of meeting end
• Quarterly audit: cancel meetings with <50% attendance or no action items
• Remote-first design for hybrid meetings
• Written decision record for every decision meeting

Resources

• Amazon — two-pizza teams and meeting culture
• Basecamp — Meetings are toxic (calibrated take)
• Google re:Work — running effective meetings
• Atlassian playbook — retrospectives
• StaffEng — Writing design docs