Unlike our friends over at Buffer who have colleagues in different parts of the world, the team at Threads is currently spread throughout both the US and Canada. So when our very own software engineer, Abdul Jamjoom, traveled back to his native Saudi Arabia for a month, he experienced firsthand what a lot of teams were grappling with this past year—remote work stretched to its limits.
There was a bit of a learning curve when adjusting to a 10-hour time difference between Jeddah and San Francisco. To put this in perspective, Abdul sums it up best:
Being 10 hours ahead of my colleagues means that they end their workday when I start mine, and vice versa.'
How Threads became a “required” tool
While residing in Los Angeles and speaking about Threads with his friends, Abdul would refer to the product as “an excellent asynchronous collaboration tool.” And well, he does work at Threads, so we can’t say we’re not happy to hear so.
However, after working from Jeddah for a month, Abdul’s view of Threads shifted. The product went from a “nice-to-have” to a “must-have” tool for getting work done—and his first-hand experience helped to pave the path for new features within Threads itself, some of which we can’t wait to share soon.
The coolest part of Abdul’s experience? The fact that the rest of the team can learn from it, too. With fully distributed customers like Buffer and Impala Travel, our collective empathy for remote teams has evolved and grown based on the personal experiences of our teammates, especially this past year. We look forward to sharing more about how these experiences show up in our product in the coming months.
Are you on a distributed team spread across time zones? We want to hear from you! Drop us a line at email@example.com or send us a DM @Threads.