After three years of fully remote work, we've learned what actually makes distributed teams thrive — and what silently kills them.
Three years ago we made the decision to go fully remote — not remote-friendly, not hybrid, but remote-first. Here's everything we've learned since then.
What actually kills remote teams
It's not timezone differences. It's not the lack of a physical office. It's ambiguity. Remote work surfaces every unclear process, every undefined expectation, every assumption that used to get resolved by bumping into someone in the hallway. If you don't fix your processes, remote will expose them brutally.
The things that work
Written culture. We write everything down. Meeting notes, decisions, context, rationale. If it wasn't written, it didn't happen. This forces clarity and creates a searchable institutional memory.
Async by default. We don't default to a meeting when a doc would do. We don't default to a Slack message when an email would do. Fewer interruptions means deeper work.
Camera-optional video calls. We used to require cameras. Then we noticed people were spending mental energy managing how they appeared instead of what was being discussed. Camera-optional changed the energy of every meeting.
The things we got wrong
We underinvested in social connection early on. When you remove the organic moments of office life, you have to deliberately create replacements. We now have weekly virtual coffee pairs (random pairing, 25 minutes, no agenda) and a monthly in-person offsite. Both are non-negotiable.