How a Fully Remote Startup Communicates Across eight Time Zones
Overview
Over the past two years, our fully remote, globally distributed startup has grown to around 25 people with no offices, minimal live meetings, and no time-tracking apps. Our team spans roughly a dozen countries, with digital nomads making counting a challenge. This post shares how we approach communication in a distributed environment and what benefits we’ve observed from embracing asynchronous workflows.
Core idea: prioritize asynchronous communication
The key takeaway: effective remote teams default to asynchronous communication. Real-time meetings are expensive in a distributed setup, often interrupting deep work and reducing overall productivity. By designing a system that favors asynchronous exchanges, a global team can stay aligned without forcing everyone to be online at the same moments.
Practical strategies we’ve implemented
1) Establish clear communication norms across the organization
– We use a simple, explicit flow for how information should be shared, depending on the situation.
– For external partners or clients, the default channel is email.
– For urgent, quick internal matters, we use direct messages in Slack.
– For thoughtful discussions or conversations not requiring immediate action, we use a forum-like platform tailored for ongoing conversations.
– Why this helps: it ensures consistency, reduces disruptive notifications, and protects deep work time.
2) Invest in writing skills
– Much of async communication is written. High-quality writing reduces back-and-forth and clarifies intent.
– We document our communication rules in a central handbook (e.g., a Notion document) so everyone follows the same standards.
3) Minimize meetings where possible
– Meetings have a clear purpose: brainstorm sessions and team-building are valuable for distributed teams; most other activities should be handled asynchronously.
– If a meeting is necessary, schedule it with purpose and timeboxed expectations to avoid spillover and context-switching.
A provocative exercise: try a completely async week
– If you’re struggling with too many meetings, try a week without any meetings. It may be imperfect, but it can reveal what truly requires real-time discussion and what can be resolved asynchronously. We tried this and found it highly insightful.
Additional context
Our distributed model aligns with our product’s mission: enabling global teams to hire, pay, and manage across borders. The systems we’ve built make this possible and help keep everybody aligned without forcing everyone into the same local clock.
A closing note on meetings and productivity
Consider a typical 9-to-5 with two meetings scheduled for 11 AM and 3 PM. For many workers, those meetings can erode roughly 90% of the day’s productive time. The cycle includes the time spent transitioning to work after an early meeting, the time between meetings, and the final hours of the day when deep work is unlikely. Reducing meeting frequency and adopting asynchronous processes can preserve large blocks of focused time.
If you’re curious, I’m continuing to explore topics around innovation, well-being, and knowledge systems in remote environments. I’d be happy to turn this into a series if there’s interest.
