In partnership with
Hey there! 👋
Building a remote team is wild because on paper it looks like: hire great people, communicate clearly, ship great work.
In practice it looks like: three Slack messages, two emails, one voice note, and a prayer that everyone's working off the same version of the doc.
Giphy
The Remote Communication Problem
When everyone's in an office, you can just walk over to someone's desk. When everyone's remote, you need systems or you end up with:
Messages lost in seven different channels
Nobody sure if they should Slack, email, or wait for the weekly call
People working on outdated information because they missed an update
Time zone chaos that makes scheduling anything a nightmare
Here's what actually works for our team spread across multiple continents and time zones.
The Communication Stack
Slack for Real-Time (But Not All-The-Time)
We use Slack, but with rules:
Urgent stuff only goes in Slack
Everything else goes in async channels (email, project management tools)
Notifications off after 6 PM your local time
No expectation of immediate responses
The key: Slack is for "now" conversations and updates, not everything conversations.
Email for Documentation
If it needs to be referenced later, it goes in email. Project decisions, client feedback, important updates - all email.
Why? Because Slack messages disappear into the void. Email is searchable forever.
Loom for Complex Explanations
If you're typing more than three paragraphs to explain something, record a Loom instead. Show your screen, talk through it, done in two minutes.
This has saved us hours of back-and-forth messages trying to explain visual concepts through text.
Weekly All-Hands for Alignment
One hour, same time every week, mandatory attendance. We cover:
What shipped last week
What's coming this week
Blockers anyone's facing
Wins worth celebrating
This keeps everyone aligned without constant check-ins.
Giphy
The Timezone Rules
All meeting times include the timezone (9 AM EST, not just 9 AM)
Record everything so people can catch up async
Default to async communication when possible
The Response Time Expectations
Document this explicitly, here’s an example:
Slack: respond within 2 hours during your work hours
Email: respond within 24 hours (on business days)
Project comments: respond within 48 hours
Weekend messages: nobody expects responses until Monday
Clear expectations mean nobody's anxiously waiting or feeling guilty about delayed responses.
Giphy
The Real Secret
Remote teams don't fail because of distance. They fail because of unclear communication norms.
Your team needs to know: Where do I ask this question? How fast should I expect an answer? What's urgent versus what can wait?
Answer those questions once in a documented system, and suddenly remote work stops feeling chaotic.
& reminder, this was a 4 part series - if you’re just tuning in head to Goodknight Operations to read the full series
💜 Tara
& now a word from our sponsor!
4x your communication output. Same quality. No burnout.
The bottleneck isn't what you want to say — it's how long it takes to type it. Wispr Flow removes the bottleneck.
Speak naturally and get polished, send-ready text for executive summaries, client updates, board recaps, investor notes, or just the 30 Slack messages you're behind on. Flow strips filler, formats numbers and lists, and preserves your tone.
Used by teams at OpenAI, Vercel, and Clay. 89% of messages sent with zero edits. Works in every app on Mac, Windows, and iPhone.
