Ask us anything on December 15: How can you be a Team Changer with the Teamwork Collection?

[#1]

Hey Teamwork Collection Community! 👋🏽

The end of the year is fast approaching and we’re already thinking about our goals for the new year. How can we help you be a Team Changer and get your teams off to a fresh new start in 2026?

• What’s the biggest workflow challenge your team faces right now?

• Are there manual processes you wish you could automate?

• What’s one thing that would make teamwork easier for you?

Ask us anything! 👀

Our Teamwork Collection product experts are here to answer your questions, brainstorm solutions, and share team-changing tips with Jira, Confluence, and Loom.

Start submitting questions below, upvote submissions, and stay tuned as we will be answering anything and everything about being a Team Changer on December 15 from 10-11am PST!

[Abby Stiris]

So excited for this!! Here's my question for the experts: If you could go back to your first day setting up Teamwork Collection for your team, what would you highlight first to drive deeper adoption from day one?

[Avery W_ Krouse]

When will Rovo and Atlassian AI features be made available to users on HIPAA BAA environments? We want to use these features and already have BAAs in place with the major AI providers (OpenAI, Anthropic, and Google) and we’d love to incorporate Rovo into what we do but we can’t. Even if you can’t provide a timeline, I’d be grateful for even a “we’re working on it, stay tuned.”

[Brittany Soinski]

That's a great question @Abby Stiris

A great way to use the Teamwork Collection to successfully roll out the Teamwork Collection is to use Loom for change management along the way (e.g. announcing your new tools and ways of working, sharing enablement materials, updates from leadership). 

We have a great playbook that will show you how to do this, too!

[Gregory Van Den Ham]

At community events the biggest challenges i keep hearing about is administrators being surprised about new features dropping into their tenant without them knowing its coming.   

When we think about doing better, it starts with administrators having the proper information to set their users up for success and energizing their user base with prepared ways to educate and inform them of upcoming change.

happy administrators = happy customers.

I've proposed this type of change before by providing administrators an "admin dash panel", where when administrators log in, they are presented basic tenant information like upcoming releases, what's recently changed, etc.   This information needs to be specific to their tenant, and not generalized like you'll get this feature sometime in 3-6 months.

[Ahmet Kilic - T2T]

Thanks @Christa Parrish for opening this door :)

One of the biggest challenge is the lack of automation between Goals to Jira, Confluence and Loom.

• Goals is the tool for business stakeholders that make decision.
• Teamwork Collection (internal delivery teams) will work meaningful, if we could sync infos both direction smoothly.

That's I need often times some trigger from Goal to Teamwork Collection.

For more feedback please don't hesitate to mail to ahmet.kilic@teams2tech.com