I often get asked about things in IBM Connections that need some explaining. One of them is the value of using the Like button in IBM Connections and whether people really should use it in a corporate environment. Let me be clear: You should! But in stead of writing another blog on why I decided to do it a little different this time and try my luck on explaining it in a video. I hope this will help!
I’ll try to do a few more like these over the coming weeks and in case you guys have questions you would like to get an answer to in regards of IBM Connections functionality let me know! who knows, I might do that one next then :)
With so many solutions touting social capabilities out there and being used for different situations it can be daunting to decide on when to use what and why. Your organization might already have Salesforce, IBM Connections, Sharepoint and solutions like Jira that offer social capabilities but how do you get all these worlds together? The last thing you want after all is to have one department ‘being social’ in one platform and another somewhere else. That completely undermines the whole aspect of cross company collaboration….
but there might be good reasons why they need to use those different platforms. Your sales departments might live and breath in Salesforce and need that direct connection between their Chatter posts and the accounts they pertain to and your developers might scream bloody murder if you take away their JIRA wall. But what if Salesforce and JIRA aren’t being used in the rest of your organization and other solutions are required or used there? Like IBM Connections. How do you prevent a ‘social island’ culture in your collaboration landscape?
Bringing it together
There are several solutions and integration options out there that address the problem of ‘social islands’ and offer integration for a large number of platforms like JIRA, BOX, SharePoint and even Salesforce already. Mostly orientated on pulling information from these platforms into the IBM connections environment or integrating specific parts of IBM Connections into them. But when it comes to integrating IBM connections into the Salesforce environment or two way integration there really was still a lot to win. This is changing as QKOM has been working hard on creating a solution that will allow for deep and seamless integration of Salesforce and IBM Connections.
By allowing the user to connect through OAUTH to use, create, search and post directly and effortlessly from within Salesforce to IBM Connections communities, files, activities and update streams – Salesforce users will be able to collaborate and work in both systems at the same time without having to leave their environment. Keeping other organizational users (or even external partners!) who might not have access to all the info in the Salesforce environment up to date of developments and statuses and utilizing the many great options each system offers. This will save your organization on potentially expensive licenses and allow for a connected yet still also secure and specialized collaborative landscape.
I’ve had the pleasure of collaborating with QKOM on this topic discussing further use cases and functional requirements and am excited to see more bridges between the Salesforce & IBM Connections worlds being build. After all, it’s all about finding ways to collaborate!
Please see the following clip for a first glance of what is possible but keep in mind that there is more to come very soon so stay tuned
At one of my customers a user complained about the fact that every time he opened a publicly shared file it would automatically ‘follow’ that file. This meant that every subsequent ‘like’, change or comment to that file would show up in his timeline. Of course he could ‘unfollow’ the file but found it irritating that it would follow it at all without him making that conscious decision.
After testing and a little digging by our admins it turns out that indeed this is the default behavior for IBM Connections and can be managed by changing a setting in the files-config.xml:
So no big deal but we did have a bit of a discussion as to why this setting is there in the first place and if it is logical. Yes, there is a case to make for auto-follow as that will ensure you keep track of subsequent changes to that file. After all, a publicly shared file that you don’t follow or isn’t in a community that you follow is sometimes hard to track but at the same time it can be quite annoying. In an environment with thousands of users and where public files are shared and mentioned in other sources like the intranet, auto-following a file simply because you opened it once, can cause lots of updates in your activity stream by other people ‘liking’, commenting or editing the file. Information you might not be interested in at all as you only just wanted to read it that once.
To be honest, I think this is one of those settings that can be interpreted either way. The bigger discussion now is do we disable it? This user clearly finds it annoying but what about all those other users? Do they want to auto-follow or not? The setting is org-wide so any change will influence all. You can’t just change the default behavior of a system used by thousands of users without annoying at least some. I guess this is something that will have to be decided by the the business.
So what do you think: Is auto-follow indeed the logical behavior or not in a Enterprise Social Network and how does your organization handle it?
On Tuesday Jan 27th 2015 my coworker Sasja Beerendonk and I had the privilege to present at IBM ConnectED in Orlando, FL on our favorite topic of Social Business. Below is the session abstract & slide deck for those interested.
BP202: Beyond Theory: Trials and Tribulations in Becoming a Successful Social Business
There are many theories and ideas around “how to become a social business” but what really does or doesn’t work? We wanted to know, and instead of just going blindly with the theory, we did the opposite and interviewed 32 companies in various stages of their journey to becoming a social business. Not just asking them about the big wins, but also talking about the struggles and small successes that really made the difference for them. Taking these experiences and real life examples of companies the likes of Dutch Railways, DAF, Saxion, Forbo Eurocol and Bavaria, and aligning them to the various theoretically relevant concepts, we were able to come up with some interesting concepts. In this session, we will take you through these concepts and theories and, using the examples provided by the companies, show you how these can help you identify the successes and avoid the pitfalls in becoming a social business.
For a while now I’ve been working on various posts on the topic of “Folders versus Tags” and why there is no such comparison really… This is a topic that is often hotly debated among people involved with social business and definitely close to my heart. The problem is, none of those posts ever saw the daylight as they became too long, too complicated and simply said: boring. There is a lot to say about this topic but most of all a lot of explaining. therefore I tried something different. I hope this infographic will help explain some of the specifics of each of the options and why comparing them isn’t always possible. Have fun!