Key Takeaways
- Remote teams fail on trust, not tools. The tools are abundant and cheap.
- Over-communication is not a bug in remote environments. It is the feature.
- Time zone distribution is a real constraint. Pretending otherwise is expensive.
Saim Abbasi built SA Media as a distributed company from the start. The decision was partly practical, the best people for specific roles were not in the same city, and partly philosophical: a company that can operate effectively without physical co-location has a structural flexibility that collocated companies do not.
That belief has been tested by real experience. Remote teams can absolutely outperform collocated teams. They can also fragment faster and in ways that are harder to detect. The difference is in the operational choices made from day one.
Async Communication as a First-Class Discipline
The failure mode of most remote teams is defaulting to synchronous communication for decisions that could be made asynchronously. Every meeting that could have been a well-structured document represents a lost opportunity for the team members in inconvenient time zones, and it creates artificial urgency that crowds out deep work.
At SA Media, Saim built the communication defaults around written documents first. Any decision with meaningful stakes required a written brief that laid out the context, the options, the recommendation, and the reasoning. Team members had 24 hours to respond asynchronously before a synchronous discussion was scheduled if needed. Most decisions were resolved without a meeting.
The Trust Architecture
Remote teams fail on trust, not tools. The tools for remote collaboration are excellent and widely available. The trust required to operate effectively without physical presence is built through different mechanisms than in an office environment.
The practices that build remote trust at SA Media were: transparent goal-setting where everyone could see what everyone else was working toward, consistent delivery on small commitments before large ones were given, and regular one-on-ones that were genuinely about the person rather than the work.
When to Bring the Team Together
Remote-first does not mean remote-always. Saim's experience is that bringing distributed teams together in person twice a year, for a full week each time, maintains the relational foundation that async communication depends on. People who have shared meals and resolved a problem together in person have a social context that makes the written communication richer and the trust easier to maintain.
The companies that skip this and are fully remote with no physical gatherings tend to develop communication that is transactional and formal in ways that erode the energy that good remote teams run on.
"A remote team that does not communicate asynchronously well is not a remote team. It is an office team with worse meeting rooms."