In my most recent blog post we discussed some scenarios expressing of the importance of organizational change management (OCM) in an Office 365 (O365) implementation. This post will focus on the approach for change and adoption of O365.
An organization must be ready, willing and able for the change and adoption of Office 365.
We take you through 10 best practices, considerations, and suggestions that can enrich your Microsoft Teams deployment and ensure both end-user adoption and engagement.
A proven approach for change hinges on 4 simple concepts:
- Define the Change – Answers the question of ‘Why”
- Communicate the Change – Answers the question of “Who, What, and When”
- Enable the Change – Answers the question of “How”
- Sustain the Change – Embeds change capabilities in the organization
Below are 5 keys to ensure the successful adoption of office 365:
- Organizational Change Management (OCM) Quick Start – Embark on a change management program by developing a case for change, performing a stakeholder analysis, and creating a communication and training plan.
- Stakeholder Engagement – Build and maintain relationships of trust and actively engage key stakeholders to ensure buy-in and support.
- Communication – Strategic and tactical messages tailored to meet needs of each audience and delivery mediums – Town Hall, email, demos, posters, blogs and FAQ.
- Training – Just-in-time learning resources including instructor-led, web-based, and train-the-trainer options and custom reference materials.
- Sustainment – Ongoing reinforcement to integrate change into culture, policies and procedures.
For more insight on how organizational change management boosts adoption of Office 365, download our guide here or below.
About the Author
David Chapman serves as General Manager and Chief Strategist for Perficient’s Organizational Change Management practice. He has more than 20 years of management consulting experience, specializing in the change management discipline. David brings his unique insight to the people aspects of any change from technology implementations to broader strategic organizational imperatives.