Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What “async” tactics or tools will you try with your team this year?

"Async collaboration" may be the way of the future...but it's still a new concept.

This powerful form of teamwork helps move projects forward, regardless of your team's time zones or geographic locations. It allows you to get work done more efficiently, reducing face-to-face meeting time and freeing up schedules.

Successful async collaboration, however, requires thought, planning, and effort. And with any new concept, there's a lot we can learn from each other. That's the purpose of this post.

Please comment below to share and discuss your "async" tactics or tools you plan to try with your team this year.

Here's the prompt: Name two "async" tactics of tools you plan to try with your team this year. Explain why and how.


If you're enrolled in the Atlassian University course on Async Collaboration for Distributed Teams...once you've shared your comment below, return to your Atlassian University browser tab to complete the course.

If you're not enrolled in the full course, but would like to be, we'll add an enroll link here soon when the course launches on January 17th, 2023. 

Thanks all! Looking forward to reading your thoughts and ideas.



Note: this article is a prompt within an Atlassian University course, Async Collaboration for Distributed Teams (link coming soon). In this activity, learners have the opportunity to provide their advice and suggestions on Community. Even if you haven’t taken the course, you’re still welcome to respond to this post and give your advice.


We are working to find the right approach for using the Jira toolset to manage our operational processes and resource management across the enterprise (vs for software development).

I note also that we are exploring ways to parse out meetings so that elements of them can be asynch while retaining only what really must be discussed in person. For example, the initial idea or sticky generation for our retrospectives can be done asynchronously, so that our time together is spent just on discussion of what's been generated. 

One concept that I'm working with as well is the benefit of asynch methods to support team members who are not as comfortable in a group, on camera, etc. 

Like # people like this

Love these @Lisa Yeager , thanks for your thoughts here! I agree, retrospective ideation seems like a great candidate to shift to async. We've also found this helpful when brainstorming new ideas. Have everyone add stickies async, so then the sync time together can focus more on discussing the ideas, and less on coming up with new ones.

Your last note is also very important! Distributed work is brand new and I think we're all still trying to figure out how to best operate within it. Even individuals that enjoy groups and being on camera could probably use a break from Zoom every once in a while. Great concept and use case here, thanks for sharing...I'm going to ponder that one a bit more.

Like Andy Gladstone likes this

As our team grows, and expands further across time zones, I'm more and more interested in creating a more productive async environment. I think a key piece for me this year will be to ensure meetings have agendas (which are actually followed) to ensure that the time we do have together is used to the fullest extent. I'd like to also be more intentional about note-taking during meetings, as well as storing those meeting notes somewhere accessible for others to allow people who aren't needed in the initial conversation a chance to review the meeting minutes when it works in their schedule.

I like promoting more asynchronous work since everyone's energy levels are different throughout the day - so even if we're in the same (or close to the same) time zone, there are different points in my day that are more suited for reviewing things that could be done asynchronously. 

Gitlab has some fantastic asynchronous information available that I've been meaning to dig into deeper. I struggle with how to make changes within my team from what I know since everyone is rather set in their ways. I also think there needs to be a clear shift (as a team) from working standard hours to working in a way that suits your energy. This could allow for 4 day weeks, broken days with a long lunch, etc. but the team would need to be on board. In my case, I think I'd struggle with feeling like I had accomplished enough without working a somewhat standard "day" just due to my current tasks. Something for me to ponder/noodle on! 😀

Like # people like this
Xoch I'm New Here Jan 20, 2023

HI! I am managing an international team remotely. I find these tips very helpful. I am going to introduce async collaboration work to my team step by step. 

I am using Miro in my meeting. I find it very helpful to use a whiteboard to throw ideas and then convert them into Issues directly in Jira.

Doing the async pre-work and establishing things like in an agenda and sending reading materials a couple of days before can save a lot of time.

Like Andrew DeBell likes this

I look forward to using Atlas for status updates. Whether the team is async or not those statuses should be on record for reference.

I think it's a good habit, when writing messages for async response, to take a moment to consider what chances the other party has to give a meaningful answer. If the other party can't understand what I ask or might misunderstand or maybe will need to ask somebody else or tell me to ask somebody else, then it's any number of hours wasted. This is especially true when collaborating with people with other native languages.

Like Andrew DeBell likes this

I would like to integrate power BI, Trello and another tool with a roadmap so that all team members can see where we are and where we are going

Like Andrew DeBell likes this

Gradually eliminate walk the board meetings that typically have no back and forth conversations with Teams group chats.

Have team members keep task information up to date in Jira to keep the async status alignment exercise short.

Like Andrew DeBell likes this

I intend to work with my team to encourage better use of Slack for aync comms such as the Daily Stand-up.  We have a large distributed team on multiple continents, and by putting stand-up notes in a Slack chat we can ask folks to call out discussion items needing synchronous collaboration, to maximise the window of time we can second together.

Also I will encourage the  team to set their dedicated time windows to do things such as respond to e-mails, or slack discussions - and to reduce the always on approach, with lots of distractions.

Like Andrew DeBell likes this

Unfortunately, not all the tools shown in the Async Collaboration for Distributed Teams training are available where I work. I intend to find equivalents, share these learnings with my team, and gently promote their use. I look forward to using the Working Agreement template, too. 

Like Andrew DeBell likes this

Hi, the course gave me a few ideas on how we can save off the weekly meeting burn. 
Top of the list would be the summary/ context video. This would shave off hrs of “pre/ setting the context ”meetings. 
In addition, I am going to explore the built-in Whiteboard and how well it integrates to tickets and dashboard components within Jira. 

Two async practices I plan on trying with my team is:


  • Confluence-based standup meeting notes. This way the entire team can look back at past questions, actions, and even add new ones before an in person meeting. This would save a good amount of time.
  • The whiteboard could prove invaluable for async brainstorming and planning.

Hi! As a Project Manager in a global organization, finding time for synchronous status meetings always left some attendees having to join outside of traditional office hours. I plan on introducing the following practices in future projects:

  • Using whiteboards for brainstorming, decision-making, and project planning.
  • Replacing status meetings. Instead, use the video time for team building.
  • Encourage on-going participation through the use of Slack and comments on Confluence or Jira.

I'm looking forward to experimenting!

So exciting to learn new methods of communication and interactions without being live. Giving time to edit or modify even a comment. Looking forward to collaborating.

Using asynch tools to prep for synch meetings is especially powerful and intriguing. I especially like the whiteboard for brainstorming and creating quick video explainers. Using Confluence as the tool where the work happens is key. My experience with other project management tools is that they result in a kind of “task war” where posting tasks is more important than doing the actual work!

I think the two async tools I'd like to use more with my team are messaging tools and status tools. These two tools, when used well, could replace regular sync calls in which there's very little collaboration or discussion.

I am looking to leverage the status updates and status notifications with the team.  

I think the discussion about pre-work is  useful since I've started a new job and I've been working hard to set meetings up. The async side is also good where we only need to have a single place to do the work which is available to all.

As PM I want to reduce the number of tools used to update the status from 3 to 1 (Confluence), so everyone could see the latest report based on Jira data and written updates.

I also want to encourage my team to share updates before a meeting starts, so everyone could see them and then we pick the most important to discuss in a meeting.


Log in or Sign up to comment

Atlassian Community Events