Forum Discussion
Should we introduce Yammer first when starting Office 365 adoption?
- Aug 08, 2017
Thanks Daniel, I think that that is one of the important questions. And I would like to add 'with the least amount of resources.' Because some values will take a lot of time / costs to implement while others are easily implemented. In my post above I argue that Yammer, for me, has been a relatively smooth implementation and might enhance other O365 implementations. However, I agree that this does depend on the goals of the organization and perceived added value of users.
Hi Marlon,
At my current customer we started with:
- Yammer
Social on daily business topics and introducing first steps in Office 365
- OneDrive / Delve
Working with personal files on Office 365. Learning the basics of Office 365
- SharePoint 'soft launch'
SharePoint sites on demand (early adopters)
- SharePoint 'full launch'
SharePoin for everyone
During this staged roll-out Yammer was our most important communication channel. Users where sharing daily business topics on this platform, but also started with topics about the use of OneDrive, SharePoint etc.
We at this customer Yammer was started at first, and still available. Great experiences with this approach.
Regards,
Marcel
Interesting Marcel, thanks.
We now kind of have the same approach and same experiences. The thing I like about this approach is that, once users are accustomed to using Yammer, they (mostly innovators and early adopters) are starting to ask for other functionalities as well. We for example get questions in Yammer about 'how to easily share project documents with each other?' and by responding (via Yammer) that they can use a SharePoint site, the word starts to spread more easily.