Let me be clear: you should really only opt to use Connections if you have no other choice. It will get you by, but it won't make you efficient.
At the moment I can't think of any scenarios where it is less appropriate.
Ex) The status feature is essentially useless without following the person posting the status. We do not follow individual staff members because it leads to a cluttered newsfeed with information irrelevant to other departments. We still use our phone chat client to communicate statuses.
During the selection process I would ask what the primary type of information the users work with: text documents or images/media. I would also ask how many users are planned to participate in the system. The bigger the organization is the more sense it is to use IBM Connections.
If you work in a large company with lots of IT resources experienced with IBM tech such as WebSphere, DB2, etc., then I’d change the recommendation to an 8 for IBM Connections on-premises. Users really loved working in IBM Connections despite various gaps they found, and it seems that IBM is very responsive to customer feedback. Many new features in the last few releases were first suggested by customers.
Similarly, if you work in an SMB and are looking at IBM Connections online (or SmartCloud or whatever IBM calls it these days), then I’d probably also say 8 assuming the cloud version is at least as good as the on-premises version. My guess is that the cloud version is probably better, given IBM’s cloud-first strategy, and don’t forget that the cloud version includes IBM Docs.
If, however, you are in an SMB with a budget-constrained IT staff who are mostly familiar with Microsoft and who find it difficult to work with anything non-Microsoft, then IBM Connections on-premises is probably not going to work well in your organization. I’d score it a 4 in that case. Even if it works well for end-users today, as time goes on it seems users discover more gaps with the software. IBM is not quick to put out new versions of their on-premises software, either. The primary reasons I think on-premises is a tough sell in this scenario are the high cost of consulting (which has a side effect of further delaying the introduction of new features), the lack of an office document editor built-in, and the lack of training for both IT and end-users alike.