Async-first: how effective companies redesign the way work happens

In a world where time is scarce and distributed work is normal, an async-first operating model is gaining attention. It is more than a fashionable term: it changes how a company records context, makes decisions and protects focused work.

What is async-first?

Async-first means that communication and task progress do not require all participants to be online at the same moment. A report can be written, a decision prepared and a question answered at a suitable time. This is especially valuable when colleagues work in several time zones: New York, Tokyo and Berlin should not have to compete over who wakes earliest for every ordinary discussion.

Async-first is not a prohibition on calls and meetings. It changes the default. Synchronous time is reserved for dialogue that benefits from immediate exchange—conflict, rapid discovery, sensitive feedback or a genuinely urgent decision. Routine status, background and review move to durable written or recorded formats.

What makes the model distinctive

The model is not simply “work whenever you like.” It is a philosophy of autonomy supported by explicit rules. Traditional organisations fill the calendar with meetings and interruptions. Async-first creates protected focus, makes ownership visible and asks a message to carry enough context for another person to act without reconstructing the whole history.

Growth and reported figures

The original article cites a “Remote Work Trends 2023” study reporting hundreds of async-first companies across dozens of countries and industries. It also cites survey percentages for fewer meetings and higher productivity. These figures depend on definitions and samples and should be checked in the named source before being used as a business case. What can be observed directly is that the model is used not only by software startups but also by consulting, education and other distributed organisations.

Why companies adopt async-first

Global teams

When colleagues are spread across continents, continuous synchronous work becomes impractical. One person can leave a structured message at the end of their day and another can respond when their workday begins. A published response window removes the anxiety of “why did you not answer immediately?”

More time for real work

The article refers to Harvard Business Review material on the large amount of time employees can spend in meetings. Replacing unnecessary status meetings with written updates reduces context switching and returns blocks of time to analysis, creation and delivery. Everybody recognises the meeting that could have been an email; the important step is to design a better email.

Work–life balance

Flexible progress helps parents, students, carers and people combining several responsibilities. Somebody may work in the morning, take a child to school and complete another block later without failing an arbitrary 9 a.m. stand-up. This flexibility requires boundaries: async-first should not become “work at every hour.”

Advantages and disadvantages

Advantages

• Flexibility: people can arrange focused work around time zones and personal constraints.
• Fewer meetings: less calendar fragmentation leaves more time for tasks.
• Global reach: geography no longer limits the talent pool or customer team.
• Documentation: discussion and decisions are recorded, simplifying onboarding and ending “did we ever agree this?”
• Deliberation: participants can read evidence and produce a considered response instead of improvising in the room.

Disadvantages

• Isolation: a person can miss informal contact and feel detached from colleagues.
• Communication delay: waiting a day for a dependency can stop the next task.
• Need for discipline: weak self-organisation becomes visible when external supervision decreases.
• Culture risk: belonging can weaken without deliberate human contact.
• Measurement difficulty: without outcomes and agreed metrics, activity in digital tools can be mistaken for performance.

How to reduce the disadvantages

Isolation

• hold optional informal video coffee sessions and periodic in-person meetings where possible;
• use virtual offices or video tools such as Gather Town, VK WorkSpace, TrueConf, Link Meetings, SberJazz, DION, VideoMost or Kontur.Talk when they add value;
• create channels for social conversation instead of forcing it into task threads.

Delays

• set response expectations, such as an answer within one working day;
• define urgency levels and the narrow conditions that justify a synchronous escalation;
• use task systems and reminders so a dependency has an owner and a due time.

Discipline and self-organisation

• teach time-management approaches such as Pomodoro or GTD without imposing one technique on everyone;
• use regular concise progress updates;
• measure completed outcomes, not green presence indicators.

Corporate culture

• create recurring team events, including virtual formats;
• reward open, respectful and transparent communication;
• connect distributed work to a mission and values that are demonstrated in decisions.

Effectiveness

• track task outcomes and employee satisfaction;
• run engagement surveys and discuss the results;
• analyse cycle time, blocked work, rework and the speed of customer response.

Comparison with sync-first work

The numeric table in the original article gives illustrative weekly hours and ratings. A company should establish its own baseline rather than assume those values will transfer.

Additional measures

• Task cycle time: elapsed time from a ready task to completion.
• Employee engagement: survey results combined with qualitative interviews—not message count alone.
• Communication quality: rework or errors caused by missing and misunderstood context.
• Customer satisfaction: speed and quality of customer outcomes.
• Retention: whether people stay longer and why.
• Focus: amount of uninterrupted time and meeting load.

The article supplies example improvements of 10–20 percent and survey results such as 85 percent engagement. Treat these as hypotheses from cited reports, not guaranteed targets.

Overcoming resistance to change

• Explain the benefit. Show how the model improves the actual day and use public examples such as GitLab and Basecamp.
• Introduce it gradually. Replace one recurring status meeting with a written update and observe the effect before widening the change.
• Train and support. Teach the selected tools and offer help with written communication, time management and self-organisation.
• Collect feedback. Ask employees what is becoming clearer or harder and change the process from evidence.
• Motivate responsible autonomy. Recognise dependable delivery and good documentation; avoid bonuses that reward superficial activity.
• Build trust. Emphasise that async-first is not hidden surveillance. Results, commitments and mutual reliability matter more than attendance at every meeting.

Public examples

• GitLab is a well-known all-remote company with an open handbook that documents many asynchronous practices.
• Basecamp promotes written communication and uses its own project-management product to reduce meetings.
• Doist has published detailed material on asynchronous work.
• Zapier is a distributed company that shares its working practices publicly.
• Buffer, Automattic, Remote, Toptal and GitScrum are additional examples named by the original article.

The article also cites Buffer, Owl Labs and Harvard Business Review for remote-work preference, productivity, stress and deep-work statistics. Verify the year, sample and wording in each original report before quoting the percentage.

Tools for async-first

• Communication: Slack, Mattermost, Dialog, Twist, Telegram and VK WorkSpace.
• Task management and documentation: Notion, Trello, Asana, Yandex Tracker, Bitrix24, Pyrus, YouGile, Kaiten, Planfix, Weeek and Megaplan.
• Virtual contact: Gather Town, Zoom, TrueConf, DION, SberJazz and Link Meetings.
• Learning and webinars: VKurse, Pruffme and DION.

A tool does not create asynchronous culture. The organisation still needs a system of record, named owners, templates, response rules and a clear way to escalate urgent work.

Recommendations for leaders

• reduce unnecessary meetings and replace them with concise asynchronous reports;
• teach the team to use the chosen communication, task and documentation tools;
• publish response expectations—for example, within one working day;
• explain the benefit and recognise independent, dependable delivery;
• avoid overwhelming people with messages;
• collect feedback regularly;
• measure productivity, stress and satisfaction without intrusive surveillance.

Likely development of the model

The original article forecasts continued adoption, wider use in Europe and Asia, more hybrid models and new tools. The precise growth percentages are forecasts, but hybrid work is already the practical direction for many organisations: asynchronous defaults combined with selected synchronous events.

Combining async-first with Scrum

Async-first can be combined with Scrum to support distributed teams without abandoning sprint structure. The benefit is fewer context switches, more complete documentation and a predictable rhythm. Success still requires a communication culture, suitable tools and clear processes.

Core principles

• retain the useful structure of Scrum while making routine processes asynchronous;
• prefer written context to meetings that add no dialogue value;
• use a durable documentation system.

Product backlog

• update the backlog asynchronously instead of waiting for a room;
• document requirements and acceptance criteria clearly;
• use comments and voting as input to prioritisation while leaving final accountability with the Product Owner.

Sprints and roles

• plan through a document containing the sprint goal, scope and task estimates;
• publish short daily status updates;
• demonstrate results through a recorded presentation where appropriate;
• the Product Owner maintains priorities and answers questions;
• the Scrum Master moderates the process and removes blockers through clear instructions;
• the team organises execution and collaborates without waiting for constant supervision.

Replacing Scrum events responsibly

Daily Scrum: each person writes what was completed, what is planned and what is blocked by an agreed time; colleagues comment where coordination is needed.

Sprint Planning: the Product Owner prepares the goal in advance, the team reviews and asks questions, an analyst improves unclear requirements and the final plan is recorded.

Sprint Review: the team records a demonstration and written result; stakeholders comment and the Product Owner updates priorities. Use a live session when immediate discussion with stakeholders materially improves feedback.

Retrospective: participants submit observations beforehand, group proposals, vote on priority improvements and publish an action with an owner. Sensitive team issues may still require a private live conversation.

Necessary tools and rules

• a task system such as Jira or Trello;
• a communication tool such as Slack or Microsoft Teams;
• a documentation space such as Notion or Confluence;
• a recording tool such as Loom or ScreenToGif, or suitable local alternatives;
• clear response deadlines and standard templates;
• regular information updates and documented decisions.

Example weekly cycle

• Monday: asynchronous sprint planning, task ownership and documentation.
• Tuesday–Thursday: written updates, focused delivery and asynchronous discussion.
• Friday: demonstration preparation, written progress report, review and next-week preparation.

Success measures and cautions

• task cycle time and achievement of the sprint goal;
• quality and discoverability of documentation;
• team satisfaction and sustainable workload;
• reduction of meeting time without increased rework;
• time to adapt, a clear goal and an active written culture;
• regular feedback and willingness to restore a live event when it is genuinely better.

This is an adaptation of Scrum, not a claim that every event should be deleted. It keeps the useful parts of both approaches and is particularly relevant to distributed teams.

Sources named in the original article

• Remote Work Trends 2023 Report;
• Gartner research on asynchronous work models;
• Forrester material on remote-work solutions;
• annual reports and public handbooks from GitLab, Buffer and Automattic;
• State of Async Work 2023 Survey.

Conclusion

Async-first is useful when it creates autonomy, durable context and protected focus. Begin with one recurring meeting, replace it with a well-designed written process and measure the result. Keep human contact, escalation and synchronous dialogue where they matter. The standard is not silence; it is work that can progress without demanding that everybody be present at once.