Are you a Team Changer? Share your story and earn a badge!

[#1]

Hi Teamwork Lab Community!

As the year draws to a close, we’re reflecting on our wins in the workplace. Oftentimes, the most rewarding part of work isn’t the work — it’s the teamwork. When we change how we collaborate, work becomes much more productive and enjoyable. From sharing knowledge and breaking down silos to making better decisions, these improvements are a Team Changer.

We want to hear about your Team Changer moments. How have you helped your teams work better together this year? Did you develop a new process or ritual? Start using an Atlassian app or feature? Change the way your team communicates? Maybe you have a team member who has inspired you.

Now’s the chance to share.

🏅 How to participate

1. Share your Success:

Comment about a Team Changer experience you’ve had this year.

Whether it's how you improved the way your team collaborates or how another team member inspired you, we want to hear your story!

Need more inspiration? Check out our latest video with Zach Woods to see how a celebrity Team Changer doesn’t always have all the answers:

2. Earn a Badge:

Every Community member who shares their story in the comments will automatically receive this special Team Changer badge:

📣 Shout out to your fellow Community members

Tag a fellow Community member you think is a Team Changer so they can share their story!

📅 Important Dates

Comment Period: December 5 - December 19, 2025

Comment, share, and celebrate your teamwork with us during this period. We can't wait to hear about your Team Changer moments to end the year on a high!

[Anahit Sukiasyan]

This year I had the chance to implement several Atlassian tools completely from scratch and onboard a team of 100+ people to start using them in their daily work. 🚀
It was incredibly rewarding to see how quickly the team adapted.

Watching these tools genuinely transform the way we work together has definitely been one of my biggest Team Changer moments of the year! 🙌

[Sean Perry]

I've migrated my team from a Confluence / Jira combination, with Scope etc. captured in Confluence and Work Progress in Jira, to just this week adopting Atlas Projects as well for the current roster of 26 Projects in order to be able to update all progress in Projects and share information with wider teams - launch is next week!

[Martin Runge]

We transformed a customer's Special Requests Management from a chaotic mix of Excel, Email, and OneNote into a streamlined 'Single Source of Truth' using Jira Service Management. By implementing dynamic intake forms and automated workflows to handle everything from duplicate checks to notifications, we are drastically reducing administrative overhead while ensuring a transparent, audit-proof communication history. Migrating the legacy data into this centralized ecosystem enabled us to utilize real-time dashboards, instantly turning what was once a reactive struggle into a proactive, data-driven strategy. This shift didn't just clean up the data; it fundamentally empowered the team to move away from firefighting and focus on delivering superior, consistent service quality.

[Haunani Nakabara]

Yesterday, we celebrated International Volunteer Day at our corporate headquarters.  I'm inspired by the excitement, energy, and passion that my colleagues brought to the volunteer event (assembling snack kits for single parents attending school and working full time).  Impactful project management brought to life!

[Tomislav Tobijas]

This year, our biggest Team Changer has been embracing Loom for onboarding both colleagues and clients to improvements, new features, and changes in Atlassian apps. The feedback has been fantastic - people genuinely love it! 🩵

My favorite moments are when users say, “Just send me a Loom” instead of “Let’s organize a meeting.” (quite proud of it actually 😅) It saves so much time, keeps everyone aligned, and makes knowledge-sharing way more accessible.

I’m also quite convinced we can get even better at it next year! 😄

[Carsten Severin _KUMAVISION AG_]

Improving workflows in work items to support existing processes and creating uniform dashboards for the company were the most significant improvements for us.

[Barbara Szczesniak]

I am basically the Atlassian monitor for my team. I get the daily digest and participate in the community, and I look through the weekly release notes for our products apps. I not only learn things myself this way, but I can bring to the attention of my teammates any announcements or new features they might need to know about.

[John Elder]

This year we (Agile Coaches at my organization) embarked on a path massively increased transparency with our teams, their processes and metrics, and their overall delivery.  This started out with some in person events and collaboration but very quickly required everyone to return to their respective teams, across three geographic locations, and begin the process of growing and practicing the things we agreed on.  Scrum ceremony event scheduling and shadowing, immediate and constructive feedback, regular 1-on-1s and coaching sessions, documented experimentation and continuous improvement efforts, and overall presentations to senior management on what the outcomes of our efforts were.  It proved to be an enormous success and we used the tools we had (Jira, Confluence) to bring that transparency to life... boards, reports, dashboards, workflows, etc. all contributed to the establishment of a system that will ensure reliable and quality delivery going forward for these teams.  We impacted technical processes as well as team culture... 2025 was a good year for teams in our org.

[Rinjini Poddar]

Enabling the team to use the tools effectively while also identifying and recommending the right plugins to ensure smooth and successful retrospectives.

[Crystal Stauber]

This year I was able to help train a new employee, mentor a colleague, and implement a new intake process to streamline requests from other departments.

[Anwesha Pan _TCS_]

This year we embraced using Rovo in Confluence which is a big Team changer for our team.🎓 We were also able to organize and clean up our Confluence Knowledge Base wiki using newly added macros and features got available this year for which we received ample feedback! 📈 Thanks Atlassian! 😀

Loom is next on our list which we mostly be implementing next year. ✨

[Thorsten Letschert _Decadis AG_]

Rolling out Loom across our different teams has genuinely transformed the way we communicate. Taking our app development as an example, instead of writing long explanations or documenting every new feature step-by-step, we now share quick videos that show updates in motion. It’s faster, clearer, and far more engaging.

What surprised me most: the ripple effect. teammates can react instantly with emojis or drop comments right on the timeline, which has made feedback loops shorter and alignment much easier.

For us, this shift didn’t just boost efficiency - it strengthened collaboration and made knowledge sharing feel more natural. Definitely a “Team Changer” this year.

[James O_Connor]

This year, I took over ownership of the Atlassian platform at my organisation, and started several initiatives to improve our usage of the tools including creating a centralised knowledge hub for both users and admins, organising training for different user groups, and standardising practices across the admin team. I also got rid of several plug-ins that had been hanging around unused for years and used the spare cash to get us upgraded to Premium, which has made a big difference across how we use the tools.

[Megan Osifeso]

Our team has recently transitioned to Atlassian Jira AND Confluence and I'm inspired every day by everyone's willingness to adapt to change.

[Cornelia Jeppsson]

I just ended the year with having one of our teams which is a part of the org that hasn't ever worked in Jira take a step from managing their project in an Excel sheet (!!) to getting a Jira Space set up for them within a minute (I think it took even less to set up, thanks to using a template). Also, we are rolling out Loom to our organization in just a few days after months of going through all the compliance/legal/security/etc reviews - so so excited to see how this will transform the way we work during next year (For myself, I am definitely hoping for less meetings and I have so many ideas of how-to-guides that I need to record!)

[Stephen_Lugton]

Our big challenge with Jira this year has been working with a partner company where we want to share some but not all of our work items (to be fair it was mostly them wanting to use a single space for both internal and customer facing items). We achieved this using an addon Exalate.

After the initial teething problems (the documentation says if you have this problem do THIS, which then caused another problem, for which the documentation if you have this problem says don't do THIS) we were able to work more closely with the partner company.

Since then other parts of the business have been coming to me saying "that Jira thingy you did worked really well, can you do something in Jira for us?"

The answer was yes, and we now have other teams using Jira and discarding Excel (except for Finance, they just made a bigger excel spreadsheet!)

[Amanda Barber]

Thankfully, the non-profit discount has allowed my team to start using the Teamwork Collection this year. In the past month, I've seen so much Loom use to prevent the need for asking, "can you hop on a call?" and for recording meetings! We're excited to continue to build out our internal knowledge in Confluence, while we continue to use Jira to track work - both for software development and other teams!

[Okan Erdogan]

This year, one of my biggest “team changer” moments was shifting our teams from tribal knowledge to shared ownership using Confluence.

We introduced lightweight but structured documentation habits:

• Clear “why / what / decision” sections instead of wall-of-text pages
• One source of truth per process (no more Slack/Teams archaeology)
• Documentation as part of delivery, not an afterthought

The result? Fewer handover gaps, faster onboarding, and much better async collaboration across time zones. Decisions didn’t live in people’s heads anymore—they lived where the team could actually use them.

It wasn’t about writing more docs. It was about helping the team work with more clarity, confidence, and autonomy!

[Julie Kremp]

This year, I helped our team work better together by designing and implementing three specialized Rovo Agents: the Legal Agent, the Privacy Agent, and the Vendor Questionnaires Agent.

Legal Agent: To streamline our legal processes, I introduced the Legal Agent, which automates the retrieval and sharing of legal templates, policies, and FAQs. This agent has made it much easier for team members to access up-to-date legal information, reducing bottlenecks and enabling faster, more confident decision-making.

Privacy Agent:Recognizing the growing importance of data privacy, I developed the Privacy Agent to centralize privacy guidelines, answer compliance questions, and guide the team through privacy-related workflows. This agent has empowered everyone to handle sensitive data responsibly and stay aligned with regulatory requirements, all while minimizing the need for back-and-forth with our privacy experts.

Vendor Questionnaires Agent: Vendor assessments used to be a time-consuming process, often involving repetitive manual work. With the Vendor Questionnaires Agent, I automated the collection, tracking, and initial review of vendor security and compliance questionnaires. This not only sped up our vendor onboarding but also improved accuracy and transparency across teams.

By introducing these three Rovo Agents, I’ve helped our team communicate more efficiently, reduce manual workload, and foster a culture of proactive knowledge sharing. The agents have become trusted digital teammates, allowing us to focus on higher-value work and collaborate more effectively across departments.

I’m proud to have contributed to making our workflows smoother and our team more connected.

[Salman Shaikh]

During a digital transformation project, I worked with a client who was struggling with disconnected tools and unclear delivery processes. Teams relied on emails and spreadsheets, making releases and hotfixes difficult to manage.

I helped implement Atlassian tools in a practical way that matched how teams actually worked. Jira was set up as a single place to track work, with simple workflows for epics, releases, and hotfixes. We also aligned these workflows with scaled Agile practices so multiple teams could plan and deliver together. Confluence was introduced for documentation and release notes.

The impact was clear. Releases became more predictable, hotfixes easier to track, and teams collaborated better with shared visibility. Seeing teams move from frustration to confidence is what made this a true Team Changer experience for me.

[Shazia Rahman]

These days as a Team Changer and Atlassian Community member had participated in the testing of the tools and improvised it and made my AI journey more thorough. And also participated in feedbacks for the sessions.

[Margherita Mancuso]

Running Jira workshops focused on WIP limits and flow phases. By helping teams visualize their work, define clear phases, and limit WIP, we improved focus, flow, and cross-team collaboration. Jira became a shared language for how work really moves, not just a board. 👊

[Bjorn Bartlett]

Over the last few months, I've been introducing various ways of using Rovo to support my Support team.

We focused on a few concrete problems:

• Ticket summaries that are too vague or inconsistent
• Tickets that are hard for our teams to triage
• Repeating the same manual steps every week for reporting

So we now use Rovo in Jira automation for a few targeted workflows:

• Checking and improving summaries/titles on new incoming tickets
• Adding a clear internal summary when a ticket is resolved
• Weekly ticket digests and activity summaries

The way our Support team uses Rovo has been documented in our internal Confluence 'University' for the benefit of the entire organisation.