Atlassian’s Most Controversial Growth Decision | Mike Cannon-Brookes

Summary

• Atlassian’s addressable market extends far beyond developer tooling: more than half its users have no technical job function. Cannon-Brookes’s category definition is deliberate: “We solve people problems. We don’t solve technical problems.” Jira evolved from a 2002 bug tracker into an issue tracker, road-mapping system, and broad workflow engine connecting technical teams with finance, HR, sales, marketing, and other business teams.
• Cannon-Brookes expects AI to compress business processes, not make workflow software disappear. Agents will remove individual boxes and branches from a flowchart, but their files, links, comments, and outputs still re-enter processes for review, approval, or further automation. His counter-consensus call: AI is “an accelerant, not a replacement.”
• The strategic asset beneath Rovo is a permission-aware “teamwork graph” containing more than 100 billion objects and connections, growing north of 50% quarter on quarter. Built since 2019 from links spanning Atlassian products and external SaaS applications, it powers enterprise search, context, ranking, and agent actions. More than 3.5 million people were already using Atlassian AI features monthly: “We don’t want to market AI; we want to ship it.”
• AI is clearly increasing task-to-code speed, but Atlassian refuses to equate faster code generation with customer value or even realized productivity. Coding consumes roughly one-third of a developer’s week, while generated code shifts effort into rebuilding mental models and reviewing output. With token-heavy tools potentially costing thousands of dollars per developer and tens of millions annually across Atlassian, DX combines quantitative delivery metrics with qualitative surveys to find actual ROI.
• Atlassian’s application-layer strategy is to supply context and select models rather than bet the product on one model vendor. Its production AI gateway runs north of 75 models, and Rovo Dev may use two or three on a typical task, including Claude Code or Gemini. A notable internal use case was not greenfield creation but an API change across more than 500 repositories—“mowing the lawn” at scale so engineers can return to “landscape architecture.”
• Cannon-Brookes rejects both mass developer displacement and the idea that only senior engineers will remain employable. He expects Atlassian to employ more developers in five years, with a continuing economic case for pairing one senior with four or five less-experienced engineers whose output AI can amplify. Accountability remains human: whoever commits or approves code owns it, regardless of whether Rovo Dev, Cursor, Claude Code, or GitHub Copilot produced it.
• The operating doctrine is “grow longer, not grow faster,” even as Atlassian reported roughly 21% revenue growth, 26% cloud growth, and 40% RPO growth. Cannon-Brookes wants durable growth north of 20%–30% five years out, not a quarter optimized by spending every available dollar on immediate revenue. His investor-relevant test is whether the company is seeding future demand or merely harvesting yesterday’s work until “the fields are barren.”

Deep dive

Not yet available upstream; scheduled sync will retry.