There’s a particular kind of tired that has nothing to do with how much work you actually did. You close your laptop at 6pm, and when someone asks what you accomplished today, you genuinely struggle to answer. You were in meetings. You remember that much. Four of them, maybe five, back to back, each one bleeding into the next until the whole day felt like a hallway you walked through without ever entering a room.
If that sounds familiar, you’re not imagining it, and you’re not bad at your job. You’re living inside a calendar system that was never designed for the kind of work most of us actually do.
The Meeting That Ate Your Day
Somewhere along the way, “being productive” quietly turned into “being available.” A full calendar started to look like proof of importance, when in practice it’s often the opposite: the fuller your calendar, the less room you have to do the work that actually moves anything forward.
The numbers back this up more than most people expect. Knowledge workers now spend somewhere between 11 and 12 hours a week in meetings, roughly a quarter to a third of the entire workweek, and a large share of that time is widely considered unproductive by the very people sitting in it. Add in the scheduling itself, the calendar Tetris of finding a slot everyone can attend, and you’ve lost hours before a single decision gets made.
This isn’t a Silicon Valley problem or a corporate-office problem. A founder juggling investor updates in Lagos, a developer on a distributed team split across three time zones, a small design studio in Manila coordinating with clients in Berlin: everyone doing knowledge work in 2026 is fighting the same calendar. Distributed teams made this worse before anyone noticed, because the instinct when you can’t walk over to someone’s desk is to book a call instead. It felt like connection. Mostly it was just noise wearing a calendar invite.
Why “Just Cancel Your Meetings” Doesn’t Work
The obvious advice, the kind that shows up in every listicle about productivity, is to simply have fewer meetings. Say no more often. Protect your calendar. It’s not wrong, exactly, but it’s incomplete, and incomplete advice is why most people try it for two weeks and quietly give up.
The reason it fails is that meetings usually exist to solve a real coordination problem: how does everyone stay aligned without constant real-time contact? If you cancel the meeting without replacing that function, the alignment problem doesn’t disappear. It just resurfaces later as confusion, duplicated work, or someone finding out three days late that a decision was already made. Cutting meetings without a system behind it isn’t a fix. It’s a delay.
This is also where many people make the mistake of reaching for a new app instead. Another dashboard, another notification channel, another tool promising to “streamline collaboration.” I’ve written before about the one-tool rule and why stacking more software rarely solves a habit problem. Meeting overload is a habit and culture problem wearing a scheduling costume. No calendar app fixes that on its own.
What the Data Actually Shows About Async Work
Asynchronous work, at its core, is simple: you communicate without requiring everyone to be present at the same moment. Written updates instead of status calls. A short recorded video instead of a live walkthrough. A shared document that carries the decision instead of a meeting that only three of the seven attendees actually needed to be in.
It sounds almost too basic to be a strategy. But teams that commit to it seriously see results that are hard to dismiss.
One widely cited piece of research from MIT’s Centre for Information Systems Research found that teams cutting their meeting load by around 40% saw productivity climb by roughly 71%, a gap large enough that it’s worth sitting with for a second. That’s not a marginal tweak. That’s a fundamentally different relationship with time. You can read more on how that research on meeting reduction breaks down.
TechSmith ran a smaller, more human version of the same experiment. In 2022, the company eliminated meetings entirely for a month across its workforce, forcing everything into async channels. The result: over 15% more employees reported feeling genuinely productive, and even the meetings that survived the experiment were later rated as more valuable, because only the ones that truly needed real-time discussion made the cut.
And this isn’t a fringe movement anymore. Companies that formally adopt an async-first default, meaning the assumption is written communication unless a situation specifically calls for live discussion, report roughly 25% fewer meetings almost immediately. You can dig into more of that async-first adoption data if you want the fuller picture. The pattern across every study points the same direction: most of what happens in a meeting didn’t need to happen live.
Sync vs. Async: Knowing Which One a Task Actually Needs
The mistake people make when they first hear about async work is treating it as all-or-nothing, as though the goal is zero meetings. That’s not the goal. Some things genuinely need real-time human contact. The skill is knowing which is which.
| Type of Work | Best Format | Why |
| Status updates | Async (written or short video) | No live discussion needed, just information transfer |
| Complex decisions with disagreement | Sync | Nuance and tone get lost in text; faster to resolve live |
| Onboarding a new hire | Mixed | Some live rapport-building, most reference material async |
| Brainstorming | Sync (small group) | Ideas build on each other in real time |
| Progress check-ins | Async | Recurring, low-stakes, rarely needs discussion |
| Crisis or urgent blocker | Sync | Speed matters more than documentation in the moment |
| Client updates | Async, with sync available on request | Respects client’s time zone and schedule |
Once you start sorting your actual meetings against a table like this, something uncomfortable usually happens: you realise most of what’s on your calendar belongs in the left column, not the right one.
The Attention Cost Nobody Puts on the Calendar
There’s a second cost to constant meetings that rarely gets counted, and it’s not about time. It’s about attention. Jumping from a client call to a team standup to a quick sync with a designer isn’t free just because each individual meeting is short. Every switch costs you the mental runway needed to actually think. Some research suggests the average person’s attention shifts tasks roughly every 47 seconds during a normal digital workday, and meetings compress that fragmentation into overdrive.
This connects to something I explored in the cognitive offloading piece: the more your day is chopped into reactive fragments, the less capacity you have left for the kind of sustained, original thinking that actually builds things. A calendar full of thirty-minute blocks doesn’t just steal your hours. It steals your ability to go deep in the hours you have left.
Building an Async-by-Design Workday
Knowing the theory is one thing. Actually restructuring how you work is another, and this is where most productivity advice quietly stops being useful. So here’s a practical way to approach it.
Start with an honest audit. Pull up your calendar for the last two weeks and sort every recurring meeting into one of three buckets: keep, kill, or convert to async. Be ruthless. If a meeting exists purely to share status that could’ve been a two-paragraph update, it goes in the convert pile. If nobody can clearly say what decision it produces, it goes in the kill pile.
Make documentation the default, not the afterthought. This is the part people skip because it feels slower upfront. It isn’t, once the habit sets in. A written update that takes ten minutes to compose can replace a thirty-minute meeting for six people, which is a net savings of two and a half hours of collective time for a ten-minute investment. The math isn’t close.
Protect actual focus blocks. Two or three uninterrupted windows a day, even 90 minutes each, do more for real output than an entire week of thirty-minute meetings stitched together. Put them on the calendar as if they were meetings with someone important, because they are: they’re meetings with the work itself.
Set response-time norms instead of always-on expectations. Async only works if people trust that a message will get a reply within a reasonable window, not instantly. Agreeing on that window, whether it’s two hours or by end of day, removes the anxiety that usually drives people back toward live calls out of habit.
Revisit the audit monthly. Habits drift. A meeting you correctly killed in January can quietly creep back by March if nobody’s watching. Treat the audit as a recurring practice, not a one-time cleanup.
Making This Work Whether You’re Solo or Leading a Team
If you’re a solo builder or freelancer, async-by-design might sound like it doesn’t apply to you since you’re not managing a team calendar. It applies more than you’d think. Client communication is often where solo operators lose the most time to unnecessary live calls that could’ve been a Loom video or a clear written proposal. Setting the expectation early that updates come async by default and calls happen when something genuinely needs discussion protects your time without making you seem unavailable.
For small teams and startups, the TechSmith model is worth borrowing directly: pick a low-stakes month, strip meetings down to only the ones that survive real scrutiny, and measure how people actually feel afterwards. You don’t need permission from a large organisation to run this experiment. You need a calendar and the discipline to say no to the reflexive “let’s hop on a call” for two or three weeks.
None of this requires new software, though a shared documentation space and a simple async video tool help. If you’re looking for lightweight options that support this shift without adding another subscription to track, our tools directory has a running list worth browsing.
Frequently Asked Questions
Does async-first mean cutting out meetings completely?
No, and treating it that way is the fastest way to break something that was working. The goal is matching the format to the task, not eliminating live contact altogether. Complex, high-stakes, or emotionally sensitive conversations still deserve real time together.
How do distributed teams handle urgent decisions without a meeting?
Urgent doesn’t automatically mean it needs to be a scheduled meeting. Most urgent blockers get resolved faster through a direct message thread with the two or three people actually needed, not a calendar invite that waits for everyone’s next open slot.
Which meeting should I cut first?
Start with any recurring meeting where attendance feels optional for more than half the invite list. If people are quietly multitasking through it, that’s usually your answer.
Does async work slow down onboarding new team members?
It can if it’s poorly documented, but done well it often speeds things up. New hires get a searchable record of decisions and context instead of relying on memory from a live call they may have half-listened to on their third day.
Where This Actually Leaves You
None of this is about working less. It’s about working on purpose. A calendar that’s full doesn’t mean a day that’s productive, and a quiet inbox doesn’t mean nothing is happening. The teams and individuals getting real traction in 2026 aren’t the ones with the fanciest scheduling tool. They’re the ones who got honest about which conversations actually needed everyone in a room, live, at the same time, and which ones were just habit dressed up as collaboration.
That’s the whole idea behind exploring how something works before trying to fix it. Cut the meetings that never needed to exist, protect the hours that are left, and you’ll find the work itself takes up a lot less of your day than the noise around it used to.
Discover more from ediccrew
Subscribe to get the latest posts sent to your email.
