Nuclino vs. Project Insight

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

Incentivized

My rating would vary depending on the types of projects that need to be managed. Since I am in software, I don't think it was an excellent fit to manage software projects unless they are small projects with only a few tasks. On the other hand, if you are needing to manage a wide range of departments that are working on a single project with many moving pieces, then I would think that PI might be a better fit. Think of it as a jack of all trades, but master of none.

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

• History tracking for any changes made to data.
• Tracks all milestones and retains records for lifetime of account.
• Easy extracting for reporting purposes.

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

• Not a good fit for all types of projects
• Very Complex

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

I found Project Insight somewhat opaque overall. I thought the training was sparse and answers to questions few and far in between. There was a lot of power there for the dedicated user/administrator. For me, who was a casual user and administrator, I found support lacking. I didn't administer Project Insight much, just some work on integrations with other tools.

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

• When I got to the company where I used Project Insight, we had our own custom tool that fit the tasks that it was designed for but wouldn't grow with the company unless resources were put onto expanding capabilities. We needed something more.
• We replaced that tool with Redmine. It worked well and was easy to use, but it looked pretty dated when we got it, and since we didn't have many resources for managing, it looked dated after a few years without receiving upgrades. It was a decent tool for small teams that were focused on similar tasks. Redmine was much more straightforward than Project Insight and felt more reliable since we never had an issue with our internal servers. On the other hand, Redmine felt dated and didn't fit as many of the tasks that were needed. Redmine's price was right if you installed it locally and was probably still cheaper if you used their SAAS version.
• Jira, on the other hand, felt like an excellent tool for software teams. Jira had a great project and task management and felt right for a software team. Jira also had useful integrations, even with Project Insight. Jira seemed pretty unreliable, worse than Project Insight. Our team would have preferred Jira, but I think it didn't work for other teams.

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

• Reduction in costs on materials (i.e. - paper documentation)
• Improved efficiency given that our field members need to report back on an hourly basis
• Web based platform allows anyone access to the same information

Incentivized