Actionspace vs. Nuclino

When you have many projects with different people on them Actionspace is well suited to handle that

Incentivized

Nuclino is suitable for just about any company. It is intuitive and helps keep any company organized.

Incentivized

• User customization for each individual and their responsibilities
• Great support staff and update capabilities
• You can see the early stages of the project and see it through in a clean and organized way

Incentivized

• Workspaces are helpful to segment information.
• Being able to download files directly from Nuclino is useful.
• Having the ability to link to external docs is useful.

Incentivized

• Sometimes anyone who has touched a project still receive notification even if they don't need it
• Having to manually enter information from other areas

Incentivized

• No real offline use is possible.
• For small teams it's ok, but pricing is too high if lots of employees need to work with it.

Incentivized

I love Nuclino's usability. The layout is clean, simple, easy to follow, and bright. I like that there is a read-only account option so that less-tech savvy people can still use it and they won't need to worry about deleting key information from the database. Similarly, I like the features that allow multiple contributors to have the same features to edit.

Incentivized

The Nuclino knowledge base is good. Most answers to your questions can be found there. I didn't need to contact support at all.

Incentivized

Nuclino is the clear winner when it comes to ease of use for both the administrator and user. Less setup time and less "training" time. The streamlined interface is quick and intuitive to learn and is not cluttered as compared to Confluence. Every tool you need to use to create a page or administer the workspace is available immediately on screen or by right-clicking. In contrast, Confluence buries many tools in administrative interfaces and only allows use of some features once you make several clicks to include a "macro" or "plug-in". We use both tools and I get complaints constantly from my team about how complicated Confluence can get just to author a quick page.

Incentivized

• Having a central documentation allowed users to find data more quickly, which resulted in 50% less "question" type bugs that would appear in our queue.
• Collaborating documentation before development resulted in less bugs; this is part process but the ease of sharing and making related documentation easy to access encouraged users into adapting the process.
• Increased use in documentation allows support response time to be higher for triage since supporting documentation is ready to go.

Incentivized