Async Instead

Async Instead Skill

"This meeting could have been an email" is true more often than the email would have worked — because async fails without structure: the doc nobody read, the thread that discussed forever and decided never. A working conversion replaces the meeting's functions, not just its slot: information transfer becomes a doc with a read-by date; discussion becomes a bounded comment window; decision becomes an explicit closure step with a named decider and a deadline — the part async most often fumbles and the part this skill enforces. And some things genuinely need rooms; the honest list is part of the design.

What This Skill Produces

• The conversion design — the meeting's functions mapped to async mechanisms, with owners and deadlines
• The artifact format — the update-doc or decision-doc template that carries the load
• The closure protocol — how the async thread ends: the decider, the deadline, the decision recorded
• The still-sync list — what this meeting does that async can't, and the smaller room that remains

Required Inputs

Ask for these if not provided:

• The meeting being converted — its functions in honest proportion (how much status vs. discussion vs. decision vs. the social glue)
• The team's async maturity — do docs get read here? Are comment deadlines respected? Conversion designs differ for teams with and without the muscle (and building the muscle starts smaller)
• The tools — where docs live, where comments happen, where decisions get recorded; the design uses the real stack
• The failure history — if async was tried and died, the autopsy (nobody read? never decided? discussion sprawled?) — the design patches the specific failure

Framework: The Conversion Rules

1. Map functions, not the slot: status → the written update (structured, skimmable, due Wednesday); discussion → the comment window (open Thursday–Friday); decision → the closure step (decider decides Monday, recorded). A meeting is usually three functions braided; async unbraids them, and each gets its own deadline.
2. The doc has a format and a due-date: free-form updates sprawl; the template (template-designer rules: prompting placeholders, lighter than the meeting) plus a hard read-by/comment-by window is what separates async-that-works from a shared doc with hopes.
3. Closure is explicit or async fails: every async decision names its decider and its deadline up front — "comments until Friday; [name] decides Monday; silence is assent" — because threads without closure rules discuss until the decision gets made in a hallway anyway, discrediting the whole conversion. Decisions land in the decision log, not just the thread.
4. Silence must mean something, declared: assent, abstention, or blocking-requires-speaking — chosen per decision's stakes and stated in the doc. Undeclared silence is why async decisions get relitigated by people who "never agreed."
5. The still-sync list is honest: genuine debate with high disagreement, sensitive feedback, creative jamming, relationship glue, and true emergencies — these keep a room, usually a smaller and shorter one than the meeting being converted ("the weekly hour becomes: async status + a 20-minute discussion slot that only fires when the comment window surfaced real conflict"). Conversions that pretend everything asyncs get reversed within a quarter.