Item: Atlassian Confluence
Rating: 8
Author: Verified User

Overall Satisfaction with Atlassian Confluence

Use Cases and Deployment Scope

Atlassian Confluence used for documentation between Engg + Product. In our organization, we use it for RCAs, Tech Specs etc. It helps centralize information streamline communication across teams. Features like page hierarchy, templates, and permission controls make it useful for documentation, while its search functionality for easy access to information.

However, Atlassian Confluence has some drawbacks. Performance can be slow, especially with large pages, and its real-time collaboration isn’t as great as Google Docs. The product is a little more complex for new users and Google Docs tends to become a lot more welcoming.

Pros and Cons

Pros

Integration with JIRA. Hence, Devs and TPMs rely a lot more on Atlassian Confluence as compared to marketing teams.
The AI integration can become actually very powerful where new members of the team can navigate across documents.
Templates for regular documentation.

Cons

The AI suggestion sometimes goes haywire as of now. I noticed some of the suggestions sent me to unrelated documents.
The FTUE is not so great. Especially if you do not know. a feature, it becomes tricky.
It would be really helpful to have a diagramming integration as lot of documents need flowcharts.

Return on Investment

The AI feature which lets me find relevant documents while reading one document is really beneficial.
Centralising of knowledge systems is one of the key differentiators for large organisations.
As long as folks keep using Google Docs and Atlassian Confluence, there is going to be a challenge in building a continuum.

Usability

Atlassian Confluence offers a robust platform for documentation and long-term retention. Strengths: Search, Tagging, AI Recommendation is indeed very good. Quickly finds relevant documents, even in large repositories, Can be seamlessly integrated with JIRA. Real-time collaboration is not so great. Similarly, the features offered by Google Docs often appears more appealing.

Alternatives Considered

Notion

Organisations might have chosen to Procure Atlassian Confluence because JIRA is integral to software development. Notion or Google Docs do not work seamlessly with JIRA. Also, Atlassian Confluence has a much higher perceived seriousness about a document as compared to Google Docs. This could me in the minds of the user but Atlassian Confluence Docs are often taken a lot more seriously than Google Docs.

Key Insights

Do you think Atlassian Confluence delivers good value for the price?

Not sure

Are you happy with Atlassian Confluence's feature set?

Yes

Did Atlassian Confluence live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Atlassian Confluence go as expected?

I wasn't involved with the implementation phase

Would you buy Atlassian Confluence again?

Yes

Other Software Used

Atlassian Jira, Slack, Miro

Likelihood to Recommend

Great for Long Term Documentation, JIRA integration, Version Control Etc. The integration with Slack too is pretty good. Not So Great for , Real TIme editing, documents having media, integration with email etc. Especially problematic is the real time editing of documents by team members. Google Docs is a lot more versatile when we are capturing feedback from numerous stakeholders at the same time.

Confluence Feature Ratings

Comments

Please log in to join the conversation

Great for Engineering Teams!