Async Is Not the Same as Slow
The criticism of async-first work is that it creates delays: questions take hours to answer, decisions sit in inboxes, blockers go unresolved until the next overlap window. This is a failure of async process, not async itself.
Done well, async work is faster than sync-heavy work because it eliminates the coordination overhead that burns most of the available synchronous time in calendar-heavy organizations. The real cost of synchronous work isn’t the meetings themselves — it’s the fragmentation of focus time that makes deep work rare.
Write More Than You Think You Need To
The most common reason async fails is insufficient context in written communication. “Can we discuss the API design?” is not actionable async. “I’m proposing we switch the task update endpoint from PUT to PATCH for partial updates — here’s the current spec, here’s my proposed change, here’s why I think it’s worth the migration cost — feedback by Thursday?” is actionable async.
The investment in writing a clearer message pays dividends because:
- It reduces back-and-forth cycles
- It allows the responder to give higher-quality input because they understand the context
- It creates a record that new team members can read later
Decision Records Are Not Bureaucracy
Documenting decisions as they happen — in the relevant task, in a knowledge base page, or in a dedicated decision log — is sometimes dismissed as overhead. It’s the opposite. Undocumented decisions get relitigated. Someone joins the team, doesn’t know why a technical choice was made, and proposes reversing it. A month of discussion follows to re-establish a decision that took 20 minutes to make the first time.
FlowEra’s knowledge base is the right place for decision records. One page per significant decision: what was decided, why, what was ruled out, who signed off, when. Link to it from the tasks that implemented the decision.
Define “Urgent” Explicitly
In async-first teams, the biggest cultural problem is undifferentiated urgency. When everything can be “urgent”, nothing is. People check messages continuously because they can’t distinguish between “this is genuinely blocking work” and “this is a low-priority question that could wait until tomorrow.”
Define what counts as urgent for your team — a production incident, a blocked teammate, a customer-impacting decision — and agree that those get synchronous communication (call or direct message). Everything else goes through async channels.
This agreement allows people to batch their async communication rather than monitoring it continuously.
Overlap Windows for Real Coordination
Fully async works for most work. It doesn’t work for everything. Brainstorming, conflict resolution, complex technical decisions with multiple participants — these often benefit from synchronous discussion.
Define an overlap window: a 2–3 hour window each day when the whole team is available for calls. Keep it short enough that it doesn’t dominate the day, but consistent enough that everyone knows when to schedule calls.
Outside the overlap window, async is the default. Inside the overlap window, synchronous communication is available when needed.
FlowEra for Async Teams
FlowEra is designed for async-first work. Tasks are the primary communication artifact — description, comments, attachments, linked docs. Video calls are available when needed but not the default. The board is always current so anyone can get context without asking.
Notifications are conservative by default: you’re notified when something directly requires your attention, not whenever anything happens in a flow you have access to. This allows async team members to batch their reviews rather than respond to a stream of interrupts.