Online, part-time, and executive MBA teams share one constraint full-time teams don't: there is no time slot where five working professionals across three time zones are all free and all awake. Teams that fight this with more scheduling lose. Teams that go async-first stop needing the slot.
Async-first is not async-only
Async-first means the default channel is written and non-blocking, and live time is reserved for what genuinely needs it: contested decisions, creative problem-solving, and rehearsal. A good rule from distributed companies applies directly—if it's information transfer, write it; if it's negotiation, meet.
Norm 1: Default to written
Status updates, section drafts, data questions, small decisions—all written, all in one agreed place. The test for whether something needs a meeting: does it require back-and-forth in real time, or does it just feel more comfortable live? Comfort is not a reason to cost five people an hour each.
Norm 2: Agree on response windows
Async fails when nobody knows whether silence means "haven't seen it" or "don't care." Set the numbers at kickoff:
- Input requests: within 24 hours
- Document reviews: within 48 hours
- "Urgent" tag: same day, used sparingly
The specific numbers matter less than everyone knowing them. Silence inside the window is normal; silence past it is a nudge-worthy miss.
Norm 3: Decide by propose-then-object
Waiting for a meeting to decide anything means your project moves at meeting speed. Instead: whoever owns the question writes a short proposal—context, recommendation, objection deadline. "I propose we scope the analysis to the US market. Objections by Thursday 8pm, else it's decided."
No objections means decided. One objection means a thread. A stalemate means a fifteen-minute call between the two people who disagree—not a full-team meeting.
Norm 4: Keep a decision log
Distributed teams relitigate decisions because the reasoning lived in a call half the team missed. Every propose-then-object outcome gets one line in a shared log: date, decision, why. Ten seconds to write, and it ends the "wait, when did we decide that?" spiral that eats async teams from the inside.
Norm 5: Make work visible without asking
The async killer is the check-in message: "hey, how's the model coming?"—multiplied by five people, daily. Visibility should be ambient, not requested. Keep every deliverable's status, owner, and due date somewhere everyone can see without asking; MBA Lab's project view exists for exactly this. When status is ambient, messages can be about substance.
The three meetings worth keeping
Async-first teams still meet—on purpose, not by default:
- Kickoff. Scope, roles, and the norms above. This is where async gets agreed, live.
- Midpoint working session. Bring the hardest integration problem, share screens, solve it together.
- Dry run. Presentations rehearse live, full stop.
Everything else earns its way onto a calendar only by failing in writing first.