Flowdock vs. HCL Connections

Flowdock is well suited for small teams and to environments that doesn't need too much reliability. I think it has some management problems that can make your life difficult if you have to manage a big amount of users. If you want just a tool communication with basic features (without using any integration or robust features) it can be suitable for you. You should try Flowdock using its free version for a small team and compare with others similar products. Flowdock delivers team chat and collaboration features, but is not necessarily the best product. Maybe some usability problems that disturb me won't be so relevant to you.

Incentivized

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.

Incentivized

• Possibility to integrate with external services such as e-mail (send messages to a flow inbox from your e-mail), twitter, github, confluence, jira, single sign-on, etc. Using those integrations you can easily improve your team productivity by centralizing all useful information in just one point.
• Very easy to configure. You can get it running for your company or team in a few minutes. Furthermore, almost all platforms (Windows, Linux, Mac, iOS, Android) have an app to install and there is a web version that can also be used.
• Powerful communication tool. You can separate differents subjects in to separated "flows" or channels. In addition, you can invite people to join just one channel increasing privacy for others members.
• Free version up to 5 users. If you are a non-profit organization or have a student project, they say that is possible to work with that too. In other case, you have to pay per user/month.

Incentivized

• Connections has an easy to understand layout so if you are new to the tool you can catch on quickly.
• The security features are excellent, I feel comfortable that we will not get hacked.
• Connections provide a single place to store project docs, pics, emails and to collaborate real-time with your team.

Incentivized

• One thing a little bit annoying is that a lot of links to others Flowdock sections (preferences, external services, etc) will open a new window/tab. Each click may take you to a new window and you can get lost easily.
• There isn't a quick access list to members of your organization to start a private chat. I took a while to find how to do that. The interface and usability could be better.
• There isn't an app for Windows Phone.
• Sometimes you try to load some conversation and it doesn't show anything. It is not frequently but happens sometimes.

Incentivized

• 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.

Incentivized

I go with the flow because I'm a newer employee and Flowdock works as advertised. If it were my decision to choose a team communciator for the organization, I'd recommend we go with Slack for its robust features and ever-changing/evolving software integrations. Slack is the outright innovator in the space and will continue to hold that role for some time.

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Incentivized

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.

Slack is a similar software.

Private chat or channels are well implemented in both softwares and both are also very easy to setup.

Besides of some usability problemas I think Flowdock is still better than Slack in this user experience and design.

The second point is the price. Flowdock is half price of Slack ($3/month). If you are a student or a non-profit organization, you are able to get some special license.

Incentivized

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.

Incentivized

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?

Incentivized

• Increasing productivity by reducing idleness, e-mail flooding, miscommunication and accidentally deleted files. We have increasead about 30% our productivity since whe start using Flowdock.

Incentivized

• 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.

Incentivized