Asana vs HCL Connections (formerly from IBM)

• Task Management - Being able to assign resources and time lines to specific activities
• Project Management - Being able to plan, execute and track project process using this tool
• Customizability - Being able to customize a solution that meets your needs or activity.

Read full review

• The plugin for MS Office/Explorer has made saving and sharing working documents extremely convenient for me and my close colleagues
• The newsfeed feature conveniently aggregates updates from the communities/people you follow. It's nice not to have to jump from community to community to see what's going on in the organization
• The various apps can be used for several purposes. A little creativity goes a long way when establishing what type of information the apps can be useful for communicating

Read full review

• I think there could be improved clarity around the different levels of Asana. For example, the resources available to paid accounts are not visible from the more basic accounts, so you're not aware that there are expanded options until you look in their knowledge base and see that they have additional features.
• Exporting projects - you can export a project into a csv, but it isn't pretty. This can be challenging if you'd like to have an archived project folder for open records requests.

Read full review

• The lack of a note-taking tool became a bigger and bigger issue as time went on. Our pilot users felt Connections was a natural place to take and share meeting notes – including photos, drawings, recorded audio, etc. – and were always frustrated that there was no easy, organized way to do that. We tried using a Blog, Wiki, etc. but nothing really resonated as a good solution for this.
• The Wiki tool is weak, providing rigid structure but with few options. A Community can only have a single Wiki, for instance. Wikis are weak in the mobile app as well; they’re not even easy to navigate. Users ended up ignoring Wikis completely despite our efforts to get them to convert documents like guidelines, policies, procedures, handbooks, etc. into Wiki form.
• The Windows Explorer plug-in was useful but required a lot of manual intervention to setup. For instance, once a user joins a Community in Connections, the Community also has to be manually added to the Explorer plug-in so the user can find, open and edit files with it. We felt this process should be much more automated.
• Tagging is only relevant in the web UI and, to a lesser extent, in the mobile app. However, in the Windows Explorer plug-in, Tags are not usable at all making it difficult to find things that were easy to find in the web UI.
• IBM Docs was not included in the on-premises deployment; it was an additional license so we did not test it. Documents, mainly Microsoft Office files, are still the single most common way our user community creates, shares, edits and presents information. That proved to be a major gap for our users, and slowed user adoption considerably. We considered testing it, but IBM Docs would only work for about half of our users so we found ourselves wondering if we really wanted to support two document editing platforms. IBM Docs also offers no way to work offline as far as we could tell. This also meant we would need to keep licensing Microsoft Office which is not cheap.
• Consulting costs are high because the back-end environment is complex. Installing, administrating and even patching Connections is a fairly complex process. We needed to hire consultants to install our test environment and any major upgrades would’ve required additional consulting fees. Any 3rd party add-ons we looked at were highly technical in nature meaning…you guessed it, more consulting costs.
• Administrating IBM Connections requires editing XML files in a specific, secure way that is typically done in a console. I love consoles as much as the next admin, but when you only use a console once every 2 months it means looking up all the documentation and re-educating yourself. A single change could take me 2 hours to implement. 3rd party admin dashboards do exist, at an additional cost, but IBM really should provide a much easier way to manage the environment.
• The lack of in-person or online training courses, materials, videos, etc. really discouraged a lot of users. The only decent training we could find (marketing videos aside) was a single video series on Lynda.com which, of course, was an additional cost. In the end that video didn’t really help our users much beyond introductory concepts.
• IBM includes reporting, but it’s a massive Cognos system requiring some serious hardware and Cognos expertise. We had neither, and would have ultimately opted for a 3rd party add-on for reporting and statistics.
• An often overlooked concern is eDiscovery. Our contracted eDiscovery service extensively works with various ECMs, but had no idea how they would handle Connections data. The cloud version of Connections offers an add-on for eDiscovery, but as far as we could tell IBM offered nothing for on-premises deployments.

Read full review

• Asana helps improve productivity in the workspace by ensuring all team members know what projects/tasks they need to get done and by when.
• Asana helps team members stay focused on what needs to get done and allows cross collaboration between departments which greatly increases overall company productivity by not having to wait around for email responses.
• Asana is a good tool for project management and is easy to use, making it accessible for the whole company to use.

Read full review

• Positive - Using IBM Connections has reduced the number of directories and file share repositories previously used for collaboration.
• Positive - The direction is to stop relying on email for the only method of communicating and sharing knowledge. IBM Connections is in the right step.

Read full review