Microsoft Sharepoint & Yammer – really the best choice?

Part of my role as social business evangelist I look at tooling that is available in the market and discuss the pros and cons of those solutions versus what IBM has to offer with IBM SmartCloud Connections. In a discussion with a business partner who implements both Office 356 and SmartCloud offering, we exchanged some good arguments. From that discussion I came up with some tough questions your should ask (and answer) yourself before moving on with Microsoft Office 365:

1. Is Microsoft putting its eggs in the Yammer basket? Will Yammer go away?


  • No new Yammer function have been implemented since the last 12 months
  • Even Yammer functions have been taken away like Yammer Events.
  • There is no clear roadmap for Yammer functionality, yet there is one for SharePoint

2. Are Office 365 and Yammer one offering?


  • Integration after two years is still limited (see my previous blog post)
  • Microsoft Office Delve is there to solve the search issues SharePoint has. Well oops, Office Delve does not search Yammer files. Roadmap states that Lync and Yammer will be added to the search, it does not state Yammer Files.
  • Still two news feeds, multiple mobile apps to follow

3. Do your employees expect a good mobile user interface? 


  • To work with Office365/Yammer you need 7 different mobile Apps (meaning 7 times a login action) and a lot of places to store files and uses the mobile OS browser.
  • No integration of collaboration options Yammer and SharePoint, No good search, and a confused user (where to share what/ where to collaborate).
  • Mobile collaboration looks more as an after thought. See this Yammer Mobile video. It is all about conversation, not collaboration. And the mobile app for SharePoint 365 is not delivering a good social mobile interface either, as you can see in the second part of this video.

4. Is Social collaboration only about documents and conversation?


  • Search with Office Delve is focussing on documents (SharePoint) and conversations (Yammer). In the demo on the Office Blogs entries in Delve app were Office files and video. No mention about wiki, blog, profiles.
  • No tagging of content/profiles: Tagging is glue to find information. e.g Tagging of profiles allows users to be found based on tagging. Expertise finding is not done by searching by name.

5. Do your users want to receive more email? 


  • SharePoint sends emails for everything to notify users.
  • Yammer sends newsletters per network. If a user is member of 20 communities/networks = 20 emails. So it is notifications galore! Just to compare: I am part of more that 120 communities with IBM, I get only 1 newsletter.


In conclusion:

SharePoint/Yammer might look like an obvious choice, but it is not the best choice for your company for social (mobile) collaboration.

Looking at the facts it is not the best integrated collaboration platform. So take a moment and look what value IBM SmartCloud Connections can offer on top of your existing collaboration infrastructure. Or even better take a test drive with a free trial account.

If you have any questions regarding IBM SmartCloud Connections just let me know.

Yammer (tries to) brings conversations to your OneDrive and SharePoint Online files

Almost two years ago it was big news that Microsoft bought Yammer for $1.2 billion to get into the social cloud collaboration market. From the first announcement it was unclear for the customers and end users where to do what and how. In the end Microsoft message was: Sharepoint is the application platform and Yammer is the social layer on top of that. In the official blog entry of Jared Spataro (General Manager of Enterprise Social at Microsoft) it is stated: Go Yammer. And he enforces this message with the statement that Microsoft is effectively abandoning SharePoint social, saying the basic social features shipped in SharePoint Server 2013 will see no more major updates. So the future is SharePoint Online + Yammer. But for the end user it is still not one solution, but two solutions that are glued / or being glued together.   The Yammer-SharePoint integration of the two products has started very slow but now we see more initiatives. First step of integration that was announced was the option to integrate / replace the newsfeed of SharePoint with the newsfeed of Yammer. Only in February 2013, the company unveiled simplified login to Yammer from Office 365 and with the release of SharePoint 2013 Service Pack 1 it allows on-premise SharePoint deployments to use an in-the-cloud Yammer network via the navigation bar.   Now Microsoft has announced this week in their Office blog entry that it now brings Yammer conversations to your OneDrive and SharePoint Online files – something what Microsoft is calling inline social experiences.   In theory it looks nice to have comments/ conversation next to your SharePoint file, but it is a big fail….#WHY? – Some info comes from the FAQ at the bottom of the same blog entry with this big announcement.   1. All notifications of what is happening inside SharePoint is send via email: the comments made are not shown. So when receiving a message the end user has to go to SharePoint to see the comments. Check this embedded experience in IBM Notes Mail – Screen Shot 2014-06-06 at 12.45.29 PM That is really a big difference. All comments are shown and end users can even write a reply into Connections, not leaving their email client! This is really an integrated end user experience. 2. When a file is renamed the whole Yammer discussion is broken. Nothing new as it is a know issue already know in SharePoint 2010. All links that are shared or used for reference use a file name. Here the official answer Document Conversations uses Yammer’s Open Graph protocol, so when a post is published it also contains a link to the file. This link serves as the glue between the file and its associated conversations. Because the link changes according to the file name, when a file is renamed, the link changes, causing the Yammer conversations to become disassociated from the new file name. If you share a file to another my site you share a copy, with another URL, so comment won’t follow the “copy”. Within IBM Connections a URL to a file or other components of Connections, contain a unique ID – This allows people to use and share URL’s without the worry of a rename.   3. The conversations are only for internal networks. That is really killing as more and more companies work with external people, communities, companies to collaborate and share files and other information. So not being able to kills the whole concept of social collaboration. Compare that with the IBM Connections on premises and SmartCloud offering where end users cannot only collaborate within, but also around (comments/discussion thread) a document with external users. And as you can see in this screenshot I am logged in as an external user and I can see the comments. Screen Shot 2014-06-06 at 1.10.56 PM 4. This point was made by an IBM partner who was trying out the new Yammer conversation panel. In the end they gave up after testing; here is why: When using Yammer to start a discussion around a document the status updates are linked to the document. When using SharePoint and the conversation panel I can add comments to a file and/or I can start a discussion with status updates in the Yammer Conversation Panel. You would expect to have now one discussion, but no. There are now three separate discussions and to make things worse: as SharePoint user you don’t see the thread started by Yammer and vice versa. How bad can it get. Depending on which widget/tool you use, you will see, not see the update. Did anyone test it out?   5. From all remarks that are made the end user cannot see to which version the remark has been made. So if a file is on version 7, some or most of the comments are useless. In that case end users can no longer trust the comments. Look at how well this works in IBM Connections Files: Screen Shot 2014-06-06 at 1.37.01 PM   6. Using the mobile apps, plural, how to know where to look for updates. The newsfeed app, showing SharePoint updates, the Yammer app to see the conversations. Getting limited functionality and in some cases being redirected to you browser app and for editing files the end user needs to be in the three different Office apps: so mobile confusion all over. So nothing inline in app here. So my conclusion is that this feature looks cool and nice, but does not deliver real business value due to 6 points mentioned above.

SharePoint Conference Keynote: Releases and Roadmap – So what is new?

Yesterday the SharePoint Conference Keynote started and via my social media this blog post of CMS Wire was shared with me. While reading the blog some thoughts came up, so let me share this with you:

Here the first quote that caught my attention:

Jared Spataro, general manager of product marketing for Microsoft Office, followed Clinton. He focused on the vision and goals shaping the future of Microsoft.

  1. We believe the future of work is all about working as a Network.
  2. We believe in personal insights that can be heard when you cut through the noise.
  3. We believe in the power of an open development platform and a robust ecosystem.
  4. We believe that the future of work is only possible when people can work anywhere on any device where organizations can still manage them securely.

First impression is that there is nothing new here. Let me go through the list

1. Since the book of McAffee about Enterprise Social Networking the whole concept of social collaboration / social business is involved around the power of networking. Within IBM we are collaborating this way where I work in virtual teams on different projects and communication is done by sharing messages on my board and my network can read this. We even use the networking platform to work with customers and business partners, indeed as a network. And I am pretty sure that IBM is not the only company working this way. So why believe the future of working is working as a network. I know Microsoft was late at the table for social, thus they bought Yammer to catch up. But wake up: the future is now.

2. Putting social analytics in the visions and goals also shows that Sharpoint is lagging in the social enterprise platform. Most ESN vendors have social analytics build in. When looking what we do within IBM (researching social analytics) it is really tangible and not a vision.

3. Microsoft states here that it believes in an open development platform. I would have preferred that they would adhere open standards, like OpenSocial or That would really open up the platform and make it really powerful. Just by opening up the API is imho not an open platform. Second the fact that Microsoft told SharePoint customers not to customize SharePoint too much does not help to support the vision of an open platform.

4. Microsoft tells people that they can work with any device anywhere. This is really a vision as there is still no Android Newsfeed app. Which is a very basic app to get the newsfeed information. Second: creating apps for the largest mobile operating systems is good, but they should put the design team to work as the usability is far from good, e.g. multiple apps to work with SharePoint, UI glitches and limited functionality. Looking at the Connections mobile app is is light years ahead in usability and capabilities.

Further in the blog there is a statement on new releases. Here is the quote:

next versions of SharePoint and Exchange will be released in 2015

I remember that Microsoft took over Yammer, as they were the company that could build agile software, with monthly/quarterly updates. So if you are now on SharePoint 2013 you have to wait, as usual, several years before being able to upgrade your on premises servers.

To looking at these points I can only see that what microsoft calls a vision and goals, it is just catching up on social and mobile. Nothing new here, most competitors like IBM, Jive, Sitrion, etc are already delivering this. And then the old school 3 years release cycle?

So why wait,for Microsoft to finally deliver,  if you can get the business value (on top of your current SharePoint environment) right now?


[EN] Star Trek Reloaded? Eight of Nine – IBM rules the Social Business Market – New Study from Experton

Originally posted on Digital Naiv:

small_ExpertonSocialBusinessLeader If you are reading a lot of analyst studies, you usually have the choice between ‘best of breed’ and ‘best platform offering’. This time it is different. Experton, the European Analyst firm, did an extensive vendor benchmark on Social Business. They are – at least to my knowledge – the first ones collecting data from Social Business Services up to different software components playing into the Social Business space. Just published early 2014 their study shows 9 different quadrants. And the results remind me of Star Trek Voyager and 7 of 9. Why? IBM is in the leader quadrant in 8 of 9 quadrants. The only quadrant not listing IBM as leader is the one for Social CRM. IBM doesn’t have an offer in this space … This is an outstanding and impressive achievement and shows the companies commitment in the Social Business space.


When talking about Social Business, people…

View original 908 more words

Social Software Adoption

After choosing the right enterprise social platform, see my previous post, it is essential to start and enable your people on how to use the tool and get them to understand why they should use it. The old story about the carrot and the stick. Make sure that they feel helped and made their life easier, as people in general, don’t like change. And to succeed in achieving your goals you have set to become a social business, step one is getting the people moving. Research shows that if you don’t do anything only 5% will start and the rest will continue the old way.

For starters you could tell the people theory on how to use it, but wouldn’t it be helpful if we could give them a little push in the right direction to start using their social network tooling. Especially if there is already so much available in the toolbox: a broad platform offers to anyones likings.
Within IBM Connections there is now a great way to give your users a head start with IBM Connections Touchpoint.This asset of IBM Software Services will onboard new users and the end result is a filled out profile, some network connections and some communities in the community list. Just enough to get the system to work for that person, as based on that it will show content on his activity stream and the end user will not stare at a blank screen and emotionally log off.
Touchpoint will start a guided procedure that takes about 5 minutes but is for the end user really worthwhile:
Screen Shot 2013-12-13 at 3.17.50 PM
 The first step is to have the user fill out his/her profile and upload a profile picture.
Screen Shot 2013-12-13 at 3.18.35 PMThe second step is to have the user to tag about how the profile can be found. What is the users core competence, what are is the user about, what is the users intrest. This is an important step as it will make this profile found if someone searches on a keyword and on tags. It will also make the profile show up in tag cloud and linked people when searching for content in Connections.
Screen Shot 2013-12-13 at 3.19.10 PM
The third step is about starting up the network within the organization. The list here shows suggestions and the user search for other colleagues. Just click and the colleagues are added to the network
Screen Shot 2013-12-13 at 3.20.00 PMAnd it also gives suggestions of the bright stars in the company
Screen Shot 2013-12-13 at 3.21.27 PM
The last step is the on boarding of the user in Communities that are interesting
Screen Shot 2013-12-13 at 3.22.28 PM
The end result is a user that is networked within the organization and is ready to participate in communities. The activity feed will now be filled with content from the people of the users network and information from communities. Based on the memberships and on the network, content suggestion is done by social analytics.
Check out this video on youtube to see a real life demo:
So far so good. the first step in using the system is set, but it is a small step, as if there is no follow up on integrating the platform in the end users business process, it will soon be seen as “yet” another information tool. But at least the first impression that lasts for ever hurdle is taken.

What does it take to become a social business?


Two years ago IBM put social business on the map and told the world that they had to become a social business too; “Get Social, Do Business”. At Connect 2011 IBM told the world what you could and should do to become a social business and Connect 2012 it were the customers telling other customers how they have become a social business. That was really powerful as it shows the (sometimes intangible) benefits of a social business. And that last remark is interesting, as most companies want to know the ROI upfront before investing in Enterprise Social Software (ESS). As I was listening to the audio book Enterprise 2.0 by Andrew McAfee in my car (which explains why I can’t tell on which page I have the quote, so my apologies upfront) there was also the statement in the last chapter that the ROI case is not always to make with 2 digits after the “.”.

The ROI of ESS is not immediate as e.g. the implementation of a digital telephony system or a web conferencing system. It requires more time and effort on the part of cultural change management and getting social embedded into the existing processes of an enterprise. This does not mean that there is no ROI case to make!  There are a lot of success stories of the use of ESS and there are also reports of e.g. McKinsey, that state that enterprises using social business are outperforming the companies that don’t. IBM even delivers workshops and other services like the Business Value Assessment focused on the benefits of becoming a social business, providing clients and business partners with case study examples of successful social businesses, and helping them to develop an agenda for driving social adoption.There are a lot of examples benefits of what social business has brought companies that started to use enterprise social software. Most of the examples on that blog post give hard numbers or time reduction, but the best example is TD Bank. The result they had with their ESS was that the employees were proud of their bank, felt valued and had more trust. Those things are not measurable in hard currency, but real value for your enterprise.

So the question is not whether you should become a social business, but whenwill you start?


There are a lot of white papers, blogs and books about how to become a social business. Sandy Carter has written in her book Get Bold: Using Social Media to Create a New Type of Social Business about the Social business agenda to help companies to become a social businesses.

The focus in the book is on the organizational aspect of becoming a social business and the conclusion is that becoming a social business is not about IT, but it is all about people!

Reading blog posts, reports and other information I see that the rule of thumb is that the effort to become a social business is 20% IT and 80% change management. This blog entry will not focus on the change management and cultural aspects of becoming a social business, but on what platform/ features do you need to offer your employees to accept and enable them to work socially?


Before an enterprise is selecting an ESS platform what are the specifications of that tool. In my opinion it is key that formal requirements are set up. Why?

Because the tools should be consistent with the goals. To give an example: Capgemini choose to use Yammer as they ESS tool, but the employees know that “no confidential or client-specific matters are discussed”. So how can you work and not be able to discuss freely about your work? Seems like rowing with your hands tied to your back. When I read the blog my impression here was that management saw that they had a lot of people subscribed to Yammer and management thought: well lets turn it on to start Social. Not realizing the shortcomings of the solution they chose. Another reason could be they wanted to get control over the freemium environment and then had to pay up to be able to administer the users. And when they finally had control they found out that a lot of users had only a profile but were no longer active user (probably as there was no change management / cultural change to promote and keep people engaged).

So my point here is: think before buying ESS platform! Check your goals and set the requirements to achieve those goals. It is just like one would do with the purchase of any software program. But the question then arise: what are the must have specifications to look for?


In the blog entry The ROI of Enterprise Social Networking, It’s like Pushing a Button there is a nice metaphor for the nice key features of an ESS platform:

Red ButtonWouldn’t it be great to have a big red “Ask” button on your mobile phone, iPad, and browser that instantly connects you to everyone in your organization when you need something? And how great would it be to have a big green “Share” Button to update you teammates and management on your work, interests, and experiences?  Better yet, the big buttons were smart enough to connect you to the right people, without spamming or bothering those who weren’t available.

It is a nice and simple description of an ESS platform, but in reality there is off course more to it. The rest of this blog entry will try to describe (IMO) the key features.

Open and Flexible Platform

The first and most important requirement of ESS that is should be an open and flexible platform for anyone to use within the enterprise. Don’t go for point solutions, but make sure that specific solution integrates into your ESS platform.

Why should you have an open extensile platform? Because the pace of innovation is going fast, you cannot rely on an ESS solution that gives an update only once every 3 or 4 years. Three years ago Android had a small market share, two years ago an iPad was non-existent and now we see Pintrest coming up on as the latest social phenomena. To support these fast changes in the outside world, make sure you get an open an extensible platform with a regular functional release cycle. In the industry software vendors are getting into more frequent release cycles. No releases to only fix bugs and security patches, but real big functional improvement cycles. When you look at mobile apps the update cycle is very quick. This way the end user get new incremental functional updates ad fixes, but you don’t want to patch the core of your ESS system every two or three months.

The reason to have an open standards based ESS platform is to assure that you can leverage the power of your platform to incorporate the latest trends and you can incorporate these into your business processes into the social platform. It will also allow you to integrate other existing or new corporate systems, intranets and processes. Here you can think e.g. about SharePoint Web Parts,, oAuth, OpenSocial, CMIS, Widgets, etc. to enhance your platform and embed and integrate social into the enterprise.

Openness also means that the consumption of the ESS services should be independent of the (browser) platform it runs on (Safari, Chrome, Internet Explorer, Firefox, etc.).  And, looking at the growth of mobile usage of the Internet, ESS should have apps for all major mobile operating systems. These apps should deliver all capabilities to the end-user. So don’t limit the mobile end user to e.g. only see and use the activity stream but make sure the end user can access the all ESS services of your platform. To conclude: bring (integrate) social into your enterprise (processes), don’t bring your enterprise processes into the ESS platform. Social Everywhere!

ESS Networking

As has been said before ESS is about people and the way they can Find, Reach and Collaborate with each other. Reading (euh listening to – in my case) the Enterprise 2.0 book of McAfee the concept of strong and weak tries was explained as one of the basic principles of Social Networks. And this is the core feature of the ESS platform: finding people and maintaining a relationship and exchanging information.

There are a lot of platforms that have a profile page and have a message board (Twitter). But one feature that is key is the tagging of information and people, e.g. within Connections everything is tagged. So based on a tag I can find everything, whether it is a blog, a file or a person. So finding people based on tagging allows me to find expertise, as you don’t search for a name, but you search for expertise. In 1999 someone said to me: “You don’t know much, but you do know who knows it or where to find the information.” Well, I had my brain tagging right, but it was all inside my head. People had to know me first before finding information and when I left the company the knowledge network was gone. So tagging is key, because it allows others to discover information with a social search within the ESS platform. Even if people have left the company the digital footprint will remain and will point people into the right direction.

The message board will help to get the discussion going and to keep in contact with you network. On the board people can let others know what they are working, ask for help, answer questions. It gets the conversation in the open (also know as working out loud) and no longer stored in email conversations. It is also a tool that helps to stay in contact as people are not always at the office.

Another aspect of an open ESS platform is that the personal (social) information is available in every context possible: web pages, instant messaging, email, Office and other collaboration environments. When ever you look at data within the ESS platform, relevant people should be visible. As there is so much content available it is important to know who has created it and it is good to be able to see who that person is and to be able to contact via mail, message board, instant messaging, etc.


In the previous paragraph I mentioned: Find, Reach and Collaborate. Finding the right people within the ESS platform is key. The second step is to be able to connect with these people with one click of the mouse (or for that matter the touch of a finger). The third step is to collaborate with others. Writing blogs, collaborate in wikis, generate ideas, share files and bookmarks, discuss in forums, etc. Communities are key in getting work done. Here information is shared within the context of the community. If someone needs to find information, a community is often a good starting point to get information, but also “meet” a group of people to network with, that are participating on the topic. And if you don’t find your answer you have a community filled with people that work on the topic you can ask a question. In the context of the community it is also important to have an activity stream to know what is going on within a community.


The third key feature is social analytics. As there is so much content created information overload. Analytics can help to filter and suggest content for the end user. Currently we see that activity streams ( as a new standard of informing users what is happening within their network. In Facebook I can see what my friends are up to. If I miss something, no problem and the number and activities of my friends are limited. So it is manageable. In my work I would go crazy if all updates of my network would show up. It would be like a fire hose in full force. Here is where analytics come in and can filter out and present the relevant information, transforming the fire hose in a garden hose. The activity stream will give updates on what is important and where action is needed. Gartner describes in the next generation of collaboration services this as the new way of working, where tweets, processes and activities show up in the stream.

The second good thing about analytics is content suggestion. This means that when new content is posted in my area of expertise, it will show up as interesting for me. Like I said before: there is too much content being created to keep up with, so this will help. And not only content, but also people (I ought to know) are suggested by the system. So when new hires or people learned new skills that are related to your expertise area you are notified of their existence.

Third: Analytics is key to drive the adoption of your ESS. If you can measure what is going on within the system, you can check the goals you have set to achieve with your ESS. Analytics on the level of communities are even more interesting as you can drive and control the community if you know who are the (top) contributors, what content is popular etc.

Governance, risk management, and compliance

Governance is important to tell people what they can do, supposed to do and what they shouldn’t do within the ESS platform. Most of the time there will be no trouble as ESS is used  within an enterprise environment where people act with a certain level of professionalism and everything added to the system has the name of the author. But there is always the possibility that someone can always misinterpret a written message. So every ESS needs to have the option to flag content.

Compliancy is a big issue as more and more regulation is put in place by governments and institutions. Compliancy within an ESS platform should provide the ability to monitor, track, and quickly pull out relevant data around conversations, posts and file uploads. For email and other systems this is often already in place, but it is also necessary for the social content that is generated, e.g. with the partnership with Actiance IBM Connections is providing a level of auditability in the technology, where every notification, every event, will be captured, archived in real-tim, and then made available through a substantial discovery process. If an employee posts insider-trading information to a blog, and later removes that post–but not before someone viewed it–an audit trail will preserve the evidence.


In the list of must haves I did not mention the blog, wiki, forum, file sharing, social bookmarking functionalities specifically. I see these applications within ESS as a given, like a bike has pedals. Most of these applications can be found within most ESS solutions. One thing I would like to mention here is that it is important for user adoption to have to features available in the context of the users workplace. That can be: posting a Word document into a blog, adding a file into the file share environment of the ESS platform by using drag and drop within Windows Explorer, uploading pictures from a mobile device into an activity stream or share a file from within a community into a Enterprise content management system. Integration is key and it works both ways, e.g. showing social information about the sender in your email client, or integrating email – social email – into the homepage of your ESS.

Social Personal File Management

One key differentiator is the file sharing functionality. What is not important is the place to store the file, or we would all be using Dropbox, but it is the capability to tag, like, share and collaborate around a document. No longer are files being placed on a shared drive, copied, modified recopied etc. There is one version and people will share links, where it is important that the link is “filename” proof (URL does not contain title) as with a rename the URL breaks. Here a nice Youtube video:

that shows the concept of social filesharing and a more traditional approach. One important feature that is important is to see your collaboration. What I mean by this is that the user can see what people have downloaded the file and have re-shared the file. This will give the user the ability to see his tippers; the people that will help him to spread his knowledge.


As I tried here to give you some pointers on the must haves of an Enterprise Social Software platform it is up to you to make a choice on what platform will suit your enterprise best.

First make sure you have the cultural change management in place. Set your goals and set the requirements list with your must haves. These are different for every company and even for every department. So talk to communications, HR, etc to ensure you can deliver the right tooling for your employees. One key ingredient is the tagging as it is the glue that makes the social software stick.

Second make sure you have a flexible and open platform. It ensures that it will be further proof and makes it easier to integrate in your enterprise (collaboration) environment to  enrich the current workplace with social. Together with a full mobile client it will help in the user adoption.

Third: When comparing feature functions, dig deeper then the functional description. I found out that two products had the same applications within the ESS platform, but when looking at the functionality there was a big difference. If possible take a test drive to see how intuitive and how, I know it sounds silly, how the UI looks like.  The first impression lasts forever when the user uses the system for the first time. New applications should always be easier then the existing way of working. Otherwise users will still work the old way. To give an example: one of my customers had the UI made like Facebook: zero phone calls to the help desk. So try how your defined tasks are done and compare how they are done, as you could see in the youtube movie, every platform does it differently.

Third: when you have your specifications look at where you want to run your software, on premises or in the cloud.  Cloud is now a very hot topic for IT, although sometimes things are not allowed (by law) or some functionality is not available. So if the cloud ESS is not delivering your must haves, a private cloud (hosting) might do the trick (e.g. so you can talk about customers and share confidential data).

Mobile Social Collaboration

While I was preparing my mobile collaboration video I was surprised that the capabilities IBM Connections delivers is almost one on one with the full web client. And not only on iOS, Android and Blackberry phones, but also on tablets. With the trend of BYOD (Bring Your Own Device) we see more people that use their own device.

Most vendors of collaboration software deliver push mail, instant messaging clients for multiple devices, but for social I think the focus on most big vendors is only on the conversation. So people are then stuck in second gear.

Worst mobile experience here is Microsoft SharePoint, as they have a brilliant client for the Windows Phone,

WP SharePoint Interfacebut really no mobile interface at all for other clients. So I tried the most downloaded app for SharePoint, but it focussed only on documents; not social at all. Yammer has multiple clients, but there I thought it was lacking the full capabilities. The focus was on the conversation and that was about it. Jive was also limited in comparison with their full web client, but I really missed a tablet version. Well enough typing here and see for yourself.