Your Calendar Is Lying to You: The Case for Skipping Meetings That Steal Your Best Hours

Open your calendar right now. Really look at it. How many of those colored blocks are genuinely, irreplaceably necessary? How many could have been a shared doc, a Slack thread, or — honestly — nothing at all?

If you work in tech, consulting, or any hybrid-remote environment in the US, there's a decent chance your week is structured around meetings the way a bad city is structured around highways: everything technically connects, but getting anywhere feels exhausting and the whole thing kind of ruins the experience of being there.

We've built a culture where calendar density signals commitment. Where showing up on video — even glazed-eyed, even half-present — reads as participation. And somewhere in all of that, the actual work got squeezed into the margins.

The Real Cost of a One-Hour Meeting

Here's the thing most meeting invites don't tell you: a one-hour meeting rarely costs one hour.

Neuroscientists who study attention and cognitive load have found that switching between different types of thinking — say, from deep analytical work to a synchronous group conversation and back again — takes a measurable toll. Your brain doesn't just pause and resume like a podcast. It has to fully disengage, recalibrate, and rebuild context each time. Depending on the complexity of what you were doing before, that recovery can take anywhere from 15 to 30 minutes.

So that 10am check-in? It's not eating an hour. It's fragmenting your entire morning.

Multiply that across a week of status updates, alignment calls, and recurring syncs that nobody's questioned in two years, and you start to see the real picture. It's not just lost time — it's lost cognitive depth. The kind of thinking that produces good writing, smart strategy, elegant code, or creative breakthroughs doesn't happen in the cracks between meetings. It needs room to breathe.

Why We Keep Scheduling Anyway

So why do we do it? Why does the average US knowledge worker spend somewhere between 35 and 50 percent of their workweek in meetings, according to data from Microsoft and Harvard Business Review?

Part of it is habit. Meetings are how we've always communicated in offices, and we ported that behavior directly into remote work without stopping to ask whether it still made sense.

Part of it is anxiety. Async communication can feel ambiguous. You send a message and you're not sure if it landed, if people agree, if there's tension you can't read. A meeting, by contrast, feels conclusive. You see faces. You get nods. There's an illusion of resolution even when nothing has actually been decided.

And part of it — let's be honest — is that meetings can feel productive without requiring you to produce anything. You show up, you talk, you leave. The hard thinking gets deferred. The calendar fills up and the actual work waits.

The Three-Question Filter

Before you accept your next invite (or send one), try running it through three honest questions:

1. Does this require real-time conversation? Some things genuinely do — emotionally complex discussions, live brainstorming where energy matters, relationship-building moments. Most things don't. Status updates, decisions with clear options, information that could be documented — these don't need everyone's simultaneous presence.

2. Is a decision actually going to be made here? Meetings without clear decision points tend to drift. If the agenda is vague, if the outcome is "discuss," if the same people are going to "circle back" afterward anyway — you're not meeting to decide, you're meeting to feel like you did something.

3. Could this information live somewhere searchable? One underrated cost of verbal-only communication is that it disappears. A written async update, a recorded Loom video, a shared Notion doc — these create artifacts that people can reference later, that onboard new teammates, that don't require everyone to be awake and caffeinated at the same moment.

If the answer to all three is no, you probably don't need the meeting.

What to Do Instead

Going async doesn't mean going cold. It means being more intentional about when you ask for someone's full, live attention.

Try a standing async update. Tools like Loom, Notion, or even a well-structured Slack channel can replace a weekly team check-in with something people can consume on their own schedule. The update still happens. The information still moves. But nobody has to stop what they're doing at 2pm on a Tuesday.

Use decision templates. One reason meetings proliferate is that decisions feel too complicated to make in writing. But that's often a structure problem, not a format problem. A simple shared doc that lays out the context, the options, the tradeoffs, and a deadline for input can surface a decision faster than scheduling time to talk about scheduling time to talk about it.

Protect maker hours. Some teams in SF and elsewhere have started designating meeting-free blocks — Wednesday afternoons, morning hours before noon — as protected time for deep work. It sounds simple because it is. The hard part is holding the line when someone's "quick sync" request shows up in your inbox.

Default to shorter. If a meeting truly does need to happen, start by cutting the time in half. A 30-minute window creates urgency. People come prepared, decisions get made, and everyone gets their afternoon back.

The Culture Shift Underneath All of This

None of this works if meeting culture is treated as an individual problem to solve alone. The deeper issue is organizational — a shared, often unspoken belief that presence equals productivity, that busyness signals value, that the person with the fullest calendar is somehow doing the most.

Changing that requires naming it out loud. It requires managers who protect their teams' time as fiercely as they protect their budgets. It requires companies that measure output, not attendance.

And maybe it requires a little of what we talk about a lot around here at Unplug SF: the willingness to step back, create some space, and trust that the best thinking rarely happens under a blinking cursor with six people watching.

Your best work is waiting. It's just waiting for you to close the calendar and finally let it begin.