Scrolls
4 min read
On this page

Managing Meetings

Most meetings are unnecessary. This is not cynicism — it is the empirical observation of anyone who has tracked where their time goes. A 2022 study by Microsoft Research found that the average knowledge worker spends 57% of their time in meetings, email, and chat, leaving only 43% for focused work. For engineers, where value is created during focus time, this ratio is catastrophic. The engineers who ship the most are not the ones who attend the most meetings. They are the ones who ruthlessly manage their meeting load.

The True Cost of a Meeting

A one-hour meeting does not cost one hour. It costs the meeting time plus the context-switch overhead on both sides:

True cost of a 1-hour meeting at 2:00 PM:

  1:45  Stop working, save mental state, walk to room or open Zoom
  1:50  Wait for meeting to start (it never starts on time)
  2:00  Meeting begins
  3:00  Meeting ends
  3:05  Return to desk, check Slack, check email
  3:15  Start rebuilding context on the task you were doing at 1:45
  3:30  Back to the same depth of focus

True cost: 1 hour 45 minutes, not 1 hour

A morning with 2 one-hour meetings:
  9:00 - 10:00   Meeting 1
  10:00 - 10:15  Recovery
  10:15 - 10:45  30 minutes of focus (not enough for depth)
  10:45 - 11:00  Pre-meeting shutdown
  11:00 - 12:00  Meeting 2

  Focused work accomplished: approximately 30 minutes
  Time spent: 3 hours

The worst meetings are the ones scattered throughout the day, because they fragment focus time into pieces too small for deep work.

Decline Criteria

You do not need to attend every meeting you are invited to. Here is a decision framework:

Should I attend this meeting?

  1. Is there an agenda? 
     No -> decline. "Happy to join if you share an agenda beforehand."
  
  2. Am I a decision-maker or providing critical input?
     No -> decline. "I don't think I need to be there. Send me the
     notes and I'll follow up async if needed."
  
  3. Could this be an email, Slack thread, or document?
     Yes -> decline. "Could we handle this async? I can respond
     to a doc or thread by EOD."
  
  4. Is this a recurring meeting with no clear ongoing purpose?
     Yes -> propose ending it. "Should we check if we still need
     this weekly sync?"
  
  5. Can someone else from my team attend instead?
     Yes -> delegate. "Alex can represent our team on this."

The Two-Meeting Test

For recurring meetings, apply the two-meeting test: if you attended the last two instances and added nothing and learned nothing, stop attending.

Signs a recurring meeting is not serving you:
  - You multitask during it (checking email, writing code)
  - You could not summarize what was decided if asked
  - The same topics are discussed every week without resolution
  - Your presence does not change the outcome
  - The meeting regularly runs over time

The 15-Minute Standup That Takes 45 Minutes

Daily standups are the most common meeting waste in software teams. The intention is good — 15 minutes to synchronize. The reality is often:

What happens:
  - 5 minutes waiting for everyone to join
  - Engineer 1 gives a 3-minute status update that could be a Slack message
  - Someone asks a detailed technical question (5-minute sidebar)
  - Engineer 2's update triggers a design discussion (10 minutes)
  - Three people check out mentally while two people debate
  - Meeting ends at 45 minutes
  - Nobody remembers what was decided

Fixing the Standup

Option 1: Async standup
  Everyone posts their update in a Slack channel by 9:30 AM.
  Format: "Yesterday / Today / Blockers"
  No meeting needed. If something needs discussion, start a thread.

Option 2: Strict 15-minute standup
  Rules:
  - Start on time, no waiting for latecomers
  - Each person gets 90 seconds maximum
  - No problem-solving during standup (take it offline)
  - Facilitator enforces the time limit
  - "Parking lot" for topics that need longer discussion

Option 3: Exception-based standup
  Only speak if you have a blocker or need help.
  If nobody has anything, the meeting takes 2 minutes.
  Most days, nobody has anything.

Async Alternatives

Most information-sharing meetings can be replaced with async communication. The key is choosing the right async format:

Meeting type              Async alternative
------------------------------------------------------------------------
Status update             Written update in Slack/email
Decision meeting          RFC or decision document with comment period
Design review             Design doc with inline comments
Demo/show-and-tell        Recorded video (5-10 min) with comment thread
Brainstorming             Collaborative doc where people add ideas
Sprint planning           Pre-populated board, async voting, then
                          15-min sync to resolve conflicts only
Retrospective             Anonymous form, then 30-min sync to discuss
                          only the top-voted items

When Sync IS Necessary

Not everything should be async. Some situations genuinely need real-time communication:

Keep as synchronous meetings:
  - Difficult conversations (feedback, conflicts, sensitive topics)
  - Complex technical decisions where rapid back-and-forth is needed
  - Relationship building (1:1s, team bonding)
  - Crisis response (production outage, security incident)
  - Final decision-making when async debate has reached an impasse

The pattern: use async for information transfer, sync for relationship and real-time problem-solving.

Meeting-Free Blocks

The most effective approach is to create meeting-free blocks at the team or organization level:

Options:
  - Meeting-free mornings (all meetings after 1 PM)
  - Meeting-free days (no meetings on Tuesday and Thursday)
  - Core focus hours (no meetings 9-12 for the whole team)
  - Maker schedule (meetings only on Monday and Friday)

The critical factor is that the whole team agrees. Individual meeting-free time gets overridden by team meetings. Team-level agreements stick.

Implementation:
  1. Propose the policy to your team/manager
  2. Block the time on everyone's calendar as "Focus Time"
  3. Set Slack DND for the team during those hours
  4. Enforce it for 4 weeks before evaluating
  5. Measure output (not feelings) to justify continuing

Running Better Meetings (When You Must Have Them)

When a meeting is genuinely necessary, make it good:

Before the meeting:
  - Write an agenda with specific questions to answer
  - Share pre-reading material at least 24 hours in advance
  - Invite only the people who need to be there (5 or fewer)
  - Set the duration to the shortest reasonable time (default 25 min, not 60)

During the meeting:
  - Start on time regardless of who is missing
  - State the goal in the first 30 seconds
  - Assign a note-taker
  - Stay on agenda (parking lot for tangents)
  - End with clear decisions and action items

After the meeting:
  - Send notes within 1 hour
  - Include: decisions made, action items with owners, and deadlines
  - If no decisions were made, the meeting failed

The 25-Minute Default

Calendar tools default to 30 or 60 minutes. Change your default to 25 or 50 minutes. This gives people a buffer between meetings, prevents back-to-back meeting exhaustion, and forces you to be concise.

Parkinson's Law applied to meetings:
  A meeting expands to fill the time allotted.
  
  Schedule 60 minutes -> meeting takes 55 minutes
  Schedule 30 minutes -> meeting takes 27 minutes
  Schedule 25 minutes -> meeting takes 22 minutes
  
  The content is usually the same. The fluff gets cut.

Saying No Without Being Difficult

Declining meetings is a social skill. Do it with grace:

Templates:

"Thanks for the invite. I don't think I need to be there for this one,
 but please send me the notes and I'll follow up if needed."

"I'm in a focus block during that time. Could I get a summary afterward,
 or is there something specific you need from me that I could send async?"

"I'd love to attend but I'm overcommitted this week. Can [teammate]
 cover for our team?"

"Would it be possible to handle this via a doc? I can give detailed
 feedback in writing by tomorrow."

"I've been attending this weekly sync for a while and I don't think
 I'm adding value. Okay if I drop off and just read the notes?"

The key: always offer an alternative. Do not just say no. Say no and provide another way to get what the organizer needs.

Real-World Example: The Team That Cut Meetings in Half

A team of 6 engineers tracked their time for two weeks. They averaged 18 hours per week in meetings per person. They categorized each meeting:

Results:
  Essential (decisions requiring real-time discussion):    4 hours
  Could be async (status updates, information sharing):   8 hours
  Unnecessary (no agenda, no outcome, habit):             6 hours

Actions taken:
  - Canceled 3 recurring meetings (6 hours recovered)
  - Converted 2 status meetings to async updates (4 hours recovered)
  - Shortened remaining meetings to 25 minutes (2 hours recovered)
  
  New weekly meeting load: 6 hours per person
  Time recovered: 12 hours per week per engineer

Those 12 hours became 2-3 additional focus blocks per day. Sprint velocity increased by 40% over the next quarter.

Common Pitfalls

  • Attending meetings out of obligation — if you are not contributing or learning, your presence is wasted. Decline with a graceful alternative.
  • Accepting 60-minute defaults — most meetings can be done in 25 minutes. Change your calendar default and force conciseness.
  • Not requiring agendas — a meeting without an agenda is a meeting without a purpose. Require agendas as a condition of attendance.
  • Treating all meetings equally — a 1:1 with your manager and a 12-person status sync are completely different. Protect relationship meetings. Cut information-transfer meetings.
  • Fighting for meeting-free time alone — individual focus time gets overridden. Team-level agreements about meeting-free blocks are far more effective.

Key Takeaways

  • A one-hour meeting costs nearly two hours when you account for context-switch overhead on both sides. Scattered meetings are worse than consecutive ones.
  • Apply decline criteria: no agenda means decline. No role for you means decline. Could be async means suggest async.
  • Most status meetings should be async. Written updates, documents with comment periods, and short recorded videos replace 80% of information-sharing meetings.
  • Meeting-free blocks at the team level are the highest-impact change. Protect mornings or full days for the entire team, not just yourself.
  • When meetings are necessary, run them well: agenda, 25-minute default, specific decisions, action items with owners, notes sent within an hour.