Atlassian Team '25: Notes from Anaheim

I spent April 8–10 in Anaheim for Atlassian Team ’25 at the Anaheim Convention Center — three days, a few thousand practitioners, and a clear look at where collaboration and software delivery are heading next.

Why I went

I build on Atlassian and help teams level-up delivery. Team ’25 is the place to understand Atlassian’s roadmap, see real-world stories at scale, and compare approaches across cloud, Data Center, and AI-assisted workflows.

Key announcements I’m excited about

AI as a teammate (Rovo, broader availability): The “AI teammate” framing clicked. It’s less about chat, more about unlocking organizational knowledge, summarizing across tools, and assisting decisions — with traceability.
New product collections: Bundling work management and strategy tooling into opinionated collections felt pragmatic. Clearer packaging should help cross-functional teams standardize without stitching together a dozen SKUs.
Deeper Loom + Confluence + Jira moments: Short async video embedded in planning and documentation workflows is maturing. It’s a small change with outsized impact on clarity.

Taken together, the direction is obvious: streamline flow, reduce copy/paste, and surface the “why” behind work.

Favorite sessions

AI in the enterprise, responsibly: Great patterns for grounding, attribution, and guardrails when rolling out AI assistance to large audiences.
Cloud and DC transformations: Useful migration stories that covered the unglamorous parts — data classification, identity, and performance envelopes.
World‑class software delivery: Teams sharing how they’ve tightened feedback loops with better visibility from idea → deploy → measure.

Hallway track and Expo

The Expo floor delivered strong demos and honest conversations — from governance and compliance to test automation and incident response. I always learn as much in the hallway track as in the rooms, and this year was no different.

The Bash

The Beach Bash finale was peak Team: lights, music, and a lot of energised conversations about the ideas we were taking home.

What this means for my work

Designing for AI assistance: I’m leaning further into explainable outputs, source links, and opt‑in usage analytics in product flows. If AI suggests, it should also cite.
Tighter platform boundaries: Clearer module boundaries (code and org) make AI assistance safer and more useful. Good architecture compounds.
Less swivel‑chair: The integrations momentum (Jira ⇄ Confluence ⇄ Loom, and beyond) means fewer screenshots in docs and more live context. I’m prioritizing native embeds and shared components wherever possible.

Tips if you’re going next year

Book 1:1s with product teams early; they fill up.
Mix tracks — a DevOps session next to a work management talk surfaces new ideas.
Leave time for the Expo and the hallway track; they’re gold.

Anaheim delivered: real talk from practitioners, a confident platform direction, and a sharper view of how AI can actually help teams. Already looking forward to what’s next.

If you want the official overview, check the event site: Team ’25.