Remote Collaboration | Async-First Practices
Enable distributed teams to collaborate effectively with async-first workflows. GitScrum supports remote teams across timezones.
6 min read
Remote work requires intentional practices that in-office teams take for granted. Successful remote collaboration isn't about replicating the office—it's about building better systems for communication, coordination, and connection that work across distances and timezones.
Remote Collaboration Principles
| In-Office Default | Remote Intentional |
|---|---|
| Quick questions | Written requests |
| Walk-up interrupts | Async by default |
| Overhear context | Document everything |
| Lunch together | Schedule social time |
| Impromptu meetings | Structured agendas |
Async-First Communication
Communication Channels
COMMUNICATION CHANNEL GUIDE
═══════════════════════════
INSTANT MESSAGING (Slack/Teams):
├── Quick questions (not urgent)
├── Social chat
├── Time-sensitive coordination
├── Response expected: 4 hours
EMAIL:
├── External communication
├── Formal/documented decisions
├── Non-urgent announcements
├── Response expected: 24 hours
GITSCRUM TASKS:
├── Work requests and assignments
├── Status updates
├── Technical discussions about work
├── Response expected: 1 business day
GITSCRUM NOTEVAULT:
├── Documentation
├── Meeting notes
├── Decisions and ADRs
├── Permanent reference
VIDEO CALL:
├── Complex discussions
├── Relationship building
├── Sensitive topics
├── Scheduled in advance
PHONE/URGENT:
├── Production emergencies
├── Personal emergencies
├── Truly can't wait
├── Rare (define what qualifies)
Writing for Async
EFFECTIVE ASYNC COMMUNICATION
═════════════════════════════
INSTEAD OF:
"Hey, can you look at this?"
"Got a minute?"
"Quick question..."
WRITE:
─────────────────────────────────────
**Context:** Working on GS-234, login API
**Question:** Should we use JWT or session tokens?
**What I've considered:**
- JWT: Stateless, but token revocation harder
- Sessions: More traditional, need Redis
**Preference:** JWT with short expiry + refresh
**Timeline:** Need decision by EOD Thursday
**Action:** Your thoughts when you have time
─────────────────────────────────────
ELEMENTS OF GOOD ASYNC MESSAGE:
├── Context (what you're working on)
├── Complete question (not just "help")
├── What you've already tried/considered
├── Your recommendation if you have one
├── Timeline/urgency level
├── Clear ask (what do you need)
Response Expectations
RESPONSE TIME AGREEMENTS
════════════════════════
TEAM AGREEMENT TEMPLATE:
─────────────────────────────────────
CHANNEL EXPECTED RESPONSE
─────────────────────────────────────
Slack 4 hours during work hours
Email 24 hours
Task comment 1 business day
PR review 24 hours (48h max)
Urgent call Immediate (define urgent)
TIMEZONE CONSIDERATION:
If sender is 8 hours ahead:
├── Their 5pm = Your 9am
├── Send end of their day
├── Expect response next day their time
└── Plan for 1-day round trip
"URGENCY" DEFINITION:
🔴 Urgent: Production down, security incident
→ Phone/page
🟡 Today: Customer waiting, blocking others
→ Slack + tag + note urgency
🟢 Normal: Default, no special handling
→ Regular channels, regular SLA
Timezone Coordination
Overlapping Hours
TIMEZONE MANAGEMENT
═══════════════════
IDENTIFY OVERLAP:
─────────────────────────────────────
Team Member Timezone Work Hours
─────────────────────────────────────
Sarah (NYC) EST 9am-6pm EST
Mike (London) GMT 9am-6pm GMT
Alex (Tokyo) JST 9am-6pm JST
Overlap: 9am-10am EST = 2pm-3pm GMT = 11pm-12am JST
ONLY 1 HOUR OVERLAP (common challenge)
SOLUTIONS:
├── Rotate meeting times (fair distribution)
├── Record all meetings
├── Async by default, sync for overlap hours
├── Group by timezone for daily work
└── Quarterly in-person for bonding
Meeting Scheduling
REMOTE MEETING PRACTICES
════════════════════════
BEFORE SCHEDULING:
├── "Could this be async?"
├── "Who truly needs to be there?"
├── "What timezone impact?"
└── Default: Don't meet
WHEN SCHEDULING:
├── Check all attendee timezones
├── Rotate if regularly outside hours
├── Send agenda 24h in advance
├── Include dial-in for those on travel
DURING MEETING:
├── Record for absent teammates
├── Strict time-boxing
├── Document decisions live
├── Action items with owners
AFTER MEETING:
├── Share notes in GitScrum
├── Action items become tasks
├── Recording available
└── Follow up async for input
Remote Work Tools
Tool Stack
REMOTE COLLABORATION TOOLS
══════════════════════════
COMMUNICATION:
├── Slack/Teams: Real-time messaging
├── Email: External, formal
├── Video: Zoom, Google Meet
└── GitScrum: Work coordination
PROJECT MANAGEMENT:
├── GitScrum: Tasks, projects, boards
├── NoteVault: Documentation
└── GitHub: Code collaboration
DOCUMENT COLLABORATION:
├── Google Docs: Real-time editing
├── Notion: Wiki-style docs
├── Miro: Visual collaboration
└── Figma: Design collaboration
ASYNC VIDEO:
├── Loom: Screen recordings
├── Async demos
├── Complex explanations
└── Personal connection
SOCIAL:
├── Donut: Random coffee chats
├── Virtual events
├── Slack games/channels
└── Watercooler time
GitScrum for Remote
GITSCRUM REMOTE FEATURES
════════════════════════
VISIBILITY:
├── All work visible on boards
├── Status updates in tasks
├── Progress without meetings
└── Dashboard for leadership
ASYNC UPDATES:
├── Daily standup feature
├── Written async updates
├── No meeting required
└── Timezone friendly
COMMUNICATION:
├── Task comments (context preserved)
├── @mentions for attention
├── Notifications configurable
└── Slack integration
DOCUMENTATION:
├── NoteVault for decisions
├── Linked to tasks
├── Searchable
└── Permanent record
Building Remote Culture
Connection Practices
BUILDING REMOTE CULTURE
═══════════════════════
REGULAR TOUCHPOINTS:
├── Weekly team sync (video, short)
├── Monthly all-hands
├── Quarterly virtual social
└── Annual in-person gathering
1:1s ARE CRUCIAL:
├── Weekly with manager
├── Consistent schedule
├── Not just status—relationship
├── Camera on when possible
└── Check wellbeing
SOCIAL CHANNELS:
├── #random - Anything goes
├── #pets - Share pet photos
├── #wins - Celebrate achievements
├── #help - Ask anything
└── Interest-based channels
VIRTUAL EVENTS:
├── Coffee chats (random pairs)
├── Virtual lunch (scheduled together)
├── Game sessions
├── Show and tell
└── Learning sessions
Best Practices
For Remote Collaboration
Anti-Patterns
REMOTE WORK MISTAKES:
✗ Treating remote like office (constant sync)
✗ No written documentation
✗ All meetings, no async
✗ Ignoring timezone burden
✗ No social connection
✗ Always-on expectations
✗ Camera-off culture
✗ Unclear response expectations