Our Team Is 75% Remote, Yet We Schedule Meetings for Everything. What's the Fix?

General
1

I lead a 40+ person engineering team distributed across 4 time zones—Seattle, Austin, New York, and one engineer in London. On paper, we’re “75% remote” with flexible work arrangements. We have all the async tools: Slack, Notion, Linear, Loom.

Yet somehow, my calendar is still packed with meetings. So is everyone else’s.

Morning standup. Sprint planning. Design review. Architecture sync. Cross-team alignment. Tech talk. Retro. The list goes on.

The Meeting Default Trap

Here’s what keeps happening: someone has a question or needs a decision. Instead of writing it up async, they think “this will be faster if we just hop on a quick call.”

And they’re not wrong—in that moment, a 15-minute conversation IS faster than writing a detailed context doc and waiting for async responses.

But multiply that across 40 people. We’re death by a thousand “quick syncs.”

The Hidden Cost

I read research showing poorly-structured remote teams spend 33% more time on coordination than well-structured ones. We’re probably in that bucket.

Our backend team in Austin regularly has 6 AM meetings to sync with London. Our frontend team in New York regularly stays until 7 PM for “overlap hours” with Seattle. Everyone’s burned out.

The irony: we adopted remote work to give people flexibility. Instead, we’ve created a situation where people have less control over their schedules than when we were in-office.

What We Tried (That Didn’t Work)

Three months ago, I sent a company-wide email: “We’re going async-first. Default to written communication. Meetings are for decisions that require real-time discussion.”

Week one: everyone nodded and said “great idea.”

Week two: calendar exactly the same.

Why? Because I didn’t change any of the underlying systems. I just asked people to behave differently while all the incentives and defaults stayed the same.

Meetings are where decisions happen. If you’re not in the meeting, you’re not part of the decision. So everyone shows up to every meeting, just in case.

The Real Question

I keep reading about GitLab’s 2000+ employees operating fully async, or Zapier’s distributed team, or Basecamp’s 4-day work week enabled by async communication.

What are they doing that we’re not?

It’s not tools—we have the same tools. It’s not policy—we have an official “async-first” mandate. It’s not awareness—everyone on my team knows meetings are expensive.

So what is it? What organizational changes actually make async communication stick?

I suspect it’s something about:

  • How we structure work (do async-friendly tasks even exist in our sprint structure?)
  • How we make decisions (are written proposals actually read and acted on?)
  • How we reward behavior (do people get promoted for “good meeting presence” or “clear async communication”?)
  • How we model leadership (am I still defaulting to “let’s discuss this in our 1:1” instead of “write this up so the team can comment”?)

But I’m honestly not sure. Would love to hear from teams that have successfully made this shift.

Specifically:

  • What changed that made async the default instead of the exception?
  • How do you handle urgent issues without falling back to synchronous mode?
  • What meetings did you actually kill vs which ones stayed?
  • How long did the transition take?

Because right now, we’re stuck in this weird middle ground—remote-ish, but not really distributed. Async in theory, synchronous in practice. And it’s the worst of both worlds.

2

Luis, oh man, I feel this. When I was running my (failed) startup, we tried going “async-first” and failed in exactly the way you’re describing.

The problem we had: we didn’t create rituals and artifacts to replace meetings. We just… stopped having meetings and hoped people would figure it out. They didn’t.

Here’s what I’ve learned from design systems work—which is inherently async because designers and engineers are rarely in the same room:

Replace Meeting Rituals with Async Rituals

Don’t just cancel the standup. Replace it with a structured async update format.

We use a Slack channel called #daily-progress with a template:

Takes 2 minutes to write. Everyone reads it when convenient. No 15-minute meeting where 14 people listen to 1 person talk.

Crucially: the template is the same every day. No thinking required. Just fill it out.

Decision Templates

We killed our weekly “design review” meeting and replaced it with a structured Notion doc:

Design Proposal Template:

  • Problem statement
  • Proposed solution (with Figma link)
  • Alternatives considered
  • Trade-offs
  • Open questions

Post it. @mention reviewers. Set a deadline for feedback (usually 48 hours). Reviewers comment async.

If there’s consensus, ship it. If there’s conflict, then we have a synchronous meeting—but only with the specific people who disagreed, not the whole team.

Result: 80% of design decisions happen async. Only the truly contentious 20% need a meeting.

The Time Zone Forcing Function

One thing that helped us: we hired a designer in Berlin. Suddenly, “let’s just hop on a call” wasn’t possible—she was 9 hours ahead.

That forced us to write things down. No shortcuts. No “I’ll just explain it in the meeting.”

Paradoxically, having someone completely out of time-zone sync improved our async discipline for everyone.

What You Said About Incentives

You’re 100% right. If decisions happen in meetings, people will attend meetings. If promotion panels care about “executive presence” and “commanding the room,” people will optimize for meeting performance.

At my current company, our director explicitly praises written proposals in team meetings. “Great Notion doc, really clear thinking” gets public recognition. Slowly, that’s shifting what people optimize for.

But it’s slow. Culture change is painfully slow.

The shift you’re looking for isn’t a light switch. It’s replacing synchronous structures with async structures. Templates, rituals, artifacts that serve the same function meetings used to serve, but better.

3

Luis, you identified the root cause: “I didn’t change any of the underlying systems. I just asked people to behave differently while all the incentives and defaults stayed the same.”

That’s exactly it. Async-first isn’t a communication preference. It’s an organizational design choice that requires changing how work flows through your company.

Start With Incentives

When I became CTO, I asked our Head of People to audit performance reviews for the previous year. Question: “What behaviors actually get rewarded?”

Turns out: people who “showed up” in meetings, who “drove alignment” in cross-functional syncs, who were “visible leaders” in group settings. All synchronous behaviors.

Meanwhile, the engineer who wrote the best technical spec I’d ever seen—preventing 3 months of wasted work—got neutral feedback because they were “quiet in meetings.”

We changed the competency framework:

  • “Clear written communication” is now a promotable skill
  • “Enables async decision-making” is a senior+ expectation
  • “Reduces meeting load through documentation” is explicitly valued

Sounds simple. But when promotion packets started getting rejected for “insufficient evidence of async communication,” people paid attention.

Kill Meetings Structurally

You can’t just ask people to stop scheduling meetings. You have to make meetings expensive and async cheap.

We implemented:

  • No meetings before 10 AM or after 3 PM (protects focus time across time zones)
  • All meetings require written agenda 24hrs in advance, or auto-cancelled
  • “No agenda = no meeting” bot in Slack that cancels invites
  • Meeting cost calculator shows estimated salary cost ($1,200 for 10-person 1-hour meeting)

First month, people hated it. “This is bureaucratic nonsense!”

Second month, meeting volume dropped 40%. Turns out when you have to write an agenda, you realize half your meetings don’t need to happen.

Make Async Decisions Binding

Here’s the subtle culture thing: for async to work, async decisions have to be treated as equally valid as synchronous decisions.

We had this problem where people would write proposals, get async approval, then someone would say “wait, I didn’t see that doc” and reopen the decision in a meeting.

New rule: if you didn’t comment during the async decision window, you don’t get to veto later. Decisions stand unless there’s new information.

Controversial? Yes. Necessary? Absolutely. Otherwise async becomes “fake decisions” and meetings become “real decisions.”

Model It Relentlessly

Maya’s right about recognition. But it goes beyond that.

I explicitly narrate my own async behavior:

  • “I’m writing this up instead of scheduling a meeting”
  • “Great question, I’ll respond in the doc so others can see my thinking”
  • “This doesn’t need my input right now—tagging @person with context”

When the CTO does it, it gives everyone permission.

The Hard Question

You asked what GitLab/Zapier are doing differently. Honest answer: they were born async. They never had the muscle memory of “just schedule a meeting.”

You’re doing something harder: culture change in an established org. That takes 12-18 months minimum. Not weeks.

But it’s worth it. We’re now 120 engineers across 8 time zones. If we were still meeting-dependent, we’d be paralyzed.

4

Coming from product side, I want to add: the way you structure work determines whether async is even possible.

Some work is inherently synchronous. Brainstorming a new product direction? Probably needs a room (or Zoom). Resolving a critical production incident? Real-time coordination required.

But most work isn’t like that. The problem is we treat everything like it’s urgent and collaborative when it’s actually routine and independent.

Status Updates Don’t Need Meetings

We killed our weekly product/eng sync meeting. It was 90 minutes every Monday with 12 people. Estimated cost: ~$2,400/week just in salary time.

What did we replace it with?

Friday async updates in Linear:

  • Each PM posts their update by EOD Friday
  • Engineering leads comment by Monday morning
  • If there’s a blocker, we escalate to a specific sync meeting with only the relevant people

Result: information flows better, faster, and doesn’t require coordinating 12 calendars.

The key insight: status updates are broadcast communication, not discussion. Broadcasting doesn’t need synchronous time.

Async Needs Clear Ownership

Where async breaks down: when it’s unclear who makes the decision.

We had this problem with feature prioritization. PM would write a proposal. Engineering would comment. Design would comment. Weeks would pass with no resolution because nobody knew who owned the call.

Now every proposal has a DRI (Directly Responsible Individual). Comments and input are welcome, but the DRI makes the final decision and documents it.

If someone disagrees with the DRI’s decision, they can escalate to a VP. But the default is: DRI decides, team executes. Clear ownership enables async.

Async Reduces Meeting Load, Meetings Don’t Reduce Async Load

Here’s the fundamental asymmetry: async communication reduces the need for meetings. But meetings don’t reduce the need for async—they often create more async work (action items, follow-ups, summary emails).

So the transition is bumpy. You add async rituals on top of existing meetings. For a while, it feels like double the work.

But then you start seeing: “Hey, we could skip this meeting and just comment on the doc.” And gradually, meetings fall away.

You can’t go cold turkey. You have to build the async muscle while the synchronous structures still exist, then slowly deprecate meetings as people trust the async process.

What Actually Killed Meetings For Us

Michelle mentioned meeting cost calculators. We also did something simpler: default meeting length changed from 60 minutes to 25 minutes.

Sounds trivial. But it forced people to be concise. Forced pre-reads. Forced “do we really need this?”

A 25-minute meeting can’t accommodate 10 people going around saying “here’s my update.” It only works if people read the pre-doc and come ready to discuss specific decisions.

Shorter meetings → more preparation → better async artifacts.

The inverse is also true: longer meetings → less preparation → worse async artifacts.

Start small. Make meetings shorter and more expensive (require agendas, limit attendees, track costs). Async becomes the path of least resistance.

5

Luis, everything Michelle and David said is spot on. But I want to add the manager training angle because that’s where async culture actually lives or dies.

Managers Are the Bottleneck

Your 40-person team probably has ~8 managers/leads, right? If those 8 people don’t change their behavior, the other 32 won’t either.

When I took over as VP at my current company, we were meeting-heavy. I did an audit: managers were scheduling 1:1s, team syncs, cross-team syncs, skip-levels… because that’s what they learned at their previous companies.

Nobody taught them how to manage asynchronously.

Manager Training We Implemented

I ran a 4-week async leadership workshop for all people managers. Not optional. Not a “nice to have.” Core competency training.

Week 1: Async Communication Fundamentals

  • How to write context-rich updates
  • When to use which async tools
  • Setting response time expectations with your team

Week 2: Async Decision-Making

  • How to structure decisions for async input
  • When sync is actually required vs nice-to-have
  • Running async retrospectives and planning

Week 3: Async 1:1s and Feedback

  • Written status updates before 1:1s (so the meeting is coaching, not status)
  • Async performance feedback loops
  • Building relationships without constant face time

Week 4: Modeling and Accountability

  • How to model async behavior for your team
  • Holding people accountable for async participation
  • Metrics that matter (response times, doc quality, meeting load)

After the training, we did monthly async audits. Each manager reviewed their calendar and answered:

  • Which meetings could’ve been async?
  • Which async communications required follow-up meetings (and why)?
  • Where are you still defaulting to sync when async would work?

The 1:1 Shift

This was the biggest unlock: 1:1s are not for status updates.

We changed the expectation: direct reports post a written update 24 hours before the 1:1. Manager reads it, comments async. The 1:1 itself is for coaching, career development, and complex discussions.

Result: 1:1s became way more valuable. No more “here’s what I did this week” (that’s in the doc). Instead: “here’s where I’m stuck and need your help.”

Freed up ~30% of manager time. Better quality conversations.

The Urgent vs Important Trap

Managers need training on: async doesn’t mean slow.

I see this mistake constantly. Manager thinks “this is urgent, so I need a meeting.” Not true.

Urgent + decision required = short async decision window with clear DRI.

We have a Slack channel for urgent decisions: #quick-calls. Post context, @mention decision-maker, set 2-hour deadline. Decision-maker responds async or calls meeting if truly needed.

~90% get resolved async, even the “urgent” ones.

Accountability and Metrics

David mentioned meeting cost calculators. We went further: managers have a meeting budget.

Each manager gets 10 hours/week of team meeting time (not including 1:1s). If you want more, you need VP approval and a business case.

Sounds draconian? Maybe. But it worked. Managers started getting creative about async alternatives when they hit their meeting budget.

We also track:

  • % of decisions made async vs in meetings
  • Average response time to async requests
  • Employee survey: “Do you have enough uninterrupted focus time?”

What gets measured gets managed.

Timeline Reality Check

Michelle said 12-18 months. In my experience, that’s optimistic.

Culture change takes time. Expect 6 months before you see meaningful behavior change. 12 months before it feels natural. 18-24 months before it’s truly embedded in how you work.

You’re not going to flip a switch. You’re going to chip away at synchronous defaults, one ritual at a time, while training managers to operate differently.

But it’s worth it. Our eng team is now 80+ people across 5 time zones. If we hadn’t made this shift, we’d be drowning in coordination overhead.