The CAB is made up of seven Community Champions representing different community cohorts, including Atlassian Marketplace Partners, Atlassian Solutions Partners, Atlassian Community Event organizers, forum contributors, and content creators.
We also held our annual CAB Breakfast at Team '25 Anaheim, which is always a highlight of our time together at the event:
CAB Members at Team '25 Anaheim
Major Themes from 2025
Raising the bar for champions (and making it sustainable)
CAB spent a lot of time on who becomes a Champion, what’s expected, and how we recognize customers and partners, discussing:
-
Clearer, stronger requirements for new Champions, especially around consistent event and community engagement
-
A more deliberate selection process for Forum Champions (with an emphasis on tone, helpfulness, and stewardship)
-
Flexibility to allow Champions to specialize or hone in on a particular skill —for example, focusing on events, forums, content—alongside room for those who want to dabble in different activities
The direction: fewer surprises, more clarity, and more room to lean into the kind of contribution you’re Champions are energized by.
Events: Less decks, more depth
If you’ve ever thought “this talk feels familiar,” you’re not alone.
CAB gave strong feedback that many Atlassian‑led sessions at events like Team on Tour and RovoCon felt too slide‑heavy and too similar across cities. In response, they pushed for:
-
More deep‑dive technical content (not just high‑level overviews)
-
A clearer difference between Team on Tour, RovoCon, ACEs, and other formats, so each has a distinct purpose
-
More AMAs, fireside chats, and “bring your problem” sessions, where the bulk of time is spent in conversation and Q&A
-
More customer and Champion speakers, fewer recycled keynotes
If you’re craving more live problem‑solving and fewer generic decks, CAB very much agrees with you—and is pushing us in that direction.
Making the program make sense as it grows
As the community grows, especially in large markets and online, CAB spent time on program structure:
-
How to handle multi‑chapter cities without stepping on toes
-
How virtual chapters can coexist with local chapters, so they complement rather than compete
-
How to make co‑hosted events (across cities, with partners, or both) feel relevant and well‑run
The direction: a more specialized, well‑coordinated community of chapters, not a confusing tangle of overlapping events.
Guardrails for Partners and Speakers
CAB strongly reinforced something most community members feel instinctively: events should feel like community, not commercials.
That led to ongoing work on:
-
Clear partner guidelines at ACEs—how partners can add value without turning sessions into sales pitches
-
Improving speaker quality through training and light‑touch feedback, so attendees get more consistent, high‑quality content
Expect an ongoing push toward sessions that teach, demo, and problem‑solve first, and only sell if and when it genuinely helps.
Stronger bridges to Product and R&D
Champions often act as a bridge between the Community and product teams. CAB leaned into that role in 2025 by pushing for:
-
Better internal playbooks that show PMs and engineers how to work with Champions and community members (AMAs, betas, early feedback loops, etc.)
-
Using async formats (like Loom videos) for one‑way updates, and saving live time for Q&A and real conversation
-
Less scattered feature communication, and more tied‑together, digestible updates the community can actually use
You should see more chances to talk directly with product owners, and more context shared through Champions and community spaces—not just during launches.
Why this matters (and how you can plug in)
Even if you’re brand new to the Atlassian Community, the topics they hammered on in 2025 are all about your experience:
-
Better events (more technical, more interactive, less repetitive)
-
Clearer paths into leadership and recognition
-
Stronger connections to product and R&D
-
A community that scales without losing its soul
If you want to shape what CAB talks about next:
-
Tell your local CAB member what’s working and what’s not
-
Share patterns you’re seeing (e.g., “talks feel repetitive,” “not enough deep‑dive content,” “confusing overlap between events”)
-
Think about where you want to contribute—events, forums, content, mentoring, or product feedback
Those themes are exactly the kind of input the CAB has the opportunity to turn into action through the feedback they provide the Atlassian Community team.
A huge thank you to the CAB
None of this work happens by accident.
CAB members volunteer their time to give hard feedback, share what they’re hearing on the ground, and push Atlassian to do better for the broader community. That often means late‑night calls across time zones, thoughtful follow‑up notes, and a lot of invisible emotional labor on behalf of other community members.
To everyone who served on the CAB in 2025: thank you. Your candor, persistence, and care for this community directly shaped the improvements above—and will continue to shape what we build next.
Your 2025 CAB representatives as of February 2026 are:
Interested in joining the CAB? Speak with your Community Manager!
To learn more about the Atlassian Champions program or to apply, visit this page.
![Photo of Huwen Arnone [Deiser/Devoteam]](https://us.v-cdn.net/6038660/uploads/avatars/6f/bc/n6fbcb837e47ed9842db045142dbc9275.png)
