Async work communication

{{whyLabel}}: You cannot fix a system without knowing where the time leaks are.

{{howLabel}}:

• Review all calendar invites from the past two weeks.
• Categorize each meeting as 'Status Update', 'Decision Making', or 'Social/Brainstorming'.
• Mark any 'Status Update' meeting as a prime candidate for immediate async replacement.

{{doneWhenLabel}}: [A list of all recurring meetings categorized by their primary function is complete.]

{{whyLabel}}: Understanding current 'implicit' expectations prevents friction when introducing 'explicit' rules.

{{howLabel}}:

• Survey the team on how quickly they feel they must respond to chat messages vs. emails.
• Identify 'ping-pong' patterns where simple questions take 10+ messages to resolve.
• Document the average 'interruption frequency' for a typical team member.

{{doneWhenLabel}}: [A baseline report of current response expectations and interruption levels is documented.]

{{whyLabel}}: A shared philosophy ensures everyone is aligned on why 'slow' communication is actually 'better' work.

{{howLabel}}:

• Adopt the principle: 'Documentation over tribal knowledge'.
• Define 'Default to Public': All project-related talk happens in public channels, not DMs.
• Include the 'Push vs. Pull' model: Push information into docs so others can pull it when they are ready.

{{doneWhenLabel}}: [A 1-page manifesto is written and ready for team review.]

{{whyLabel}}: Anxiety in remote work often stems from not knowing when a reply is 'late'.

{{howLabel}}:

• Tier 1 (Urgent/Emergency): Phone call or specific 'Urgent' tag (Response: <15 mins).
• Tier 2 (Standard Chat): Non-urgent queries (Response: 4-8 hours).
• Tier 3 (Email/Docs): Deep feedback or updates (Response: 24 hours).

{{doneWhenLabel}}: [A clear table of response times per channel is published in the team hub.]

{{whyLabel}}: Async fails when messages require immediate follow-up questions for clarity.

{{howLabel}}:

• Mandate that every request includes: 1. The Goal, 2. The Deadline, 3. Necessary Links, 4. What has already been tried.
• Use the 'Ask so there are no follow-up questions' rule (inspired by GitLab best practices).

{{doneWhenLabel}}: [A message template is created and shared with the team.]

{{whyLabel}}: Async work requires a 'Single Source of Truth' where all decisions are searchable.

{{howLabel}}:

• Use a wiki-style tool (Notion, Confluence, or open-source BookStack).
• Create a 'Decisions Log' to record the 'Why' behind every major project pivot.
• Organize folders by project, not by department, to increase cross-functional visibility.

{{doneWhenLabel}}: [The hub is live with at least 3 active project pages and the Manifesto.]

{{whyLabel}}: Constant pings destroy the 'Deep Work' that async communication is meant to protect.

{{howLabel}}:

• Instruct the team to disable all desktop and mobile push notifications for chat tools.
• Set 'Do Not Disturb' schedules for deep work blocks (e.g., 9 AM - 12 PM).
• Use 'Status' icons to signal current focus (e.g., 🎧 for Deep Work, 🗓️ in a meeting).

{{doneWhenLabel}}: [Every team member has confirmed their notification settings are optimized for focus.]

{{whyLabel}}: Some things are too complex for text but don't deserve a 30-minute live meeting.

{{howLabel}}:

• Deploy a screen-recording tool (Loom or the open-source Screenity).
• Set a rule: If an update takes more than 3 paragraphs to write, record a 2-minute video instead.
• Ensure all videos are shared with a written summary of key action items.

{{doneWhenLabel}}: [The tool is installed and the first 'Video Update' is shared in a public channel.]

{{whyLabel}}: Theoretical systems need real-world stress testing before full adoption.

{{howLabel}}:

• Cancel all 'Status Update' meetings for two weeks.
• Replace them with a daily 'Async Standup' thread in your chat tool.
• Appoint an 'Async Shepherd' (a team member) to call out when someone defaults back to unnecessary sync calls.

{{doneWhenLabel}}: [The 14-day period is completed without reverting to old meeting habits.]

{{whyLabel}}: You need data to prove that async work doesn't slow down delivery.

{{howLabel}}:

• Compare the planned completion dates vs. actual completion dates during the pilot.
• Analyze if 'blockers' were resolved faster or slower than during the sync-heavy period.
• Use your project management tool's analytics to track task throughput.

{{doneWhenLabel}}: [A data report comparing pilot performance to the baseline is ready.]

{{whyLabel}}: Qualitative data on team well-being is as important as quantitative productivity data.

{{howLabel}}:

• Ask: 'Do you feel more or less productive?', 'Is your stress level lower?', 'Where did the system fail?'.
• Use anonymous responses to encourage honesty regarding 'isolation' or 'information overload'.

{{doneWhenLabel}}: [Survey results are analyzed and shared with the team.]

{{whyLabel}}: Continuous improvement turns a 'test' into a 'culture'.

{{howLabel}}:

• Update the Manifesto based on pilot feedback (e.g., adjusting SLAs if 24h was too slow).
• Schedule a monthly 'Sync Social' to prevent the isolation that can come with pure async work.
• Finalize the 'Onboarding Guide' for new hires so they learn the async way from day one.

{{doneWhenLabel}}: [The updated Communication Manifesto is signed/acknowledged by the whole team.]