Forum Discussion
When Adoption Goes Wrong
Asif,If nothing else your response drew people’s attention in showing the bad side of expecting training to be the Adoption answer, it obviously is not.
However, it MUST be part of the answer as the expectation that your 'mass' of end users will suddenly understand everything that is being delivered is probably not realistic. And also, how do you manage new applications as MS release them.
My response is that your view is correct but your statement is wrong.
Training is crucial, but like everything else in the adoption space it has to be done right with all training plans being based on a training needs analysis exercise. This then means that the training provided is as a request by the business and motivation to train is because the business see that the project is delivering the training in the formats and subject matter that they have been requesting.
So, training on its own is not the answer, but as a blended adoption solution it is a crucial part of the process.
Steve Dalby
Microsoft
Maddie_Egan wrote:
When Adoption Goes Wrong
Email is often approached as an easy “win” as everyone uses email, and it can be migrated over, mostly as a forcing function. But in migrating, one company changed the email address formats for all end-users. Specifically in email, maintaining as much consistency as possible across platforms is very important. We don’t recommend changing email addresses, unless you absolutely must.
What have you seen that didn’t work as planned? Any tips on what not to do when rolling out new product?
Would love to hear more adoption 'horror stories' from this group! What did you see as a adoption tactic 'fail'?
Conversely, what unconventional way have you seen working?
