If You Have More Than 5 Calls a Day, It's Time to Quit. Or Start Doing This

A practical guide to combating meeting overload in remote teams, covering why excessive video calls drain productivity and how to replace them with asynchronous communication, structured agendas, and conscious meeting refusal.

Here's what a typical day looks like:

  • 10:00 — daily standup
  • 11:00 — sync on new feature
  • 13:00 — demo
  • 15:00 — "quick" call
  • 16:00 — another call
  • 17:30 — retro
  • 18:30 — finally can work

One evening, management called me at 10 PM. That's when I decided to resign. But then I discovered there were solutions.

Why We Got Here: Meeting Dependency

The problem intensified during COVID lockdowns. Managers felt obligated to schedule video calls as a substitute for in-person interaction. Years later, many organizations still rely heavily on meetings.

Stanford researchers coined the term Zoom fatigue to describe the exhaustion that follows video calls — the brain tires faster, attention scatters, and constant visibility creates discomfort.

Why Meetings Frustrate People

1. No Clear Agenda

According to research: "64% of regular and 60% of one-time meetings occur without clear objectives. Decisions are made at only 37% of meetings."

Meetings become habit ("we have a meeting Thursday") rather than necessity. People are invited vaguely to "discuss a task," conversations meander, and forty minutes pass without structure.

2. Inviting Everyone "Just in Case"

Typical demos or planning sessions: ten people on screen, three silent for an hour, two completely lost, others rotating "no questions." Adding 15-20 more people creates the corporate classic: the "all-hands meeting."

Research on the Ringelmann effect shows that larger groups produce less effort per person because "nine others will figure it out anyway." 42% of employees admit turning off cameras and working on other tasks.

3. Cameras Off = Lost Connection

I once conducted a demo for twenty department members — all with disabled cameras. Repeated requests to enable them met silence, like teaching middle schoolers playing Dota in parallel.

The opposite extreme: mandatory cameras "so management sees engagement." I invented excuses (illness, connection problems) to avoid pretending.

4. Unannounced Calls

Messages like "got a minute?" followed by sudden calls interrupt deep work. For introverted people, every Telegram notification triggers anxiety.

5. Meetings for Minor Issues

"Can we voice chat?" starts a call for questions solvable in one task tracker comment. Usually stems from self-doubt: "I'll explain better verbally."

6. Lateness

Meeting scheduled for 11:00, organizer arrives at 11:07 saying "sorry, was on another call." These meetings are "almost a third less productive." Waiting time fills with random chatter; focus never restarts.

7. Unexpected Performances

Cats on keyboards. Screaming children everyone pretends to find adorable. One colleague's husband emerged from the shower during her quarterly presentation to 500+ people.

GitLab treats this as normal (encouraging family appearances), but Russian corporate culture differs significantly.

Solutions for Meeting Organizers

Asynchronous Communication as the Foundation

GitLab operates under a "default to async" philosophy with comprehensive guides.

Five practical rules:

1. Discuss tasks in task trackers, not Zoom

Using YouGile (free for small teams), every task includes a chat for file-sharing and clarifications.

2. Record explanatory videos

For mockup comments, record brief screencasts directly in the chat for flexible reviewing.

3. Auto-collect status reports

Rather than asking "how's the task?", check the system first. I configured weekly employee task reports and status summaries — dynamic reports collecting tasks by criteria in single columns (overdue tasks, stalled tasks, sprint-incomplete tasks).

4. Skip other departments' meetings

Subscribe to relevant tasks, receive notifications only for significant changes — no need to attend their calls.

5. Set reminders

Create task reminders: "check issue in 24 hours" to avoid bugging people and eliminate waiting.

Optimization Strategies

1. Break the scheduling habit

Not all meetings are necessary — though admitting this feels obvious, it's the hardest step.

Justified meetings:

  • Retros and planning
  • Strategic discussions
  • Crisis resolution
  • Regular 1:1s (measured)
  • Live brainstorming

Unjustified (just laziness):

  • Task status updates
  • Five-minute clarifications
  • Project updates
  • Basic reporting

2. Reduce call duration

Default practice: schedule everything for one hour. I cut meetings to five minutes — nothing changed except everyone gained work time. Next challenge: thirty minutes.

3. Prepare beforehand

Before 1:1 meetings, open the specific employee's task list. Issues and blockers become immediately visible; conversation stays focused.

4. Structure your thinking

First verbalize, then write. AI tools help: dictate scattered thoughts, request organization, then send to team.

5. Replace video with voice messages

When tone matters, use voice messages in the tracker (auto-transcribed), leaving text and replay option.

Agendas Aren't Formalities

GitLab's rule: "No agenda, no attenda." Agendas function as living Google Docs, edited collaboratively during meetings.

Three steps:

  1. Start every meeting asking: What do we want to solve? This single question redirects conversation immediately.
  2. Use templates: create reusable calendar templates with attendee agendas.
  3. Send agendas in advance.

Example comparison:

VagueClear
Project updatesFix blocker status + rebuild task plan for new deadline
Feature questionsAnswer team questions to hand off feature to development

Meetings Without Results = Wasted Time

I always document outcomes — either myself or by requesting a volunteer note-taker. Avoid lengthy protocols; record: decision, responsible parties, deadline. Update the task tracker immediately.

For comprehensive capture, I use the tl;dv browser extension: it records Google Meet/Zoom, auto-transcribes, and highlights key points.

Don't Invite Everybody

Core principle: meetings are a direct labor expense. More attendees = higher cost.

Research: 42% of participants don't speak at all.

Before inviting: "Is this person a participant or an observer?" Observers get a summary in the task chat with a mention.

For Exhausted Individual Contributors

Sometimes your calendar feels like prison. Three practical tactics:

1. Block personal time

An empty calendar invites chaos — others schedule anything. Block morning time: coffee, thinking, daily review.

2. Learn to decline without guilt

Hardest thing: saying "no" to irrelevant meetings.

Initial concern: rejection. Reality: honest communication works. Sample phrases:

  • "Seems I'm not valuable here. Send the summary to the task chat — I'll review and jump in if needed."
  • "Better in writing? I'm swamped — written answers are faster."
  • "Can't join, but let me know if something critical comes up — happy to help."

Asana actively encourages conscious meeting refusal when unnecessary. This represents mature professional positioning.

3. Propose different formats

At one startup, daily 9 AM Zoom calls started meetings before people understood where they were. Low value: people mumbled, nodded, left.

I proposed: write plans to chat by 10:30, sync by call only for problems weekly. The team immediately supported this.

Some Russian companies implement "meeting-free days" (e.g., Wednesdays). Formally this saves time and money; practically it provides breathing room.

Summary

Meetings become torture when stripped of purpose.

Want a real conversation? Meet in bars or coworking spaces. Need task clarity? Write comments. Really need a call? Keep it brief, agenda-driven, and result-focused.

Communication is a skill like any other — develop it if you want time for actual work.

Key statistics from the article:

  • 64% and 60% of meetings lack clear objectives
  • Decisions are made at only 37% of meetings
  • 51% of employees work overtime due to excessive meetings
  • 67% of managers work overtime for the same reason
  • 42% disable cameras and work on other tasks
  • Meetings without agendas are "a third less productive"

FAQ

What is this article about in one sentence?

This article explains the core idea in practical terms and focuses on what you can apply in real work.

Who is this article for?

It is written for engineers, technical leaders, and curious readers who want a clear, implementation-focused explanation.

What should I read next?

Use the related articles below to continue with closely connected topics and concrete examples.