Forum Discussion
Adoption roles
Hi Peter.. Just FYI this is not the adoption guide we are teaching from. We have an enhanced version that was released at Ignite that will be public and through all the Microsoft channels starting November 1st.
That's a great concern. Often times we see that users need more than training materials; they need to be inspired to approach and adopt the technology. From my experience, when you're planning an adoption effort, it is important to have a view that extends past your initial launch.
I like to think of Microsoft Adoption as a Program instead of a Project. Users don't know what they don't know. And that has a real cost associated to it.
There are probably many ways you can approach this. My challenge now is that I need some ball park figures for creating a high level "budget" for the business adoption. It's OK with a first guesstimate as the details will be given in the scoping, once we get a green light to start. Concrete examples (best practices) of adoption setups from successful implementations would be a great help. Of course this has to be adapted to our specific needs but it is always great to have something to start from.
- Hey Allan, if you just need some ballpark figures then take a look in the stakeholder deck I linked to :-).
Thanks, I will :-)
