New year's resolution: Kiss status meetings goodbye

[#1]

👋 fellow Atlas users!

Time is precious, especially in an increasingly remote and distributed work environment. As we fast approach the start of a new year, now's a good time to start thinking about changes you would like to make resolutions to improve the way your team/department/company operates. And we have an idea for you.

I am personally looking forward to 2023 being a year where we strike every wasteful meeting from our calendars. In fact, we've already started here at Atlassian, thanks to Atlas.

Atlassians are saving up to 1 hour every week

In a recent survey of employees, 90% of respondents who shared that Atlas helped their team have fewer meetings about the status of their work reported they were saving up to 1 hour's worth of meetings each week. For the other 10%, it was up to 2 hours.

Imagine that, giving everyone at your company an hour back every week. Add it all up and that's a lot of time every month, quarter, and year you can put back into more activities that yield better outcomes. That might be time to focus on deep work. Or it might be time to connect and bond with your team. Heck, it could even be an hour to simply rest and recharge.

So, how do we do it?

We practice The Loop with Atlas.

If you'd like to see how your teams can too, check out the talk @Rachel Lin and I gave recently at Atlassian's inaugural Work Life event at the Chase Center in San Francisco. 

Here's to cleaner calendars and time better spent in 2023. Powered by Atlas of course. 😊

[Carlos Garcia Navarro]

Cool article, @Matt ! Thanks for sharing!

[Matt]

Thank you, @Carlos Garcia Navarro

[Ajay _view26_]

Great presentation @Matt & @Rachel Lin .. gave me an overview of Atlas and its structure

[Matt]

Thanks @Ajay _view26_ Glad you found it helpful. 🙌

[Dave Mathijs]

Well done @Matt and @Rachel Lin ! Actively using Atlas for project updates.

[Trilok Rawat]

Thanks @Matt and @Rachel Lin on sharing thoughts. Could you please clarify - will it not be possible that the Automation takes inputs from Curation itself.

[Emile Steenkamp]

Nested responses in Jira would've been perfect to solve for this.

[Summer Hogan]

Great job on this @Matt! Thank you for sharing this!