Connections from HCL Technologies (formerly from IBM, acquired by HCL in 2018) is a collaboration tool and employee digital workspace with key features like social analytics, blogs, document management, and a social network.
N/A
Trello
Score 8.4 out of 10
N/A
Trello from Atlassian is a project management tool based on a Kanban framework. Trello is ideal for task-management in a to-do list format. It supports sharing boards and cards across users or teams. The product offers a free version, and paid versions add greater automation, collaboration, and administrative control.
$6
per month per user
Pricing
HCL Connections
Trello
Editions & Modules
No answers on this topic
Standard
$6
per month per user
Premium
$12.50
per month per user
Enterprise
$17.50
per month per user
Free
Forever Free
Offerings
Pricing Offerings
HCL Connections
Trello
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
A discount is offered for annual billing and for larger numbers of users.
More Pricing Information
Community Pulse
HCL Connections
Trello
Features
HCL Connections
Trello
Project Management
Comparison of Project Management features of Product A and Product B
HCL Connections
-
Ratings
Trello
8.5
222 Ratings
9% above category average
Task Management
00 Ratings
9.5222 Ratings
Resource Management
00 Ratings
9.3185 Ratings
Gantt Charts
00 Ratings
7.173 Ratings
Scheduling
00 Ratings
9.1168 Ratings
Workflow Automation
00 Ratings
8.2142 Ratings
Team Collaboration
00 Ratings
9.0218 Ratings
Support for Agile Methodology
00 Ratings
8.9147 Ratings
Support for Waterfall Methodology
00 Ratings
7.6115 Ratings
Document Management
00 Ratings
8.2159 Ratings
Email integration
00 Ratings
7.6146 Ratings
Mobile Access
00 Ratings
9.1192 Ratings
Timesheet Tracking
00 Ratings
9.388 Ratings
Change request and Case Management
00 Ratings
8.8102 Ratings
Budget and Expense Management
00 Ratings
7.673 Ratings
Professional Services Automation
Comparison of Professional Services Automation features of Product A and Product B
IBM Connections is well suited for larger organizations that need an internal social networking tool and are willing to deal with IBM and the complexity of the software. It is less appropriate for smaller organizations and those who don't want to deal with the complexity, or IBM's awful customer service and prices.
For teams or individuals with lots of individual tasks/details to track, Trello is perfect! It basically removes the need for a paper checklist. For those that need an overall project management tool that requires less tasks and more overarching goals, collaboration amongst various teams, and gantt charts I would suggest monday.com
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
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.
Connections has continued to more than meet our needs from a collaboration point of view and we are currently working on integration with our IBM Websphere portal platform to provide an integrated collaboration solution. This scenario will provide our users the best both products have to offer in a single interface.
I am very likely to renew Trello, because it doesn't cost anything to do so. I am also very likely to use Trello's upgraded features in the future because a lot of my team's data is stored on there and they have already gotten used to the platform. Trello is very easy for new team members to pick up, making the onboarding and usability very streamlined.
Connections combines all the most useful abilities from various social networks. This makes it useful of course, but it also reduces user adoption time initially by allowing users to get comfortable with basic features. Once they are comfortable, it's easy for users to start exploring. They find new people in the organization to contact, new sources of information, etc. Before you know it, about half of the users are contributing back in some form -- and all with little or no training needed by IT.
Trello is incredibly intuitive, both on desktop and mobile right away. It is also full of helpful features that make it even easier to use, and is flexible enough to suit almost any organizational need. Onboarding for the software is thorough, but concise, and the service is frequently updated with even more QOL improvements.
Once Connections was installed, patched, etc. it was ALWAYS up. We only had to bring it down for OS updates to the servers. That seems to be typical of anything that runs on WebSphere; it's bulletproof and could probably run for months and years if the underlying OS didn't require constant patching.
IBM Connections web UI, mobile app (data sync to / from the device), and file transfer speeds were almost always very fast. It was rare for a slow-down of any kind, even when doing searches.
IBM Support has ALWAYS been quick to respond, regardless of the product. Even first level techs seldom provide "canned" responses and they really try to help. If they can't help, they don't wallow around but engage the right person immediately. It's very rare that the first level tech needs to escalate, and even more rare when they do escalate and the next person engaged cannot solve it. We have been more than satisfied with IBM support's quick and professional responses to our issues.
I haven't reached out to their support very often and their support is very limited anyway for the free users. They do have tons of great articles and videos in their Help Center and constantly send emails with updates and add-ons to the product. The fact that I've barely ever had to contact their support team means that they've developed a great product.
Try to understand you will never find a product which suites all your end user for 100%. IBM Connections is the best of all breeds but if you go look on each functionality on its own there are better example out there. But as IBM COnnections delivers it all in just one platform makes it the best example about integration of different functionality into one platform.
For our small business, getting a few of us started well on Trello was the key, I think. As long as a couple of us were really comfortable with the interface, we could lead others and help them with any questions. From now on, anyone who works with us just naturally uses Trello for information sharing - it's just part of what we do.
From the few times that I have used MS SharePoint, I can say that it doesn't seem to hold a candle to the robust features of IBM Connections. The out-of-the-box capabilities of IBM Connections are amazing and are more easy to access and use than what I've seen with MS SharePoint.
Trello is more simple and not as "robust" as the other tools, but it's easier to use and manage and understand and ACTUALLY get stuff done with. It's simplicity is part of the beauty of using it. You don't need a million options that nobody uses, you just need to get stuff done.
Scaling UP is never an issue with IBM's core technologies like WebSphere, DB2, etc. as long as you have or can find the technical resources to implement it. Where IBM seems to fail is scaling DOWN for smaller organizations. Connections 5.0 on-premises would have required us to create 7 servers -- yes, they would be virtualized, but still that's 7 OS licenses, 40 virtual CPU cores, 80GB RAM, and a few TB of hard disk space. All to replace Quick which runs on 1 server with 1 OS license, 4 cores, 8GB RAM and 600GB of disk. Granted, there are major differences in capabilities between the two, but how do you get a CFO understand why features like a mobile app, file sync, and social sharing require 10x the back-end resources?
Trello keeps me organized, focused, and on track. I could filter the Trello board to only see my issues and understand what I needed to work on and when.
Trello helped our team implement an agile structure. It's a very simple kanban method of viewing all of your team's tasks and statuses. You can completely customize the columns to your team's specific workflow and create tags relevant to your work.
Trello helps reduce unnecessary communications between teams. When I want to request translations, I simply create a card on the localization Trello board -- no need to directly message anyone on the team, and I can watch the status of the card change from "in progress" to "in review" to "translated," all without having to directly ask for updates.