Quick question for teams working async

[Evan Fishman - Rally for Jira]

What’s the one thing you’ve done that made a real difference in async communication?

We’ve been diving deep into async team workflows lately, and I’d love to hear what’s worked (or hasn’t) for others.

[PJ Zaiac]

Hi @Evan Fishman - Rally for Jira! 👋🏻 

Chiming in with a slightly-biased answer, but it actually comes from long before my time here at Atlassian - Loom has CHANGED THE GAME for me.

For the full context, prior to joining the community team here I helped found a startup with a globally dispersed team - we had teammates spread across 4 VERY different time-zones (if you've worked with folks across an ocean, you know the feeling). While some of our teammates were willing to take midnight meetings and totally re-arrange their days around our HQ's hours, I always felt icky bragging about loving my own work-life balance knowing that other members of the team didn't have the same reality.

Loom became a life-saver in being able to feel like we were all in the room, just at different times based on our local working hours - and it gave those 'after hours' back to our teammates in different timezones. Even better, it works for everything from bug reporting and product feedback to company-wide announcements and catching up on meetings outside of your local timezone. 

I was so excited to join Atlassian partially due to Loom, and have loved continuing to leverage Loom for async communication for the year+ I've been on the team here too! 💙 

[Lauren McGoodwin]

Using Loom to share demos, weekly updates, and recapping meetings has been a GAMECHANGER for my communication within a remote team.

[Andy Gladstone]

Another Loom mention is due here. Recording videos at 2AM in my time zone, that can be shared for follow-up and viewing by team members at a later (or earlier) time in their timezones has been a game changer. It also provides evergreen content for Confluence and to be used in our training documentation.