Working with Remote Team Members | Async Best Practices
Collaborate with remote team members using async-first communication. GitScrum provides visibility and documentation for distributed dev teams.
8 min read
Remote work requires intentional practices that don't happen naturally in offices. The teams that thrive remotely have clear communication norms, async-first workflows, and tools that keep everyone connected. This guide covers practical patterns for remote team collaboration.
Remote Collaboration
| Challenge | Office Solution | Remote Solution |
|---|---|---|
| Quick question | Walk to desk | Async message |
| Alignment | Hallway chat | Written docs |
| Brainstorm | Whiteboard | Virtual board |
| Status check | Standup | Async update |
Async-First Communication
Writing Over Talking
ASYNC-FIRST PRINCIPLES
══════════════════════
DEFAULT TO ASYNC:
─────────────────────────────────────
Before scheduling a meeting, ask:
├── Can I write this instead?
├── Can they respond when available?
├── Does this need real-time?
├── Is the topic complex enough for sync?
└── Most things work async
WHEN SYNC MATTERS:
─────────────────────────────────────
├── Complex problem-solving
├── Conflict resolution
├── Relationship building
├── Sensitive topics
├── Brainstorming with energy
└── Schedule intentionally
WRITTEN COMMUNICATION:
─────────────────────────────────────
Benefits:
├── Anyone can read anytime
├── Creates documentation
├── Time to think before responding
├── Searchable history
├── Includes all timezones
└── Respects focus time
HOW TO WRITE ASYNC:
─────────────────────────────────────
Subject: Clear topic
Context: What they need to know
Request: What you need from them
Deadline: When you need response
Format: Make it scannable
Example:
"Subject: API design decision needed
Context: Building user endpoint for mobile.
Two options:
A) REST with pagination
B) GraphQL with cursor
I lean toward A for simplicity.
Request: Your thoughts by Friday.
We'll finalize Monday and start building."
Async Standups
ASYNC DAILY UPDATES
═══════════════════
INSTEAD OF SYNC STANDUP:
─────────────────────────────────────
Written update each day:
├── What I did yesterday
├── What I'm doing today
├── Any blockers
└── Posted by X:00 their time
GITSCRUM UPDATES:
─────────────────────────────────────
Option 1: Slack integration
"At 9am, share tasks completed yesterday
and tasks planned for today."
Option 2: Comment on tasks
Update task with progress note.
Team sees activity feed.
Option 3: Standup board
Dedicated standup section.
Each person posts update.
Read async, discuss if needed.
BENEFITS:
─────────────────────────────────────
├── No timezone conflicts
├── Written record
├── Read when convenient
├── More thoughtful updates
├── No 15 min × N people wait
└── Focus time preserved
SYNC STANDUP STILL USEFUL:
─────────────────────────────────────
Weekly video standup:
├── Face time builds connection
├── Discuss blockers together
├── Alignment check
├── But only when overlapping hours
└── Record for absent teammates
Timezone Management
Working Across Zones
TIMEZONE STRATEGIES
═══════════════════
MAP YOUR TEAM:
─────────────────────────────────────
Team Timezone Map:
├── Sarah: PST (UTC-8)
├── Mike: EST (UTC-5)
├── Alex: CET (UTC+1)
├── Emma: IST (UTC+5:30)
└── Max spread: 13.5 hours
OVERLAP HOURS:
─────────────────────────────────────
Find common working hours:
PST EST CET IST
─────────────────────────────
6am │ ░░░ ░░░ ░░░ ███ │
9am │ ░░░ ███ ███ ███ │
12pm │ ███ ███ ███ ░░░ │
3pm │ ███ ███ ░░░ ░░░ │
6pm │ ███ ░░░ ░░░ ░░░ │
Overlap: 9am-12pm PST (3 hours)
This is precious—use wisely.
USE OVERLAP WISELY:
─────────────────────────────────────
Reserve for:
├── Sync meetings that need everyone
├── Real-time collaboration
├── Quick decisions needed
├── Team bonding
└── Don't fill with regular meetings
TIMEZONE TOOLS:
─────────────────────────────────────
├── World time buddy
├── Calendar showing teammate zones
├── Slack timezone display
├── Meeting times in multiple zones
└── Never schedule someone's midnight
Follow-the-Sun
FOLLOW-THE-SUN WORKFLOW
═══════════════════════
CONCEPT:
─────────────────────────────────────
Work flows around the globe.
As one region ends day,
another picks up.
24-hour progress possible.
EXAMPLE:
─────────────────────────────────────
Day 1, 9am IST:
Emma reviews overnight PRs.
Starts new feature work.
Leaves notes for Alex.
Day 1, 2pm CET:
Alex picks up from Emma.
Continues development.
Leaves notes for Mike.
Day 1, 10am EST:
Mike picks up from Alex.
Finishes and merges.
By Emma's morning: done!
HANDOFF DISCIPLINE:
─────────────────────────────────────
At end of day:
├── Write status update
├── What's done
├── What's next
├── Where you're stuck
├── What decisions needed
└── Explicit handoff
In GitScrum:
├── Update task status
├── Add comment with context
├── @mention next person
├── Clear, complete information
└── They can start without asking
Remote Meetings
Effective Video Calls
REMOTE MEETING BEST PRACTICES
═════════════════════════════
BEFORE MEETING:
─────────────────────────────────────
├── Clear agenda shared in advance
├── Pre-read materials if any
├── Right attendees only
├── Timezone-friendly time
├── Duration: 25 or 50 min (not 30/60)
└── Meeting optional if possible
DURING MEETING:
─────────────────────────────────────
├── Cameras on (when practical)
├── One person talks at a time
├── Chat for questions/reactions
├── Screen share for context
├── Someone takes notes
├── Start and end on time
└── Facilitation matters more remotely
AFTER MEETING:
─────────────────────────────────────
├── Summary posted (async attendees)
├── Decisions documented
├── Action items assigned
├── Recording available
├── Follow up in writing
└── Don't require meeting to know outcome
MEETING ALTERNATIVES:
─────────────────────────────────────
Instead of meeting:
├── Loom video (explain async)
├── Written RFC (collect feedback)
├── Slack thread (quick discussion)
├── GitScrum comments (in context)
└── Meeting is last resort
Building Connection
REMOTE TEAM BONDING
═══════════════════
INTENTIONAL CONNECTION:
─────────────────────────────────────
Unlike office, connection doesn't happen.
Must be intentional.
IDEAS:
─────────────────────────────────────
Virtual coffee chats:
├── Random 1:1 pairings weekly
├── 15 minutes, non-work topics
├── Donut bot for Slack
└── Build relationships
Team social time:
├── Monthly virtual happy hour
├── Online games together
├── Show and tell (hobbies)
├── Celebrate wins together
└── Optional but encouraged
Daily rituals:
├── Morning greeting in chat
├── End of day "logging off"
├── Sharing wins/blockers
├── Photo sharing channel
└── Human presence in async
AVOID:
─────────────────────────────────────
├── Forced fun
├── Too many events
├── Only work topics ever
├── Ignoring new team members
└── Assuming connection happens naturally
Documentation
Write Everything Down
REMOTE DOCUMENTATION
════════════════════
WHY CRITICAL:
─────────────────────────────────────
In office: "Just ask someone"
Remote: That person is asleep.
Documentation = 24/7 answers.
WHAT TO DOCUMENT:
─────────────────────────────────────
Onboarding:
├── How to set up dev environment
├── Who to ask for what
├── Team norms and practices
├── Where things are
└── New person self-sufficient
Decisions:
├── What was decided
├── Why (context)
├── Who was involved
├── Date
└── Searchable later
Processes:
├── How we do releases
├── PR and review process
├── Standup format
├── On-call rotation
└── Step by step
Technical:
├── Architecture overview
├── API documentation
├── Runbooks
├── Common issues/fixes
└── Updated with code
WHERE TO DOCUMENT:
─────────────────────────────────────
├── GitScrum: Task-specific context
├── Wiki/Notion: Evergreen docs
├── README: Repo-specific
├── ADRs: Architecture decisions
└── One source of truth
GitScrum for Remote
Remote Features
GITSCRUM REMOTE COLLABORATION
═════════════════════════════
TRANSPARENT STATUS:
─────────────────────────────────────
Everyone sees same board.
├── Current work visible
├── Progress tracked
├── Blockers flagged
├── No "what are they doing?"
└── Trust through transparency
ASYNC COMMUNICATION:
─────────────────────────────────────
Task comments:
├── Context stays with task
├── Anyone can read anytime
├── History preserved
├── @mentions notify
└── Discussion in context
NOTIFICATIONS:
─────────────────────────────────────
Configure per person:
├── Slack integration
├── Email digests
├── Mention notifications
├── Status change alerts
└── Stay informed without noise
INTEGRATIONS:
─────────────────────────────────────
├── Slack: Updates in channels
├── GitHub: PR links to tasks
├── Calendar: Sprint dates
├── Video: Meeting links
└── Unified workflow
Best Practices
For Remote Work
Anti-Patterns
REMOTE WORK MISTAKES:
✗ Too many meetings
✗ Expecting instant responses
✗ No documentation
✗ Ignoring timezone
✗ All work, no connection
✗ Micromanaging remotely
✗ Hiding information
✗ Office practices remotely