Forum Discussion
Solved
Pivot for driving adoption: Build it around Team Site
Like in most successful endeavors, we need something to build driving adoption around. For Office 365 adoption, my idea is to build it around Team Sites - where the prompts for harmonized use of the...
In a perfct world I would generally use the following stages:
- What's the pitch (communicate the 'why'; align the stakeholders)
- What's in it for me (define new ways of working, end-user journey, candidate environment)
- Business architecture (technology alignment, planning and measures of success, governance) - this is where you can strategically look at which tool to deploy first (unless you are giving everyone, everything at once) and which brings most value. In my opinion if you are looking at changing the way an oranisation works it's a 'Yammer First' approach. Get that right and everything else becomes easier)
- Business Engagement (leadership engagement, use cases, stakeholder management)
- Adoption Services (coaching and training, advocates, events, communications)
- Sustaining Usage (this is the psychological aspects where we introduce behavioural economic techniques, nudging, social norms etc)
Thank you all for this excellant discussion.
We have recently migrated to 365 and I have been tasked with it's long term adoption. Despite deploying the entire product all in one go, usage is currently limited to Email, OneDrive and Skype. Formal SharePoint deployment was intended as a phase 2, but I am reading great things about Office Groups and Team Sites making deployment (and adoption) less confusing. Several previous replies specifically mention user perception when driving adoption, and I am concerned that unless I am able to present (at least) like for like functionality in certain key areas such as file sharing (think mapped Network drives), any attempt to promote the new envrionment will fail miserably.
Does anyone have any further advice, and I appreciate slightly off topic with regards to using a migration of file server data to SharePoint as a adoption driver.
Thanks,
James.
Yours sounds like the situation we are also into on O365. At the moment then I can only give insights based on a relative knowledge coming from previous experiences of implementing couple of hardsells and few softsell ones.
Groups is just a notion, but this rides/creeps into existing organizational and technical structures and feeds pre-existing needs, hence a lot of opportunities for Softsells when it comes to actual uses of the tool suite. Just letting them start with it will naturally start the steady adoption and may even surprise with quick wins that can trigger adoption frenzy if we make things fall into place e.g. easier compliance on QMS for control of documents and information and centralized maintenance and global accessibility of most used templates.
Trying to present a like for like functionality can easily become a lot of hardwork for frustration. For us, I am just taking notes of whatever shortcomings of what they currently use and then excite them on how these can be finally solved. Keep of course a subtle caveat about pains of going through the change.
File servers - to be honest at least on most file servers I have seen is over 90% virtual dump site or paranoia placebo for not losing anything we might need in the future whereas in fact we go back and re-use only about 1 to 5 % of the files we have ever stored there if not way less. Therefore, if migration will be painful and expensive due to the scary size and magnitude, I would never recommend migrating all contents over. Instead, I would offer a more organized flow and structure into OneDrive and document libraries of Sharepoint starting only on most used contents - the rest can follow as needed.