View on GitHub

Cross-Disciplinary Software Team Spaces

A Pattern Language

Asynchronous Collaboration Norms

Summary

Create writing-first workflows and meeting rules for distributed teams to work well together across time zones and schedules.

Context

Hybrid and distributed teams need to work together well despite being in different places and time zones. This requires new approaches to communication and coordination.

Problem

When teams require everyone to work at the same time, it creates bottlenecks for distributed teams and leaves out team members who can’t join real-time meetings.

Solution

Create clear rules for working together without being online at the same time. Include communication templates, response time expectations, and the right tool choices for different types of interactions.

Communication Templates

Note: These templates are starting points - adapt them to your team size and culture. Smaller teams may need simpler formats, while larger organizations might add more structure.

Decision Request Template:

## Decision Needed: [Brief Title]

**Context**: [Background and current situation]
**Options**: 
1. Option A: [Description, pros, cons]
2. Option B: [Description, pros, cons]
3. Option C: [Description, pros, cons]

**Decision Criteria**: [What factors matter most]
**Timeline**: [When decision needed by]
**Impact**: [Who/what is affected]
**Recommendation**: [Your suggested approach]

**Response needed by**: [Date/time]
**Decision maker(s)**: [@mention specific people]

Status Update Template:

## Weekly Update: [Team/Project Name] - [Date]

**Completed This Week**:
- [Specific accomplishment with link/context]
- [Specific accomplishment with link/context]

**In Progress**:
- [Current work item] - [expected completion]
- [Current work item] - [expected completion]

**Coming Up Next Week**:
- [Planned work item]
- [Planned work item]

**Blockers/Help Needed**:
- [Specific blocker] - [@mention who can help]
- [Specific need] - [@mention who can help]

**Team Dependencies**:
- [What you're waiting for from others]
- [What others are waiting for from you]

Problem/Incident Report Template:

## Issue: [Brief Description]

**Impact**: [Who/what is affected and how severely]
**Timeline**: [When did this start]
**Current Status**: [What's happening now]

**Investigation So Far**:
- [What we've checked]
- [What we've ruled out]
- [Current theories]

**Next Steps**:
- [ ] [Specific action] - [@owner] - [by when]
- [ ] [Specific action] - [@owner] - [by when]

**Communication Plan**:
- Updates every [frequency] until resolved
- Stakeholders to notify: [@mentions]

RFC (Request for Comments) Template:

## RFC: [Proposal Title]

**Summary**: [One paragraph overview]
**Status**: [Draft/Under Review/Accepted/Rejected]

**Problem Statement**:
[What problem are we solving? Why now?]

**Proposed Solution**:
[Detailed description of the approach]

**Alternatives Considered**:
1. [Alternative A] - [Why not chosen]
2. [Alternative B] - [Why not chosen]

**Implementation Plan**:
- Phase 1: [Description and timeline]
- Phase 2: [Description and timeline]
- Phase 3: [Description and timeline]

**Success Metrics**:
[How we'll know if this is working]

**Review Timeline**:
- Comments by: [Date]
- Decision by: [Date]
- Implementation starts: [Date]

**Reviewers**: [@mention required reviewers]

Meeting Summary Template:

## Meeting: [Topic] - [Date]

**Attendees**: [List participants]
**Absent**: [Note who couldn't attend]

**Decisions Made**:
1. [Decision] - [Rationale]
2. [Decision] - [Rationale]

**Action Items**:
- [ ] [Action item] - [@owner] - [due date]
- [ ] [Action item] - [@owner] - [due date]

**Discussion Points**:
- [Key topic discussed and outcome]
- [Key topic discussed and outcome]

**For Async Review**:
[Questions or decisions that need input from absent members]

**Next Meeting**: [Date and focus]

Response Time Expectations

Urgent Communications (Production issues, blockers):

Important Communications (Decisions, deadlines, reviews):

Normal Communications (Updates, questions, discussions):

FYI Communications (Status updates, announcements):

Time Zone Considerations:

Communication Ownership:

Tool Selection Criteria

Long-form Documentation (RFCs, specs, decisions):

Real-time Discussion (Quick questions, brainstorming):

Project Management (Tasks, deadlines, priorities):

Code Review and Technical Discussion:

Visual Collaboration (Diagrams, wireframes, planning):

Knowledge Sharing (How-tos, onboarding, FAQs):

Selection Framework:

  1. Identify the need: What type of communication/collaboration?
  2. Consider audience: Team size, technical comfort, time zones
  3. Evaluate features: Does it support async workflows?
  4. Check integration: Does it work with existing tools?
  5. Test with team: Run pilot before full adoption
  6. Measure success: Are people using it? Is it working?

Tool Consolidation Principles:

Forces

Implementation Examples

Engineering Team (15 people, 3 time zones):

Product Team (8 people, 2 time zones):

Customer Success Team (12 people, 4 time zones):

Common Challenges & Solutions

Challenge: Information overload from too many async messages

Challenge: Decisions taking too long with async-only approach

Challenge: Team feeling disconnected without face-to-face interaction

Challenge: Time zone equity - some people always accommodating others

Challenge: Context loss in async communication

Challenge: Transitioning from sync-heavy to async-first culture

Challenge: Some team members struggle with async communication

Sources