Work methodology prioritizing asynchronous communication over real-time meetings. Optimizes for deep work and global collaboration by defaulting to written, time-shifted communication.
Async-First Time Management is a work methodology that defaults to asynchronous communication (written messages, recorded videos, documents) over synchronous communication (meetings, calls, instant messaging). This approach optimizes for deep work, accommodates different schedules, and reduces time fragmentation.
Core Principles
1. Default to Async
Written communication is default
Meetings are the exception, not the rule
Real-time chat is for urgent matters only
Documentation over conversation
2. Response Time Expectations
24-48 hours is reasonable
Urgent matters have clear escalation paths
No expectation of immediate response
Quality response over quick response
3. Over-Communication
Write more detail than feels necessary
Provide context
Share thinking process
Document decisions
4. Written by Default
Proposals in documents
Updates in shared spaces
Decisions recorded publicly
Meetings followed by written summaries
Benefits
For Individuals
Deep work: Fewer interruptions
Flexible schedule: Work during peak hours
Thoughtful responses: Time to think before responding
Reduced meeting fatigue: Fewer video calls
Work-life balance: No constant availability pressure
For Teams
Global collaboration: No timezone conflicts
Inclusive: Introverts, non-native speakers get equal voice
Documented: Everything written creates knowledge base
Scalable: Info accessible to all, not just meeting attendees
Productive: More making, less meeting
For Organizations
Lower costs: Less meeting time
Better retention: Flexible work attracts talent
Knowledge preservation: Documented decisions
Onboarding: New hires can read history
Distributed teams: Work across timezones
Implementation
Communication Tools
Async Tools:
Documentation: Notion, Confluence, Google Docs
Long-form updates: Email, newsletters
Project management: Asana, Linear, Height
Video messages: Loom, Vidyard
Code collaboration: GitHub, GitLab
Sync Tools (Use Sparingly):
Video calls: Zoom, Google Meet
Real-time chat: Slack, Teams (with boundaries)
Phone calls: For complex or sensitive matters
Meeting Criteria
Only meet when:
Brainstorming: Real-time ideation benefits from synchronous
Complex discussion: Too nuanced for writing
Relationship building: Team bonding, 1-on-1s
Sensitive topics: Conflict resolution, feedback
Decision urgency: Can't wait 24 hours
If it doesn't meet these criteria, use async.
Writing Practices
Structure:
Lead with bottom line
Provide context
Show your thinking
Be explicit about what you need
Set clear deadlines
Example:
TL;DR: Proposing we delay feature X by 2 weeks to focus on stability.
Context: We have 23 open bugs, customer complaints increasing.
Analysis: [detailed reasoning]
Proposal: [specific recommendation]
Decision needed by: Friday EOD
Next steps if approved: [action items]
Team Norms
Response times:
Urgent: Tag as urgent, expect 4 hours
Normal: 24-48 hours
No response expected: Mark FYI
Status updates:
Weekly written updates
Dashboard for real-time status
No status meetings
Decision making:
Write proposal
Collect async feedback
Synthesize
Decide
Document
Challenges and Solutions
Challenge: Feels slow
Solution:
Most things aren't truly urgent
Async enables better decisions
Less time in meetings = more execution time
Challenge: Miss spontaneous collaboration
Solution:
Schedule optional coworking sessions
Virtual office hours
Annual/quarterly in-person gatherings
Challenge: Hard to build relationships
Solution:
Regular 1-on-1s (these should be meetings)
Team social events
Video intros for written updates
Virtual coffee chats
Challenge: Requires strong writing
Solution:
Provide templates
Training on clear writing
Accept that it's a learned skill
Value clarity over perfection
Best Practices
Overcommunicate: Write 2x more context than feels needed
Be specific: Clear action items, deadlines, decision-makers
Visual: Use screenshots, diagrams, videos
Searchable: Use consistent tagging, formatting
Public by default: Share broadly unless sensitive
Meeting notes: Always document if you must meet
Video option: Record video message for complex topics
Respect boundaries: No expectation of immediate response
Measuring Success
Metrics:
Meeting hours per week (aim for 20% reduction)
Deep work blocks per week (aim for increase)
Employee satisfaction with schedule flexibility
Documentation coverage (% of decisions documented)
Response quality (not just speed)
Exceptions
Some situations benefit from synchronous:
Crisis management
Complex creative collaboration
Relationship repair
Quick brainstorming (if truly faster)
Final decision after async discussion
The key: Be intentional about when to break from async.
