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
Jive
Score 8.7 out of 10
N/A
Jive Software, part of the Aurea family of customer experience solutions, provides the gateway to an organization's most important assets – its knowledge and people. Jive's interactive intranet solution promises to connect people, information and ideas to help businesses outpace their competitors. The vendor says the product has more than 30 million users worldwide across every industry, and is consistently recognized as a leader by top analyst firms.
IBM Connections is possibly most suited for larger organizations where bigger teams are able to have more people to share with. Also, it may be less appropriate when there is so much security that it would hinder the anytime, anywhere access capabilities and prevent users from being able to enjoy sharing content with each other.
The content in the news section isn't totally responsive - meaning if I have a small window taking up half my screen, the images for the headline articles may not load properly and when I maximize that window, it's left with ugly half-loaded images. Also, the collaboration feature for Office documents is great in theory but tends to cause more pain than it's worth to just download the document and open it separately in Word or Excel.
Search in connections is incredibly poor. It's commonly joked that once data goes into Connections, you never find it again, unless you have a direct link. This alone kills usability for Connections.
Embedded content in wiki pages in connections is poorly implemented. While the content displays, you can't interact with it, or edit it reasonably, and it's really slow to load.
The "social" features in Connections are pretty lame, and no self-respecting user spends any time trying to build their profile. It's just disappointing.
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.
There are always external factors that can impact this decision but currently, the Jive platform is maintaining its lead in the market place in this area. If the innovation in this space by Jive continues, then this number will remain high. Integration with other systems and adaptability to changes in the market or in client needs will also make this decision hard to predict more then 6 months into the future
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.
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.
Uptime was OK. But there was one day that the system crashed for a whole day. Our company was unable to operate. And all the plugins to word/excel froze causing those systems to freeze.
Jive posted a statement to the media saying all customers were up, but we were not.
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.
They did an OK job when I needed them. Except for the one day the system went down. Jive pointed the finger at the hosting company, and the hosting company pointed the finger at Jive. No reliable information came to us.
Jive online training is there. It is OK/average. I feel some other companies are doing better. It is not a piece that is required to have a successfully implementation, but it could be useful to improve it
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.
IBM Connections offers a complete package of tools that can be useful but it doesn't integrate well with other services. Competitors like Yammer offer slightly fewer features but are cheaper and much easier to maintain. If we were making a decision today we probably would choose a combination of Yammer, Slack, Microsoft Teams, and other Microsoft or Google Tools.
I honestly don't recall what we briefly used before Jive - it wasn't good and didn't last long. I think it was under-utilized because you couldn't really do a whole lot with it. Jive does pretty much everything we need it to do, so for that reason alone, Jive is the superior tool.
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?
