Chapter 6: Remote & Distributed

The Remote Reality

Remote and distributed teams are now the norm, not the exception. Traditional co-located standup wisdom doesn't always apply.

Challenges:

• No physical presence or body language
• Time zone differences
• Connection and video issues
• "Zoom fatigue"
• Harder to build rapport
• Easy to multitask and disengage

Advantages:

• Written records (async standups)
• Can include people anywhere
• Flexibility for team members
• Reduced commute stress

This chapter shows you how to make remote standups work.

Synchronous Remote Standups

Setup Requirements

Video:

• ✅ Cameras on, always (non-negotiable)
• ✅ Stable internet connection
• ✅ Good lighting (face visible)
• ✅ Professional background
• ✅ Gallery view (see everyone)

Audio:

• ✅ Decent microphone (not laptop mic if possible)
• ✅ Quiet environment
• ✅ Headphones to prevent echo
• ✅ Mute when not speaking

Platform:

• Zoom, Google Meet, Teams, or similar
• Screen sharing capability
• Chat for links and notes
• Recording for async review

The Virtual Standup Script

Host starts meeting 2 minutes early

9:28am - Meeting opens, small talk
9:30am - "Alright, let's start. Everyone's here. Quick standup today.
         Same format as always. Sarah, want to kick us off?"
         
[Sarah shares her update]

"Thanks Sarah. John, you're next."

[John shares]

[Continue around the team]

"Great standup, everyone. Three action items:
1. Bob will help Alice debug that API issue at 11am
2. Carol will review John's PR by EOD
3. I'll follow up with the ops team about the staging environment

Thanks everyone. Have a great day."

9:40am - Meeting ends

Camera Best Practices

Why cameras must be on:

• Shows respect and engagement
• Nonverbal communication is visible (nodding, reactions)
• Builds human connection
• Keeps people accountable
• Reduces multitasking

"But I'm not camera-ready":

• It's 9:30am and you have a standing meeting
• Plan accordingly
• Use virtual background if needed
• Professional appearance matters

Legitimate exceptions:

• Bandwidth issues (audio only okay)
• Personal emergency
• Technical problems

But 95% of the time, cameras should be on.

Managing Virtual Attention

Signs someone is multitasking:

• Looking down at phone/laptop
• Typing during others' updates
• Delayed responses when addressed
• No facial reactions or engagement

As facilitator:

"Hey John, I notice you're multitasking. Can I get your full attention
for these 10 minutes? Thanks."

As participant:

• Close email and Slack
• Full-screen the video call
• Take notes with pen and paper (or visible notepad)
• React with head nods, thumbs up, facial expressions

Technical Issues

When video freezes or audio cuts:

Facilitator: "Alice, we lost you. Can you hear us?"
[Wait 10 seconds]
Facilitator: "Okay, moving on. Alice, DM me your update and we'll 
            sync after."

Don't wait forever. Keep the standup moving.

Async Standups

For teams across many time zones, async standups work better than forcing someone to join at 3am.

Choosing Async vs. Sync

Use async when:

• Team spans 8+ hour time zone difference
• Team values deep work and minimal meetings
• Team has strong written communication culture
• Work is less interdependent

Use sync when:

• Team is within 4-6 hour time zone difference
• Rapid collaboration is needed
• Team needs human connection
• Onboarding new members

Use hybrid:

• Async updates + weekly sync call for connection

Async Standup Platforms

Slack/Discord:

• Dedicated #standup channel
• Daily threads
• Reactions for "I read this"
• Pin important blockers

Notion/Confluence:

• Daily standup page per person
• Searchable archive
• More structured format
• Better for lengthy updates

Specialized Tools:

• Geekbot: Slack bot that prompts for updates
• Standuply: Automated standup questions
• Range: Team check-ins and updates
• Dailybot: Slack standups and mood tracking

Async Standup Format

Template:

✅ Yesterday:
- Completed login API endpoint
- Reviewed Sarah's PR

🎯 Today:
- Start frontend integration for login
- Pair with Bob on database migration

🚫 Blockers:
- None

💭 Notes:
- Available for pairing after 2pm

Post by 9am your local time. Read others' updates within 2 hours.

Making Async Standups Work

Set clear expectations:

1. Post by 9am your timezone
2. Read all updates within 2 hours
3. React with 👍 when you've read
4. Respond to blockers immediately
5. If someone needs help, DM them

Enforce the habit:

• Automated reminders (bot)
• Manager checks daily
• Call out when people skip
• Make it part of team culture

Follow up on blockers:

Async standup: "🚫 Blocked on design approval"
You (reading): DM to designer: "Hey, can you prioritize this?"

The async standup is only as good as the follow-through.

Async Standup Anti-Patterns

❌ No one reads them

• Updates go into a void
• No engagement or follow-up
• Feels like busywork

❌ Too long and detailed

Bad: "Yesterday I started by reviewing the requirements document which
     took about 2 hours because there was a lot to understand, then I
     began working on the database schema..."

Good: "✅ Reviewed requirements, started DB schema (50% done)"

❌ Generic and useless

"Working on stuff. No blockers."

❌ Posted but never referenced

• No one cares
• Information is lost
• Better to just not do it

Hybrid: Async + Sync

Best of both worlds:

Monday-Thursday: Written async updates

Everyone posts by 9am their time
Team reads and responds async
Quick DMs for follow-up

Friday: 15-minute video sync

No repetition of written updates
Discuss blockers and coordination
Build team connection
Quick wins celebration

This works great for distributed teams.

Time Zone Strategies

The 3-Team Model

When team spans 16+ hours:

Americas team: 9am Eastern standup
EMEA team: 9am GMT standup
APAC team: 9am Singapore standup

Weekly all-hands: Rotating time (share the pain)
Async updates: Everyone posts daily
Tech leads sync: Coordinate across regions

The Rotation Model

When team spans 8-12 hours:

Week 1: 9am Eastern (Americas-friendly)
Week 2: 3pm Eastern (Europe-friendly)
Week 3: 9pm Eastern (Asia-friendly)
Week 4: Async (everyone's choice)

No one timezone is privileged. Share the pain.

The Core Hours Model

Define overlap hours:

Americas: 8am-5pm Eastern
Europe: 2pm-11pm Eastern (9am-6pm Central European)
Overlap: 2pm-5pm Eastern = Core standup hours

Standup happens during overlap.

Outside core hours: Async updates

The Follow-The-Sun Model

For 24/7 operations:

Morning standup (9am local):
- Americas team reviews APAC updates
- Discusses handoffs

Midday standup (9am local):
- EMEA team reviews Americas updates
- Discusses handoffs

Evening standup (9am local):
- APAC team reviews EMEA updates
- Discusses handoffs

Work literally follows the sun around the globe.

Building Connection Remotely

The Problem

Remote teams lack:

• Hallway conversations
• Lunch together
• Coffee breaks
• Casual bonding
• Serendipitous collaboration

Standup becomes one of few touch points.

Human Connection in Standup

Start with 2 minutes of connection:

"Before we start, how's everyone doing? Any weekend highlights?"

"Quick check-in: What's your energy level today? 1-10."

"Non-work question: What's something good that happened this week?"

End with recognition:

"Before we go, any shoutouts? Anyone want to recognize someone?"

Beyond Standup

Don't rely only on standup for connection.

Weekly:

• Virtual coffee chats (random pairs)
• Team lunch (everyone orders food, eats together on Zoom)
• Friday wind-down (optional social call)

Monthly:

• Team retrospective
• Virtual game or activity
• Show and tell (personal or professional)

Quarterly:

• Team offsites (if budget allows)
• Virtual team building event

Remote Standup Tools

Screen Sharing

When to share your screen:

• Walking the board (Jira, Trello, etc.)
• Showing diagrams or architecture
• Demonstrating something

When NOT to share:

• Just doing verbal updates
• No visuals are needed
• Slows down the standup

Digital Boards

Jira/Trello/Asana:

• Visual workflow
• Real-time updates
• Everyone sees same view
• Async collaboration possible

Miro/Mural:

• Virtual whiteboard
• Visual standup board
• Draw connections
• More creative formats

Standup Bots

Geekbot (Slack):

• Automated standup questions
• Async responses
• Aggregates updates
• Reminds people to post

Standuply (Slack):

• Customizable questions
• Mood tracking
• Anonymous feedback
• Retrospectives

Range:

• Check-ins and standups
• Team health monitoring
• Meeting notes
• Async updates

Timer Tools

Built-in Zoom timer:

• Share screen with timer
• Visual countdown
• Keeps standup on track

Standuply timer:

• Chrome extension
• Per-person timers
• Gentle alerts

Facilitating Remote Standups

The Remote Facilitator Role

Harder than in-person because:

• Can't see full body language
• Harder to interrupt politely
• Technical issues happen
• People hide behind mute button

Starting the Meeting

Open 2 minutes early:

• Small talk as people join
• Technical check: "Can everyone hear me?"
• Start exactly on time even if people missing

Opening script:

"Good morning everyone. Let's start. Quick standup today. Same format.
If you're blocked, speak up and we'll assign someone to help.
Alice, want to start us off?"

Managing the Flow

Keep energy up:

• Vary your tone
• React to what people say ("Great!" "That's helpful" "Thanks")
• Don't let silence linger

Handle long updates:

"Thanks John, I'm going to pause you there. Sounds like you have a
blocker on X. Let's take that offline. Can you wrap up in 30 seconds?"

Handle silence:

"Sarah, we haven't heard from you. Anything to share today?"

Technical Troubleshooting

Video issues:

• "Alice, your video is frozen. Audio only is fine."

Audio issues:

• "John, can't hear you. Try rejoining."
• Wait 30 seconds max, then move on

Connection drops:

• Don't wait forever
• Continue without them
• They can catch up async

Remote Standup Etiquette

As a Participant

Do:

• Join on time (2 minutes early even)
• Camera on, professional appearance
• Mute when not speaking
• Unmute before speaking
• Look at camera when speaking
• Pay full attention (no multitasking)
• React with nods and facial expressions

Don't:

• Join late without heads-up
• Keep camera off (unless legitimate reason)
• Eat during standup
• Work on other things
• Check phone
• Dominate conversation

As a Facilitator

Do:

• Open meeting early
• Start on time
• Keep energy high
• Enforce time limits
• Ensure everyone speaks
• Park detailed discussions
• End with clear summary

Don't:

• Wait for late people
• Let tangents happen
• Ignore technical issues
• Multitask yourself
• Go over time

Measuring Remote Standup Effectiveness

Quantitative Metrics

Attendance rate:

• Target: >95%
• Track who's missing regularly

Duration:

• Target: 10 minutes or less
• Track trends over time

Engagement:

• How many people speak?
• How many blockers surfaced?
• How many follow-ups happen?

Async read rate:

• What % of team reads updates?
• How quickly do they read?

Qualitative Indicators

Good signs:

• People arrive on time with cameras on
• Energy is positive
• Blockers are surfaced
• Follow-up happens after
• Team helps each other

Bad signs:

• Frequent absences
• Cameras off
• Low energy, monotone updates
• No blockers mentioned (hiding)
• No follow-up or action

Troubleshooting Remote Standups

Problem: Low Engagement

Symptoms:

• Cameras off
• Multitasking
• Monotone updates
• No questions or interaction

Solutions:

• Make cameras mandatory
• Call people out (gently) for multitasking
• Vary the format
• Start with human connection
• End with team recognition

Problem: Too Long

Symptoms:

• Regularly goes 20-30 minutes
• People arriving late
• Frustration visible

Solutions:

• Strict time limits (2 min per person)
• Use timer
• Facilitator interrupts
• Park all discussions
• Try "blockers first" format

Problem: Time Zone Pain

Symptoms:

• Same people always at inconvenient times
• Resentment building
• Regular absences from one region

Solutions:

• Rotate meeting times
• Split into regional teams
• Go fully async
• Record for those who can't attend

Problem: No Follow-Through

Symptoms:

• Blockers mentioned but not resolved
• Same issues every day
• No collaboration happening

Solutions:

• Assign owner to every blocker
• Track action items visibly
• Follow up in next standup
• Manager 1-on-1s to understand why

Remote Onboarding

First Standup for New Remote Employee

Before standup:

Email to new person:
"Tomorrow at 9:30am is our daily standup. Here's the Zoom link.
We go around and each person shares:
- What they worked on yesterday
- What they're working on today  
- Any blockers

It's super casual. Just introduce yourself briefly tomorrow and feel
free to just listen. You'll get the hang of it quickly."

During standup:

"Everyone, this is Alice joining us as a backend engineer. Alice, we'll
go around the room. Feel free to just introduce yourself briefly when
it's your turn. Welcome!"

After standup:

DM to new person:
"How did standup feel? Any questions? Happy to chat more about how we
do things."

Key Takeaways

1. Cameras on is non-negotiable for sync standups: it builds connection and accountability
2. Async standups work great across time zones: but need strong follow-through
3. No one timezone should be privileged: share the pain by rotating
4. Hybrid (async + weekly sync) balances flexibility and connection
5. Build extra connection time: remote teams need intentional bonding
6. Use tools strategically: bots and digital boards help coordination
7. Keep technical quality high: good audio/video matters
8. Facilitate actively: remote standups need stronger facilitation
9. Make async updates readable: no one reads walls of text
10. Follow through is everything: async updates are useless without action

Remote Standup Checklist

Before Standup

• [ ] Calendar invite with Zoom link
• [ ] Reminder 5 minutes before
• [ ] Open meeting 2 minutes early
• [ ] Check your video/audio quality
• [ ] Have digital board ready to share if needed

During Standup

• [ ] Start exactly on time
• [ ] Everyone's camera is on
• [ ] Each person keeps update under 2 minutes
• [ ] Blockers get assigned to owners
• [ ] Park detailed discussions
• [ ] End with clear action items summary
• [ ] End on time

After Standup

• [ ] Post action items in Slack/team chat
• [ ] Follow up on blockers assigned to you
• [ ] DM people who need sync-ups
• [ ] Track blocker resolution
• [ ] Record attendance (if tracking)

What's Next

Now you know how to run remote standups. Let's learn what NOT to do:

→ Chapter 7: Anti-Patterns: Common mistakes and how to avoid them