Anyone who is involved in discussions with colleagues over Facebook at Work (I imagine many of you are the same ones that deal with the Slack discussions) here is an informative article around progress on the product.
I echo the authors comments around building relationships and community as a driving force for new ways of and Facebook at Work does have nice features.
However, no communities or relationships within an organisation sit in isolation from the way work gets done or linked to its strategy, processes, workflows, campaigns or initiatives. You could spend time integrating Facebook at Work with search but eventually you will need to leave Facebook at Work to deal with the outcomes of the communities and relationships.
The benefit of O365 is the increasingly ‘seamless integration’ with other capabilities that may be needed as a result of the community outcomes. For example, files uploaded on Yammer will be hosted on SharePoint. Conversation on Yammer could bleed into a Skype Teams call. Videos displayed on Yammer will play through Stream. There is linkage to Office apps, O365 Groups etc. All activity will be understood and surfaced via Delve. The need to leave O365 becomes increasingly unlikely within the collaborative process.
The compelling narrative behind O365 will be the seamless integration with the way people collaborate, not just building community and relationships, but in group work, file sharing, communicating and other collaborative activities.
One things I strongly agree with thought is “It’s not the tool but the people and programming that make enterprise social a success.”
My bias comes from a people centric perspective (rather than document or process centric) so I’ll be interested to hear other folks opinions, especially if you have been involved in a Facebook at Work trial.