Atlassian Confluence vs. FigJam

I would recommend Atlassian Confluence for companies that want to have internal documentation and minimum governance processes to ensure documentation is useful and doesn't have a lot of duplicated and non-updated content. I wouldn't recommend Atlassian Confluence for companies with a low budget since this product might be a little costly (especially with add-ons).

Incentivized

If you're working in small product teams, like triads, and already using Figma, this is a no brainer for white boarding, quick/fast sketches, wireframing, collaborative doodling ... it gets less appropriate with large teams, infrequent. IMO, due to the way in which they price, it's better to keep the inner circle small-ish.

Incentivized

• Cross product linking - If you use other Atlassian products then Atlassian Confluence is a no-brainer for your source of documentation, knowledge management etc. You can show previews of the linked asset natively E.g. showing a preview of a JIRA ticket in a Atlassian Confluence page.
• Simple editing - Though the features available may not be super complex right now, this does come with the benefit of making it easy to edit and create documents. Some documentation editors can be overwhelming, Atlassian Confluence is simple and intuitive.
• Native marketplace - If you want to install add-ons to your Atlassian Confluence space it's really easy. Admins can explore the Atlassian marketplace natively and install them to your instance in a few clicks. You can customise your Atlassian Confluence instance in many different ways using add-ons.

Incentivized

• One file, auto updated, no need to get latest
• Easy to preview
• Lack of client is benefit to some (not me)

Incentivized

• UI Design is very simplistic and basic could make use of more visually interesting colour choices, layout choices, etc.
• Under the 'Content' menu, it defaults to having a landing page for all L1 and L2 category pages. Meaning as long as the broader content category has a sub-category, it still creates a separate landing page. In my team's case, this often creates blank pages, as we only fill out the page at the lowest sub-category (L3).
• Hyperlinks are traditionally shown as blue, however, this results into very monotonously blue pages in cases where a lot of information is being linked.

Incentivized

• It misses easy-to-use pre sets of diagrams. The ones presented seem to be not native and hard to use. Miro is a good benchmark.
• Navegating throught projects in the main page is confusing, specially when people are not admin users.
• It should suggest ways of organizing the pages designers do, specially when the project is big and have many pages and sections.
• It could have, for example, a draft version for every page, so that one can hide it when they finish the work, but can open it whenever something needs to be modified, versioning the job.

I am confident that Atlassian can come with additional and innovative macros and functions to add value to Confluence. In 6 months, Atlassian transformed a good collaborative tools into a more comprehensive system that can help manage projects and processes, as well as "talk" with other Atlassian products like Jira. We are in fact learning more about Jira to evaluate a possible fit to complement our tool box.

Great for organizing knowledge in a hierarchical format. Seamless for engineering and product teams managing software development. Helps in formatting pages effectively, reducing manual work. Tracks changes well and allows for easy rollbacks. Granular controls for who can view/edit pages. Search function is not great which needs improvement. Hire some google engineers

Incentivized

I don't use it often, because the organization I work in uses a different environment on a commo basis. This is rather used between the designers, who prototype the solutions in Figma - they just have it as a workbook/notebook for their ideas. However, if those need to be shared with stakeholders or other organization members, the designers are expected to use a different environment.

Incentivized

I do not recall having outages or applications error so far, very reliable and available.

Incentivized

We never worked against the tide while using Confluence. Everything loads considerably fast, even media components like videos (hosted on the platform or embed external videos from Youtube, for example). We are not using heavy media components a lot, but in the rare occasion we happen to use one we have no problems whatsoever.

Incentivized

This rating is specifically for Atlassian's self-help documentation on their website. Often times, it is not robust enough to cover a complex usage of one of their features. Frequently, you can find an answer on the web, but not from Atlassian. Instead, it is usually at a power user group elsewhere on the net.

Incentivized

Overall, I am very satisfied with the initial implementation (and the subsequent upgrades and implementations made over the years).

This product has never rose to the level of being an major issue at an executive level. It has quietly and valiantly done it's job for our company!

Incentivized

We chose Atlassian Confluence over SharePoint because it's much more user-friendly and intuitive. Atlassian Confluence makes collaboration and knowledge sharing easier with its simpler interface and better search. While SharePoint can be powerful, it often feels clunky and complex, making it harder for our team to actually use it.

Incentivized

FigJam works best in pair with Figma, as it allows you to keep track of your project in one place, supporting all phases of the process. The functionality is more intuitive, quick, and efficient. Visually, I also prefer it more —it’s more enjoyable and playful, making the experience much more engaging.

Incentivized

This tool is very adaptable. So much so we use it for three completely separate projects, in three very different ways.

Incentivized

• 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.

Incentivized

• FigJam saves a lot of time ... it's nice to have all my visual notes/sketches within Figma itself where a lot of design work lives
• The project organization and other features contribute to the ease of answering that age old question ... "where can I find that mockup?"
• Dev Mode is pretty cool. Not many use it, so some designers may spend unnecessary time spec'ing out things that no one will appreciate, let alone look at.

Incentivized