Remote work

Too Many Meetings, Not Enough Work: A Remote Work Reset

You were on calls all day. Somehow the work you were supposed to do is still waiting. The problem may be the shape of your calendar, not your ability to concentrate.

It's 4:17 p.m. You have attended the daily stand-up, a project check-in, an unexpected “quick sync”, a planning call and the meeting that could only happen once everyone's schedule was clear. You have been professional, helpful and fully present.

You have not touched the thing you needed to finish.

This is one of the peculiar frustrations of remote work. You can be genuinely busy and still have very little to point to at the end of the day. Worse, the unfinished work often moves into the only space left: your evening.

The usual advice is to decline more meetings. That helps if you control your calendar. Many people don't. The better question is: how can meetings leave enough room for the actual work, without making collaboration somebody else's problem?

First, recognise the kind of meeting-heavy day you have

A meeting isn't wasteful merely because it took time. Some conversations prevent a week of confusion. Some help a new colleague feel less alone. Some resolve a disagreement that was getting worse in writing.

But calendars usually don't distinguish those from meetings held because no one wants to make a decision in a document.

Look at your next week and mark each meeting in one of three ways:

  • Decide: a decision needs to happen with several people at once.
  • Work together: the group is building, investigating or rehearsing something in real time.
  • Broadcast: one person is mostly telling others things they could read.

The first two may genuinely need a call. The third is a candidate for a written update, a recording, or an optional office-hours slot. This is not a universal rule. Complex topics can be easier face to face, and some colleagues benefit from conversation. The categories simply give you a more useful question than “Is this meeting annoying?”

Count the fragments, not only the hours

Two hours of meetings arranged back to back can leave a useful afternoon. The same two hours spread across eight half-hour gaps can turn the whole day into preparation, call, recovery and preparation again.

The lost resource is continuity. You can read an email in a small gap. It's harder to make the difficult argument, code the complicated change or design the new process when you know somebody will want you in seventeen minutes.

Microsoft's 2025 Work Trend Index reported that, on average in its measured population, workers were interrupted by a meeting, email or message roughly every two minutes. That is a workplace-wide figure, not evidence that every remote worker personally receives the same number of interruptions. Still, it points to a real tension between communication and concentration.

What the research measures

Microsoft's 2025 Work Trend Index combines Microsoft 365 telemetry and survey research, reporting frequent digital interruptions across its observed knowledge-work population. It does not prove a particular meeting schedule is right for everyone. Read Microsoft's original report ↗

Protect one piece of uninterrupted work before adding more meetings

Instead of trying to rescue the entire week, choose one task that requires sustained thought. Put a realistic block in your calendar, ideally at a time when you have some energy and fewer cross-team dependencies.

Give the block a description that helps other people respect it: “Draft client proposal, deadline Thursday” is clearer than “Busy”. If your team uses shared calendars, the aim is to make actual project work visible, not to manufacture an excuse to disappear.

Then protect it with an interruption policy. If something urgent happens, of course you respond. For routine messages, tell colleagues when you'll check back. Silence non-urgent notifications for that window. Leave a brief note about the precise next action before you start, so one unavoidable interruption doesn't erase the whole session.

And don't schedule four uninterrupted hours for a task you can only begin in fifteen-minute bursts. One honest 35-minute block beats an impressive calendar appointment that never survives contact with Tuesday.

Write invitations that earn people's attention

The easiest meeting to improve is sometimes the next one you organise.

A meeting invitation with a reason to exist

Decision needed: Choose between launch date A and launch date B.

Read beforehand: One-page comparison, linked here.

People needed: Owner of delivery, owner of support, decision-maker.

Time: 20 minutes.

Outcome: Named decision, owner and next step recorded in the project.

If participants can make the decision in the document beforehand, cancel the meeting and return everyone's time.

Notice what this changes. The invitation is no longer “discuss project status”. It makes the collaboration finite. Everyone can prepare in different time zones, and the final outcome has somewhere permanent to live.

How to push back without sounding unhelpful

Most people are not looking for a dramatic stand against meetings. They want to be useful without losing the whole day. A smaller, warmer question often works better than declining silently.

When you're invited only for an update

“Happy to help. I can put my update in the project document before the call. Would that cover what you need, or is there a decision you'd like me there for?”

When two calls overlap your one work block

“I'm working on the Thursday deliverable during that slot. Could I send my notes ahead and join for the decision, or would another time work?”

When the call keeps growing

“Could we agree what we're deciding in this meeting? The other questions feel useful, but I think they need separate owners.”

These are invitations to collaborate better, not excuses to refuse shared responsibility. If your role requires the meeting, attend it. Then talk with the person who can change the recurring pattern rather than fighting every calendar invitation individually.

Use the ten minutes after a call

If you cannot control the morning, you can often control the first ten minutes after a meeting. Before you open messages, write down the decisions, owners and follow-ups while they're still clear. Put each task where it belongs, not in your memory.

Then choose deliberately: is there enough time and mental energy to return to a complex task, or is this a sensible moment for administrative work? The point is not to force deep work into every 12-minute gap. It's to stop the gaps filling themselves.

When a meeting interrupts something important, leave a re-entry line: “next: check the third figure against the source”, or “still need customer example for paragraph two”. Read it after the call rather than restarting from scratch.

A better remote team doesn't mean a calendar with no meetings

Human contact matters, particularly for people whose working day can otherwise feel solitary. A one-to-one with a manager, a collaborative problem-solving session, or a casual conversation with a colleague can be worth far more than the minutes it consumes.

The aim is to keep calls that produce connection, decisions and progress, and question the ones that mostly reproduce information people already have.

A small Calphii thought
Collaboration should make the work possible, not consume all the hours in which you could do it.

Run the seven-day calendar audit

At the end of each working day, write one sentence: Which meeting changed what happened next? Keep the useful ones. For one low-value recurring call, propose a two-week experiment with a written update and clear escalation path. For one important task, schedule a protected block and see whether you actually use it.

Inside Calphii, a single visible task, a quick note and Deep Focus can make that protected block feel like a place to return to. But the first fix is often outside the app: changing which demands get the right to interrupt you.

If you often find yourself losing the thread between calls, read our short interruption recovery guide. If colleagues work far apart, try our practical guide to asynchronous collaboration.