Engineers hate meetings for a reason: most meetings that include engineers shouldn't. Status updates that could be a PR comment. Decisions that could be a 30-second async Slack thread. Syncs that exist because the manager doesn't trust async communication.
But engineers who claim they should never be in meetings are also wrong. The question is which meetings are worth it and how to run the ones that are.
The meetings engineering teams should cut
Daily standups longer than 10 minutes. A standup is a synchronization point, not a status report. If someone is explaining their work for more than 90 seconds, the standup has become a meeting about a meeting. Cut to: what's blocked, what's being handed off, what's done. Everything else goes in the ticket.
Meetings without an agenda sent in advance. If the organizer doesn't know why the meeting exists before it starts, the participants definitely don't. An agenda doesn't have to be formal — a two-line Slack message explaining the decision to be made is enough.
"Alignment" meetings that are actually information broadcasts. If the goal is to tell people something, write it down. If the goal is to make sure they understood it, ask them to comment. If the goal is to handle questions, do a short async Q&A thread. A live meeting for information distribution is scheduling overhead for everyone attending.
The meetings engineering teams should keep (and run better)
Architecture decisions with real tradeoffs. Async ADR (Architecture Decision Record) threads work for decisions where the tradeoffs are clear. When the right call is genuinely ambiguous — new infrastructure pattern, security model, API contract that multiple teams depend on — a focused synchronous session with the right people in the room reaches a decision faster than a week of async back-and-forth.
Incident retrospectives. Blame-free post-mortems require real-time conversation to work. The nuance of "here's what I was thinking when I made that call" gets lost in writing; in a live session, it builds shared understanding that async never achieves.
Sprint planning with cross-functional dependencies. When one team's output is another team's input, synchronizing that in real time once per sprint prevents a week of misaligned work that could have been avoided in 30 minutes.
1:1s. These are relationship and growth conversations. Async has no substitute.
How to make the necessary meetings shorter
Start with the decision, not the context. Engineers in a meeting already have context — that's why they're in the meeting. Start with "here's the decision we need to make and why" rather than rebuilding context that everyone already has.
Timebox and respect the box. A 30-minute meeting that ends at 28 minutes trains your team that meetings are efficient. A 30-minute meeting that runs 45 minutes trains them that the scheduled time is a suggestion.
Close with explicit action items. "We should look into X" leaves the meeting without an owner. "Sara will check the latency numbers and post by Thursday" leaves with accountability. The difference between meetings that produce results and meetings that produce more meetings is this habit.
The tooling angle
Engineering teams have a higher-than-average tolerance for async and a higher-than-average allergy to meeting overhead. Platforms that reduce meeting overhead — AI that automatically captures decisions and action items so engineers don't have to take notes — are particularly well-received in engineering culture.
MeetOye is built around this: Oya generates a structured recap of every meeting automatically, so engineers can focus on the conversation rather than split attention between discussing and documenting. Decisions and action items are captured and emailed to every attendee when the call ends — which means "did we actually decide that?" is answerable from the transcript rather than from memory.
Author bio:
The MeetOye Team builds AI-native meeting software used by engineering and product teams. MeetOye (meetoye.com) automatically transcribes and recaps every call, so the discussion stays focused and the record takes care of itself.
Top comments (0)