My team is using JIRA for project tracking and Confluence for knowledge sharing to help us work more efficiently across timezones and with several people being involved in projects. Using these asynch tools will help us all stay on the same page while maximizing productivity
The two areas of focus for async collaboration I think we can act on now is firstly, eliminating status meetings by employing a tool such Atlas and secondly, providing short videos of walkthroughs of design and/or developed product posted on Slack(or within the related Jira issue) for comment and review. Currently we mostly wait for sync meetings to demo and review and I think things can be missed or assumed to have been captured.
Our review/feedback system is one of our greatest challenges and getting everyone using the same tools & methods is our goal. For the most part we have good ways of working but after going through the course I can see our review/improvement mechanisms are slow so there is plenty of fertile areas where we can improve our collaboration and communication.
I will introduce to my team an experiment of using a 'statuschat' to allign on user story status combined with our weekly meeting where everyone is physicially present
Our organization is using Atlas and Jira task management system to improve Async communication. I have also implemented the confluence whiteboard for brainstorming and planning sessions, which will hopefully be helpful as the team has ample time to jolt down ideas before the actual meeting. This also reduced the meeting time significantly and helps the team to focus more on the work rather than just talk about it.
Planning on using links to Confluence pages and whiteboarding for meeting prep, to make sure that we get the most out of our time and that people who aren't as comfortable speaking up in meetings have the chance to fully participate and have their ideas noticed.
Using whiteboards for some ideas and brainstorming moments is great, and also using Atlas to share status can be really helpful. Looking forward to it.
I will try whiteboard and Confluence with my team.
Using async status meetings and whiteboard tool for brainstorming
The Async work its needed every day, more and more. Do the job you have to do and share with your team in the best possible way, does not obligate a call or a meeting.
There its so many ways to do that effectively, with a short video for example. Force weekly meetings its a not natural way to make things done.
1. Do a async prework before the sync meeting so the sync meeting is more successful.
2. Link the Confluence page to my jira item so it allows people to async and collaborate and provide responses on their own time.
My team uses Jira, but we have a 15 min daily standup meeting to review progress on each issue. I am thinking through the usefulness of this and if we could do this async instead. I do plan on sending our Retro document out sooner so that everyone gets the opportunity to start filling it out on their own time and possibly shorten the time we're taking in Retro.
Confluence is great for removing the lure to collaborate on a 'live' document, I've never had much luck with people updating a PPT or Word doc asynchronously.
Atlas seems ideal for removing unnecessary status meetings too - particularly limiting the characters so the updates are brief and not to onerous for others to read/review.
Been using Jira WM and Trello to track work but I will be adding these to async meetings moving forward. I would also want to use Atlas for high level async meetings, keeping everyone/stakeholders abreast on the status of the work/project
My no. 1 priority for async tools and strategies is to free up time for actual work by having fewer and shorter meetings, which I expect will save time and speed up our workflow/throughput.
Many people are so used to having meetings with everyone present that it can be a challenge to introduce new ways of working. But I expect the benefits to become apparent soon enough: Not everyone works full time, and those who don't sometimes have to cram all sorts of status meetings into the little time they have, maybe two days a week, leaving very little time for their actual work. Others have busy schedules and multiple project assignments, and will be just as grateful to be able to do more things on their own time.
The new cloud features make it easier to use Jira and Confluence together, and Atlas will add even more useful features to the mix. I have yet to explore how to combine Jira work management and Jira software features in a single project, which I believe is now possible.
My first step in the process is to start a new project using Confluence whiteboards for async ideation, and then demonstrate how easily we can turn this into Jira issues. There will be a kick-off meeting to warm everyone up to the idea of trying new ways of working together.
Add a new phase to the production phase to test in the test lab per ATP that Engr will provide.
Reduce the number of meetings for status updates
Try Atlas
Prework saves so much time. Working to get information onto proposed timelines and tasks without focusing on targeted due dates but on the work needed to be completed is key to focusing on enhancing value. Using quick video recordings (2 to 5 minutes) with key Calls to Action is another way to get easy to digest information in a visible and easy to digest manner.
I enjoy having asynchronous prework activities where we can collaborate and brainstorm independently before our scheduled meetings or events. It's a great way to come prepared, share valuable insights, and make the most of our time during the actual meeting. I also appreciate Trello for our team stand-up where we can visualize our meetings and tasks and easily update our cards/boards.
Confluence and Jira Work Management
I love using Jira on project management to track updates of task and Confluence to document progress and status.
Asynchronous Playtesting (like PlaytestCloud):
Collaborative Design Docs (using Google Docs or Notion):
Two "async" tactics or tools I plan to try with my team this year are:
1. Confluence for document collaboration – I will use Confluence to share documents and gather feedback asynchronously. This allows team members to review and provide input at their convenience, fostering deeper collaboration without needing constant meetings. By doing this, we will save time and streamline the decision-making process, as all stakeholders can see and comment on the latest version of the document.
2. Loom for video updates – I plan to use Loom to record quick video updates instead of holding meetings for every minor update. This helps keep everyone informed while respecting different time zones and schedules. Team members can watch the updates whenever they are available and leave comments or questions if needed, reducing the pressure to attend live meetings.
These tools will promote flexibility, improve productivity, and reduce the number of unnecessary meetings, helping the team focus on work while staying aligned.
One tool I intend to use would be Confluence, which will allow me and my team to post updates to our project and keep each other up-to-date without needing dedicated meeting days. One tactic I intend to employ would be async brainstorming ideation. I hope that by having team members brainstorm and post their ideas into a confluence page or board, this will help the brainstorming process when developing ideas to move our project forward.
Recommended Learning For You
Level up your skills with Atlassian learning
Redesign your workweek
Configure your calendar to prioritize high-impact work and goals. You'll learn how to set daily priorities, prioritize essential meetings, and schedule focus time.
How to run effective meetings
Lead efficient meetings that have clear goals, keep your attendees actively engaged, and use the Atlassian Playbook to improve meeting success.
How to build strategic guidance
Build a high-performing, effective team by providing clarity, defining success, and making it clear who will benefit from your efforts — a technique we call strategic guidance.