Something that has been on my mind lately is a bit of a contradiction I’ve occasionally noticed within the Atlassian ecosystem.
The ecosystem itself thrives on integrations, extensions, and building tools that help teams work more efficiently. The whole idea is enabling better workflows, smarter automation, and new ways of working on top of the platform.
But when people start using tools like Rovo to improve their daily work, the reaction isn’t always curiosity or support. Sometimes it feels more like subtle hesitation as if relying on a tool like that means you’re not really doing your job properly.
And that’s where the irony comes in.
Rovo is meant to help people find information faster, connect knowledge across tools like Jira and Confluence, and reduce the time spent searching through documentation or switching contexts. In theory, it supports exactly the kind of productivity and efficiency that the Atlassian ecosystem promotes.
Yet the perception can sometimes be that using an AI assistant is “taking shortcuts.” Instead of being seen as someone optimizing their workflow, it can feel like the assumption is that the work isn’t being done properly if AI is involved.
Of course, some caution makes sense. AI tools bring real questions about data governance, accuracy, and responsible use. Being thoughtful about how these tools are used is important.
Still, viewing the use of these tools negatively can feel like a cultural mismatch. In an ecosystem that celebrates building better tools and improving how teams work, using those tools effectively should be seen as a strength rather than a weakness.
Otherwise, it creates a strange contradiction: promoting smarter ways of working externally, while certain environments in the ecosystem may be hesitant about using the same tools internally.
Curious if others have experienced something similar. Have you ever felt like using tools like Rovo was seen as “not doing the work properly”? 🤔
