Asynchronous Work: What It Means and How Small Businesses Use It
What is asynchronous work? Definition, 6 examples, async vs sync comparison, and how to implement it at a small business without an HR team.
Asynchronous Work
What it means and how small businesses use it
My company went remote at 11 employees. For the first month, we tried to replicate the office digitally: morning standups on Zoom, instant replies expected on Slack, ad hoc video calls whenever someone had a question. By week three, half the team was in meetings 3 to 4 hours per day, and the other half was waiting for someone to be available before they could make progress on their work.
The fix was not more meetings or better meeting software. It was fewer meetings and more writing. We switched to asynchronous work: written status updates instead of standups, recorded walkthroughs instead of calls, documented decisions instead of verbal agreements, and defined response windows instead of the expectation that everyone replies instantly. Within a month, meeting time dropped by 60%, and output went up because people could actually focus.
Asynchronous work does not eliminate human interaction. It means choosing the right communication mode for each situation and defaulting to the one that respects everyone's time and focus. These principles are built into how we think about onboarding at FirstHR, where self-paced task workflows, training modules, and document management let new hires complete onboarding on their own schedule.
This guide explains what asynchronous work means and how it differs from synchronous work, walks through six practical examples, weighs the benefits and challenges for small businesses, and shows how to implement it on a small and growing team, including the wage and hour and multi-state hiring rules to watch along the way.
What Is Asynchronous Work?
Asynchronous work is a collaboration model where team members do not need to be online at the same time to make progress. Instead of real-time communication (meetings, instant messages, live calls), work advances through written updates, recorded content, documented processes, and defined response windows.
The concept is not new. Email has always been asynchronous. What changed is that companies now apply the principle to nearly all communication, not just email. Status updates, process documentation, decision-making, training, and onboarding can all happen asynchronously, with synchronous meetings reserved for complex discussions, sensitive conversations, and deliberate relationship-building.
Asynchronous vs Synchronous Work
The difference is timing: synchronous work needs everyone online at once, while asynchronous work lets people contribute on their own schedule within agreed timeframes.
| Dimension | Synchronous Work | Asynchronous Work |
|---|---|---|
| Communication mode | Real-time: meetings, live calls, instant messages expecting immediate replies | Time-shifted: written updates, recorded videos, messages with defined response windows |
| Scheduling | Requires everyone available at the same time | Each person works on their own schedule within agreed timeframes |
| Decision-making | Decided live in meetings, often undocumented | Proposed in writing, discussed with comments, decided and documented |
| Information sharing | Presented live; you had to be there | Written or recorded; accessible anytime, replayable |
| Timezone compatibility | Requires timezone overlap | Works across any timezone with proper handoff practices |
| Default at most companies | Yes (meetings are the default) | Rare (requires intentional adoption) |
| Best for | Complex decisions, sensitive conversations, brainstorming, relationship-building | Status updates, information sharing, documentation, training, routine coordination |
Most small businesses default to synchronous work because it feels natural. You have a question, you ask someone. You need a decision, you call a meeting. You hire someone new, you walk them through everything in person.
That habit works while the whole team still fits around one table. As you grow, synchronous defaults start creating bottlenecks: the founder is in meetings half the day, decisions wait until everyone can get on a call, and new hires cannot make progress when their manager is unavailable.
6 Practical Examples of Asynchronous Work
Asynchronous work is not abstract. It is a set of specific practices that replace synchronous habits with written, recorded, and self-paced alternatives.
The common thread across all six examples: information is captured in a durable format (written, recorded, documented) rather than shared in a transient one (verbal, live, real-time). Durable communication creates a record. Transient communication creates a memory, and memories diverge.
Benefits of Asynchronous Work for Small Businesses
For a small business, the main benefits are fewer meetings, built-in documentation, scheduling flexibility, and less dependence on the founder.
| Benefit | How It Works | Impact at Small Scale |
|---|---|---|
| Fewer meetings, more focus time | When communication defaults to writing, recurring status meetings stop earning their slot on the calendar and people reclaim hours for deep work. | Three fewer hours of meetings per person per week adds up to more than a full day of focus time reclaimed across a small team. |
| Documentation as a byproduct | When decisions and processes happen in writing, they are automatically documented without extra effort. | New hires can read how decisions were made and how processes work instead of relying on someone explaining it. |
| Timezone and schedule flexibility | Team members contribute when they are most productive, not when the founder is available. | Enables hiring across timezones without requiring everyone to be online during East Coast business hours. |
| Reduced founder bottleneck | Information does not wait for the founder to be available. Written context enables independent progress. | The founder stops being the single point of failure for every question and decision. |
| Better onboarding | Self-paced onboarding tasks, recorded training, and documented processes let new hires ramp without waiting. | New hires complete onboarding on their schedule instead of waiting for live sessions that keep getting postponed. |
| Inclusive communication | Written communication levels the playing field for non-native speakers and introverts who contribute better in writing. | At diverse small teams, async gives everyone equal time to formulate thoughtful responses. |
Research reported in the Society for Human Resource Management's HR Magazine (2017) shows that up to 20% of all employee turnover happens within the first 45 days. Async onboarding addresses one of the root causes: onboarding that depends on the founder's availability. A self-paced process keeps the new hire moving even when the founder is busy.
Challenges of Async Work and How to Solve Them
Async work runs into six predictable problems, and each has a practical fix.
| Challenge | Why It Happens | The Fix |
|---|---|---|
| Loneliness and disconnection | Without casual office interactions, people feel isolated | Schedule weekly non-work connection time: 15-minute social call, virtual coffee, personal check-in at the start of 1-on-1s |
| Slower urgent decisions | Async response windows mean 4-hour delays on non-urgent items | Define an escalation path: phone call or @urgent tag for genuinely time-sensitive issues. Everything else follows normal response windows. |
| Writing fatigue | Communicating everything in writing is more effortful than speaking | Use recorded video for explanations that are easier to show than write. Reserve writing for decisions, updates, and documentation. |
| Context loss in text | Written messages lack tone, facial expressions, and nuance | Use video for sensitive topics. Add context to written messages: not just 'the report is wrong' but 'the Q3 numbers in row 14 do not match the source data.' |
| Over-documentation | Teams document everything including things that do not need documenting | Document decisions, processes, and onboarding. Do not document casual conversations, brainstorms, or one-time exchanges. |
| New hire confusion | New hires do not know the async norms and default to synchronous patterns | Include async norms in onboarding: which channels to use, response windows, when to schedule a meeting vs write a message. |
The last challenge (new hire confusion) is the one most companies overlook. A new hire joins a team that has been async for a year and has no idea how things work. They send urgent Slack messages expecting instant replies, schedule unnecessary meetings, and feel ignored when nobody responds within 5 minutes. The fix: include a one-page async norms document in your onboarding.
Which Roles Can Actually Work Async
The honest version of this guide has to say that async is not uniformly available across a company. The dividing line is not seniority and it is not exempt versus nonexempt. It is whether the role owns work or owns coverage. Work can be time-shifted. Coverage cannot, because coverage is a promise that someone is there during a defined window.
| Role Type | How Async Applies | What Stays Synchronous |
|---|---|---|
| Project-based individual contributors (engineering, design, writing, analysis) | Almost fully async. Work is measured in delivered output, and interruptions cost more than delays. | Design reviews, project kickoffs, anything requiring live disagreement to resolve. |
| Managers | Partially async. Status intake, approvals, and written feedback shift easily. | One-on-ones, performance conversations, conflict, and anything with emotional content. Do not deliver difficult feedback in writing to save a meeting. |
| Customer support and success | Async between the team, not with the customer. A response-time commitment to a client is coverage. | Staffed hours, escalation availability, and handoffs at the edges of shifts. |
| Sales | Internal coordination and pipeline updates go async. | Customer calls run on the customer's schedule, which is the definition of synchronous. |
| Operations, fulfillment, scheduling, and anything on-site | Async is largely unavailable for the work itself, though the coordination around it can be written. | The shift. Do not sell async flexibility to a role that has none; it reads as a benefit for other people. |
This split matters more at small scale than at large scale. In a small business you can easily end up with most of the team on flexible async schedules and two or three people covering a support queue from 9 to 5, and the second group notices.
The fix for that imbalance is not to force everyone into the same model. It is to be explicit about which roles have schedule flexibility and which have coverage obligations, and to balance the coverage burden in other ways: predictable schedules published in advance, real time off, and rotation so the same person is not always the one who has to be online.
How to Implement Asynchronous Work at a Small Business
A small business can roll out async work in about a month by following eight steps, starting with a meeting audit and written channel norms.
| Step | What to Do | Timeline |
|---|---|---|
| 1. Audit current meetings | List every recurring meeting. For each: could this be a written update instead? If yes, cancel it and replace with async. | Week 1 |
| 2. Define channel norms | Write a one-page document: which tool for which message type. Quick questions: Slack. Announcements: email. Decisions: shared doc. Urgent: phone call. | Week 1 |
| 3. Set response windows | Team norm: Slack within 4 hours, email within 24 hours, urgent issues via phone immediately. Post this in the team channel. | Week 1 |
| 4. Start with weekly written updates | Every Monday, each person posts: what they finished last week, what they are working on this week, what is blocking them. | Week 2 |
| 5. Record instead of presenting | Next time you need to explain something to the team, record a 5-minute video instead of scheduling a 30-minute call. | Week 2-3 |
| 6. Document decisions after discussions | After every meeting or significant Slack discussion, one person posts a summary: what was decided, who owns what, deadlines. | Week 2-3 |
| 7. Make onboarding async | Convert your onboarding from live orientation to self-paced tasks: documents to sign, training to complete, guides to read, check-ins at milestones. | Week 3-4 |
| 8. Review and adjust monthly | Ask the team: what is working? What is not? Adjust norms based on real feedback, not assumptions. | Ongoing |
The most important step is number 2 (channel norms) because without clear rules about which messages go where, async work creates chaos instead of clarity. If the founder keeps scheduling unnecessary meetings while telling the team to "go async," the team will not change.
Step 1 is the one that produces an argument, so do it on paper rather than in conversation. List every recurring meeting, multiply length by attendees by frequency to get the weekly cost in person-minutes, and make a decision on each row. Meetings survive on habit, and the column that ends most of them is the one asking what the meeting is actually for.
| A | B | C | D | E | F | G | H | I | J | K | L | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Meeting | Frequency | Length in minutes | People who attend | Person-minutes per week | What it is actually for | Could this be written or recorded? (Y/N) | Replacement format | Owner of the replacement | Decision (keep / shorten / replace / cancel) | Date decided | Checked again after 30 days |
| 2 | Example: daily standup | Daily | 15 | 8 | 600 | Status sharing | Y | Monday written update in the team channel | Replace | |||
| 3 | Example: weekly all-hands | Weekly | 25 | 15 | 375 | Announcements and connection | N | Keep | ||||
| 4 | ||||||||||||
| 5 | ||||||||||||
| 6 | ||||||||||||
| 7 | ||||||||||||
| 8 | ||||||||||||
| 9 | ||||||||||||
| 10 | ||||||||||||
| 11 |
Async and Wage and Hour Law
Most articles about asynchronous work are written as if everyone on the team is salaried and exempt from overtime. If you have nonexempt employees (staff entitled to overtime pay), as many small businesses do, "work whenever suits you and reply within four hours" is a wage and hour position, not just a culture choice. The rules do not change because the work moved to Slack.
The core principle is that you owe pay for all hours worked, including work you did not authorize. Under the Fair Labor Standards Act (FLSA), the regulation at 29 CFR 785.11 treats work you did not request but allowed to happen ("suffered or permitted") as work time, and if you know or have reason to know the work is happening, it counts.
A nonexempt employee who reads and answers messages at 9:30 in the evening is working. A policy telling them not to is not a defense on its own. Under 29 CFR 785.13 you are expected to enforce it, and enforcement is a management job, not a paragraph in the handbook.
Small increments are the trap here. Federal law has long tolerated genuinely insubstantial amounts of unrecorded time (29 CFR 785.47), but that exception is narrow.
The California Supreme Court has declined to apply that exception to routine off-the-clock minutes (Troester v. Starbucks Corp., 2018). Ten minutes of evening message triage, five days a week, is not a rounding error in either the math or the record.
| Async Practice | Wage and Hour Consequence | What to Do Instead |
|---|---|---|
| Four-hour response window that spans evenings and weekends | Nonexempt employees monitoring channels off-shift are working, and that time is compensable | Scope response windows to the employee's scheduled hours. Make it explicit that nonexempt staff are not expected to read messages outside them. |
| Flexible schedules with hours spread across the week | Federal overtime is calculated on the workweek, a fixed and regularly recurring 168-hour period, and hours cannot be averaged across two or more weeks | Set and document the workweek. Watch weekly totals, not daily ones, unless your state adds daily rules. |
| Async work in California and a few other states | Some states impose daily overtime on top of the weekly rule. California requires overtime past 8 hours in one day, with additional rules beyond 12 and on the seventh consecutive day; Alaska, Colorado, and Nevada have daily rules of their own | Check the rule in each state where someone actually works, not where the company is headquartered. |
| Timekeeping by memory or by calendar | The FLSA requires records of hours worked each day and each week; no particular format, but you need the record | Have nonexempt staff clock in and out for each work block, including short evening blocks. Self-reported time is acceptable if it is accurate and you act on what it shows. |
| No structured breaks because everyone sets their own day | Federal law does not mandate meal or rest breaks, but many states do, with penalties for missed periods | In break-mandate states, build the meal period into the schedule and record it. Short breaks of roughly five to twenty minutes are paid time under federal rules; bona fide meal periods where the employee is relieved of duty are not. |
State law is where a flexible schedule gets expensive. In California, a 10-hour Thursday earns two hours of premium pay even when the week ends under 40 hours, and the double-time and seventh-day rules stack on top of that (California Division of Labor Standards Enforcement). The same hours spread evenly cost less.
Recordkeeping is the other half of the problem. Under 29 CFR 516.2 you keep hours worked each day and total hours worked each workweek for every nonexempt employee. A shared calendar and a memory of who was online do not meet that standard, and an incomplete record is the employer's problem, not the employee's.
Hiring Across State Lines Once You Go Async
The reason most small companies adopt async is the reason it becomes an administrative project: once schedule overlap stops mattering, geography stops mattering, and the first out-of-state hire is rarely far behind. That hire is not a payroll setting. It is an entry into a new regulatory jurisdiction.
| What Triggers | Why | Typical Requirement |
|---|---|---|
| State income tax withholding | Withholding generally follows where the work is physically performed, not where the company sits | Register with the state revenue agency before the first payroll in that state. Some state pairs have reciprocity agreements that change which state you withhold for. |
| State unemployment insurance | Unemployment coverage is assigned to one state per employee, determined by a sequence that starts with where the work is localized | Register for a state unemployment account and pay contributions at that state's rate and wage base. |
| Workers' compensation | Coverage requirements and how they are satisfied are set state by state, and a few states require coverage through a state fund | Confirm your policy actually extends to the new state before the employee starts. |
| Paid sick leave and other mandated leave | Numerous states and cities require accrued paid sick leave, and several have paid family and medical leave programs funded by payroll contributions | Add the accrual to your policy and the contribution to payroll. These vary widely, so check the specific state and sometimes the specific city. |
| Notices, postings, and pay transparency | Several states require a written wage notice at hire and their own posted notices; several require pay ranges in job postings, and those laws can reach a remote role that could be performed in the state | Issue the state's hire notice, post electronically for remote staff, and include ranges in postings once any covered state is in scope. |
| New hire reporting and business registration | New hire reports go to the state where the employee works (an employer with staff in two or more states can register with the U.S. Department of Health and Human Services to send them all electronically to one of those states), and employing someone in a state can require registering to do business there | Report within the state's deadline and confirm whether foreign qualification applies. |
None of this makes remote hiring a bad idea. It makes the second state a decision rather than an accident. A practical approach for a small business: pick a small number of states you are willing to employ in, register properly in those, and treat any request to work from a new one as a business decision with a real setup cost rather than something a manager can approve in a Slack thread.
Employees relocating quietly is the common version of this problem, which is why the async norms document should say that a change of work state has to be reported before it happens.
Monitoring, Trust, and Notice Laws
The predictable failure mode of async management is that a manager who can no longer see people working starts looking for a proxy. Green dots in the chat tool. Response latency. Activity dashboards. Screenshots. This substitutes a metric for the thing you actually wanted, which is output, and it teaches the team that presence in the tool is what gets rewarded. People then produce presence in the tool.
What to measure instead is boring and effective: did the committed work arrive, was it the quality expected, and did the person keep others unblocked.
In an async team, all three questions can be answered from the artifacts that async produces anyway, which is one of the underrated benefits of moving communication into writing. The weekly written update, the documented decisions, the completed tasks and the review comments are a performance record. You do not need a surveillance layer on top of a system that already generates evidence.
If you do monitor, there is a legal layer worth knowing. Several states require employers to give notice of electronic monitoring.
Under New York Civil Rights Law 52-c, an employer with a place of business in New York that monitors telephone, email, or internet usage must give written or electronic notice on hiring, collect an acknowledgment, and post the notice where employees can read it. Connecticut and Delaware have their own notice or posting requirements.
Recording conversations adds a separate rule set, because consent requirements for recorded calls vary by state and some require all parties to consent, which matters if your async culture includes recording meetings for people who could not attend.
The safe default for a small distributed team is to announce recording at the start of the call, keep recordings where the participants can find them, and state in the norms document exactly what the company does and does not monitor.
Asynchronous Onboarding: Where Async Work Starts
Onboarding is the most natural entry point for asynchronous work at a small business because the alternative (synchronous onboarding) is the most fragile. When onboarding depends on the founder being available for live walkthroughs, it gets postponed every time the founder is busy. The new hire sits idle. The paperwork stalls. The training gets delayed.
| Onboarding Element | Synchronous Version | Asynchronous Version |
|---|---|---|
| Paperwork (W-4, I-9, direct deposit) | Founder walks new hire through forms in person | Self-service portal: W-4 and direct deposit forms completed and signed before day one. Form I-9 keeps its federal deadlines: Section 1 by the first day of work, document review and Section 2 within 3 business days |
| Policy acknowledgments | Founder explains policies in a meeting | Policies delivered via task workflow; new hire reads and signs electronically |
| Role training | Manager sits with new hire for a full day | Recorded training modules completed at the new hire's pace, with milestone check-ins |
| Team introduction | Live all-hands introduction | Written intro in team channel plus async welcome messages from each team member |
| First week check-in | Scheduled meeting that gets rescheduled twice | Structured check-in questions sent via task workflow at Day 7; manager responds within 24 hours |
Employees are 3.4 times as likely to describe their onboarding as successful when their manager plays an active part in it (Gallup). Asynchronous onboarding does not replace the human relationship between the new hire and their manager. It replaces the administrative dependencies that delay onboarding when the founder is busy.
Tools for Asynchronous Small Teams
Most small async teams need five kinds of tools: messaging, async video, shared documentation, project management, and an HR platform for onboarding.
| Category | What It Handles | Examples |
|---|---|---|
| Team messaging | Daily coordination, quick questions, channel-based updates | Slack, Microsoft Teams |
| Async video | Process walkthroughs, explanations, demos that are easier to show than write | Loom, Vidyard |
| Shared documentation | Processes, decisions, reference information, wikis | Notion, Google Docs, Confluence |
| Project management | Task assignment, deadlines, progress tracking, workflows | Asana, Trello, ClickUp, Monday |
| HR and onboarding | Self-paced onboarding workflows, document management, e-signatures, training modules, employee self-service | HR platforms with task workflows and self-service portals |
The tool stack matters less than the norms. Five tools with clear channel rules produce better async communication than fifteen tools with no rules. Define which tool handles which type of communication and enforce it.
Common Async Work Mistakes
Teams new to async tend to repeat the same six mistakes, and each one has a simple fix.
| Mistake | Why It Happens | The Fix |
|---|---|---|
| Going async without written norms | Assumes everyone knows how async works | Write a one-page norms doc: channels, response windows, meeting rules. Share on Day 1 of every hire. |
| Eliminating all meetings | Overcorrecting from too many meetings | Keep weekly all-hands (25 min), 1-on-1s (15-20 min), and ad hoc meetings for complex discussions. Cut everything else. |
| Expecting instant replies on async channels | Old synchronous habits persist | Enforce the response window norm. If someone needs an instant reply, they call. Everything else follows the agreed timeline. |
| Not including async norms in onboarding | Treating async as 'how we already work' that new hires will absorb | New hires default to synchronous patterns. Explicitly teach async norms in onboarding. |
| Using the wrong mode for the message | Writing a 500-word Slack message when a 3-minute video would be clearer | Match the medium to the content: writing for decisions and updates, video for explanations and demos, meetings for discussions. |
| Founder does not model async behavior | Founder sends urgent Slack messages at 10 PM expecting immediate replies | The founder sets the standard. If you want async, model it: write updates, respect response windows, cancel unnecessary meetings. |
The root cause of most async failures is not technology or process. It is that the founder does not model the behavior they want. If the founder sends messages outside business hours and expects instant replies, no written norm will change the team's behavior.
This week, run the meeting audit and cancel the first recurring meeting that could have been a written update. It is the quickest way to show the team you mean it.
Frequently Asked Questions
What does asynchronous work mean?
Asynchronous work is a way of working where colleagues do not have to be online together to get things done. People share progress through written updates, recorded videos, shared documents, and agreed response windows, then reply on their own schedule within the timeframe the team has set. The contrast is synchronous work, where everyone has to be present at the same moment for meetings, calls, or instant replies.
What is the difference between asynchronous and synchronous work?
Synchronous work requires everyone to be present at the same time: meetings, live calls, real-time chat. Asynchronous work does not: written updates, recorded walkthroughs, documented decisions. Most teams use a mix. The question is which is the default. Async-first teams default to written communication and call a meeting when a topic needs live back-and-forth. Sync-first teams default to meetings and live communication for most interactions.
What are examples of asynchronous work?
Six common examples: written status updates posted in a team channel instead of standup meetings, recorded video walkthroughs instead of live presentations, documented decisions in shared docs instead of verbal agreements, defined response windows (4 hours for messages, 24 hours for email) instead of instant-reply expectations, self-paced onboarding with task workflows instead of live orientation sessions, and timezone-friendly handoffs using written context instead of waiting for overlap.
Is asynchronous work good for small businesses?
Yes, for three reasons. First, it reduces meeting overhead: a small business does not need the same meeting cadence as an enterprise. Second, it supports remote and hybrid teams without requiring everyone in the same timezone. Third, it creates documentation as a byproduct: when communication happens in writing, decisions and processes are automatically recorded rather than lost in verbal conversations.
How do you manage an asynchronous team?
Four foundations: define channel norms (which messages go where), set response time expectations (4 hours for team chat, 24 hours for email), document all decisions in writing (not just discussed verbally), and schedule synchronous time deliberately for discussions, feedback, and relationship-building. The manager's role shifts from directing work in real time to setting clear expectations, providing context in writing, and checking outcomes rather than monitoring activity.
What tools do you need for asynchronous work?
Most small async teams need five categories of tools: team messaging with channels (Slack or Microsoft Teams), async video recording (Loom or similar), shared documentation (Notion, Google Docs, or Confluence), project management (Asana, Trello, or ClickUp), and HR and onboarding (for self-paced new hire workflows, document management, and training delivery). The tools matter less than the norms: define how each tool is used and enforce the norms consistently.
Does asynchronous work mean no meetings?
No. Asynchronous work means meetings are intentional, not default. Instead of scheduling a meeting for every discussion, you default to written communication and reserve meetings for topics that genuinely benefit from real-time interaction: complex decisions, sensitive conversations, brainstorming, and relationship-building. A well-run async team has fewer but more productive meetings because the information-sharing happens asynchronously.