Confluence vs Lucidspark

• QUICK How-to Guides that can be generated and share instantly
• One can subscribe to the pages and spaces and receive updates in the feed on their home page
• Automatic Email notifications of new updates in the Confluence area
• The platform integrates easily with other Atlassian platforms including third-party apps thus improving its reliability

Read full review

• Intuitive and simple design is one of its strong points, so zero learning curve!
• Clearing away the whole board or parts of the board is a breeze to avoid confusion.
• The different pens with colors and nib thickness allow easy explanations.

Read full review

• Navigation. Similar to other Atlassian products, users have complained that aspects of Confluence are difficult to learn right away[.]
• An issue that users can face when using Confluence is attempting to edit a document while someone else is editing. Although users can access the document and save it, they are unable to see the changes happening in [real-time] that other users are implementing until they refresh their page. Some users have also noted that this can result in loss of edits.
• Another drawback of using Confluence is its specific organizational structure. All information is stored within one page or project, although the page is able to be broken up into sections, some users do not prefer this style. Users can use the ‘page tree’ on each page to organize the different elements of each project.

Read full review

• CSV export of Lucidspark board cannot be imported into another board.
• I cannot import contents from Miro (or other tools) to import my whiteboards from other tools into Lucidspark.
• JIRA integration was clunky and I accidentally created 16 cards in JIRA without realizing it. All selected items in a flow chart became separate JIRA stories, which was surprising.

Read full review

• We've gone from folders and folders of Word documents and PDFs into a single system with a search feature to bring all of our data together and trackable
• While onboarding took a bit longer for the company (to switch from a Word document centric mindset - to a web-based one), overall the company has embraced the features and power of Confluence within the working stack
• However, as costs continue to climb for the Atlassian product, we are forced to continue our evaluation of the product - with replacing it a remote possibility if it begins to outprice its usefulness to us.

Read full review

• I've made a Planning Poker template in Lucid that we use for Sprint Planning, and it's made it easier to switch to Story Points and forego task breakdown and time estimation altogether. It does save time during Sprint Planning but that's less significant than the fact that developers no longer feel the need or pressure to conform to whatever random time estimate was provided. That's thanks to Story Points, not Lucid itself, but Lucid surely made Planning Poker a lot easier than it used to be. As an added bonus, it stores voting history, so we can go back during the Retrospective and review particular items of interest that we completely botched the sizing of.

Read full review