Forum Discussion
Pivot for driving adoption: Build it around Team Site
- Sep 16, 2016
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)
I concur with Mark's response, and the order he suggests, particularly in the "What's in it for me" statement. If you want users to work differently, meeting them where they are to understand the challenges they face then propose a solution that addresses them is the best way to go IMO, particularly if that can be tied to a measurable business outcome. I'd expand the "What's the pitch" part to identify the target user communities the solution is intended for. that way, the WIIFM message is aligned.
The only other thing I'd add below is managing resistance. People naturally resist change and being vigilant in looking for places where users or departments are resisting the change need to be addressed directly.
Finally, from a purely technical perspective (assuming all the stuff we just covered is in effect) I'd consider looking at Outlook Groups. In addition to team sites, having groups gives you
- A distribution group for team communications
- A OneNote notebook
- A team site for collaborating
Great discussion!
Thank you Mark.
Indeed, Groups plays a big part.
The integration of group options is still evolving though - main concern is we may need to have groups as well structured as possible, Yammer and Planner groups comes into play and we do not want to end up with confusing groups particularly for large Organizations as ours.
- Mark TilburySep 21, 2016Brass Contributor
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.
- Leon ComoSep 21, 2016Brass Contributor
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.