Forum Discussion
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)
One of the key documents in any adoption / change campaign is 'what goes where' or 'which tool when' - if you leave people too many options they will just avid using them so clarity around this is important to give people confidence.
That is one single big chunk of challenges we have to face - the overlapping functionalities.
Where the groups go, individual users must go - so indeed it is really pointing into pivoting from Team Sites that has to be managed / administered well.
