Async Culture

When to Meet vs Write: The Async-First Decision Tree

April 2026 · 6 min read · By

The question of whether to book a meeting or send a message is one of the most consequential micro-decisions in knowledge work. Most teams default to meetings; async-first teams default to writing.

The concrete practice

Meet or write — the decision works best when it's codified — not as a vague preference but as a team-level norm backed by scheduling-tool configuration. A booking link that enforces your working hours, your no-meeting blocks, and your required buffer time is far more durable than a personal habit.

How Cal Clear supports this

Cal Clear's per-link working hours let you configure different availability for different meeting types. Buffer time settings enforce prep windows between meetings. Required booking-form fields like 'meeting agenda' push meeting-requesters to prepare before the call. All of this is available on the free tier.

Getting started this week

Open Cal Clear settings → Working Hours. Remove any time block you want to protect for deep work. Set buffer time to at least 10 minutes between bookings. Add a required 'agenda' field to your booking form. Deploy the new link and replace the old one on LinkedIn, your email signature, and your website.

Frequently Asked Questions

Does this work with Google Calendar's default behavior?

Yes — Cal Clear layers on top of your Google Calendar without changing Google's side. Your calendar itself behaves normally; the booking link is the new enforcement mechanism.

How do I transition my team to async-first?

Start with one recurring meeting — typically daily standups — and experiment with a one-month async replacement (written standups in Slack, Loom recordings, or a shared doc). If the team survives without the daily sync, look at the weekly and biweekly meetings next.

Scheduling built for modern work

Cal Clear is free forever with unlimited multi-calendar, anti-spam, and privacy-first defaults.