Is Jira dead? đź’€
Â
Not quite, but its role as the flagship Atlassian product is slipping away fast in the System of Work.
Â
For years, we repeated as a mantra: 'It ain't work if it's not in Jira.'
But work isn't the tickets.
It's documents, data, decisions, discussions, and war rooms.
Â
Tickets are a structured record of something that needs to happen: who, what, and when.
What's actually done (deliverables), how it's done (processes), and what it's done to the business (outcomes) most often live elsewhere.
Â
Moving cards on a board from left to right is one of the most mundane and boring things to do at work.
I do a lot of it as a marketing leader, and I see it all the time:
❌ teams forget to update their work items or don't want to do it at all
❌ leadership doesn't even want to log in and throw email notifications into spam
Â
Today, 50% of Atlassian platform users are in finance, HR, marketing, and other non-technical teams.
We're working in a content-based world, not a database with 5,000 custom fields.
Conversational and voice interfaces. Rich media documents. Tables and spreadsheets that update themselves.
Is there an AI agent that could create, track, and resolve work items on our behalf based on what we share in other connected tools?
Please 🙏
Â
I already know I'm not alone with this.
@Sarah Wright and @Rodney Nissen pointed out the antipattern of overloading Jira with information that belongs better on a Confluence page during our recent discussion on The Jira Life podcast.
In the comments under my latest LinkedIn post on the topic, prominent Ecosystem people acknowledged a broader sentiment towards Confluence.
Many customers I've interviewed reported having more Confluence seats than Jira seats across their orgs.
Â
But maybe we're all wrong 🤷‍♂️
So let's continue talking about this.
Â
Where does work happen in your org today?
Where does it get shared, discussed, and become actionable?
Where do you think the future of work is?