Atlassian on AI Agents, Teamwork Graph, and the Future of Work

What if the biggest barrier to successful AI isn't the model itself, but the lack of context behind every decision your teams make? As AI agents become more capable, how do organisations ensure they understand the people, projects, documentation, and history that shape real work?

In this episode of Tech Talks Daily, recorded at Team '26, I'm joined by Taroon Mandhana, CTO of AI and Teamwork at Atlassian. His responsibilities span engineering for products including Jira, Confluence, Loom, and Trello, alongside the company's AI strategy and the development of Rovo. Our conversation explores why Atlassian believes AI should become a teammate rather than simply another chatbot.

Taroon explains why enterprise context has become one of the most valuable assets in the AI era. While today's foundation models continue to improve at an incredible pace, they still lack the organisational knowledge that human teams naturally accumulate over time. Atlassian's Teamwork Graph aims to bridge that gap by connecting people, projects, documentation, code, goals, and conversations into a living knowledge network that AI agents can use to produce more accurate, relevant outcomes.

We also discuss why Atlassian has chosen an open approach, making its Teamwork Graph available through technologies such as MCP rather than limiting it to its own AI products. Taroon shares why interoperability will become increasingly important as businesses adopt multiple AI platforms and why organisations should be free to use the agents that best suit their needs without losing access to valuable business context.

Another fascinating part of our conversation focuses on how Atlassian's own engineering teams are changing the way they build software. Smaller teams, tighter collaboration, AI-assisted development, and faster iteration cycles are allowing products to move from concept to release in weeks rather than months. Taroon explains how AI is changing both software development and the structure of engineering teams themselves.

We also examine where AI should take ownership of work inside platforms like Jira, where human judgement remains essential, and why successful organisations are treating AI adoption as an ongoing product journey rather than a one-time technology deployment.

If your business is looking beyond isolated AI experiments and wondering how to build AI into everyday work, this conversation offers valuable insight into the role context, openness, and organisational change will play in the next generation of enterprise software.

As AI becomes part of every workflow, what do you think will become the real competitive advantage: better models, or better organisational knowledge?