A closer look at how using collaborative sites has helped ALE teams and peers to share information and foster collaboration.
Among the many application and infrastructure projects – 125 at last count – that my teams are delivering as part of the carve-out from Alcatel-Lucent, there are several where our Enterprise Social Network has made a significant difference in that project's success.
Take Office 365 as an example
The benefits this software delivers in simplifying communications and the daily work process should make users excited about new possibilities, and one hopes they would embrace it at once! In fact, some did realize its true outcome: my office suite is anywhere and on any device! There’s no longer a need to create a virtual private network (VPN) to access corporate email, for example. For the majority of the users who do not recognize this – let’s be optimistic and add 'yet'! – it is all about change. So beyond whatever benefits IT/IS provides with these new tools, managing the change is key to success.
A transparent look at our process
Let’s look at the various steps the IT/IS teams and the digital user community went through. For the sake of being comprehensive, the Enterprise Social Network we use at ALE is Yammer.
1. Our first decision was to appoint a Moderator/Editor that would supervise all communications threads. We chose to enroll someone who had great and extensive experience in driving user communities on a corporate social network.
2. Then, Groups were created for each rollout domain – for example, Office 365/Yammer Support.Manuals and procedures were posted to prepare the user community for their migration work.
3. Users were requested to perform the migration of their Exchange mailbox including inbox, calendar and contacts in two steps within a very short period of time (2-3 days).
4. Users were able to report issues or request support through a dedicated email address – our new helpdesk was not yet deployed at that stage.
5. Additionally, employees could also post issues on Yammer where our Moderator, backed by the IS subject matter experts, proposed real time support. This was key for users to feel they were heard and their issues addressed.
Users also volunteered tips and tricks to improve other users’ experience. This was a true example of community engagement. And bingo, we succeeded! Step 6 helped the user community become a significant part of the rollout.
We also managed to improve user perceptions and feelings about the rollout and IT/IS support. One user who was very vocal was complaining that he would miss his quarterly sales quota with all these changes. Fortunately within days, he managed to see the benefits and he now holds a record for having O365 deployed and used on several devices.
For the non digital natives, and we have a few, it was a different experience. Their expectation was more along traditional modes of support: a hotline and even to some extent on-site support, which was not available for cost reasons. Post go-live support can be very expensive when you are geographically spread across many time zones on five continents, with many languages. They are also adverse to the use of threads and FAQs, or fail to find posted/shared information. Sometimes I wonder whether there is a barrier they can’t overcome to asking questions openly, but I won’t go into that territory.
In the end we had less than 12% of ALE employees logging incidents or requests thru the support mailbox, which took the organization a couple of weeks to clear. The main topics were user ID and password resets, or requests for creating generic mailboxes. On Yammer we had posts from the user community in the first few days of deployment covering at least 30 unique topics, much broader than the support email received. The response time on a Yammer thread was no more than 1-2 days. Even now, dialog continues as employees continue to share new tips with their peers.