Assess company-wide change impacts – Google Apps for Work User Manual
Page 49
Change Management Guide
49
Phase 1: Core IT
Assess company-wide change impacts
Time frame: Weeks 2–4
What are change impacts? Change impacts are things that will be
different once your organization switches to Google Apps—updates
to business processes, applications or policies. Tracking these
changes helps prevent foul-ups and needless duplication—and you
can identify opportunities as well.
Start with your project team: Many of these changes depend on the
technical decisions and scheduling. Work with the team to identify
changes that affect your user community with the move to Google
Apps. A few common change impacts:
•
Legacy email application access: How will users access your
legacy email application? Can they forward and archived email,
and for how long? You’ll want make these policies clear to users.
•
Delegated mailboxes: Will you be migrating shared or delegated
mailboxes? How will users know how to access these accounts?
•
Shared or team calendars: Will these types of calendars be
migrated to Google Apps? How will users learn to access them in
Google Calendar?
For each of these changes, you’ll determine how to communicate a
new policy or procedure, how users will learn the updated procedure,
and what training could be helpful.
The result: A list of key company-wide changes resulting from the
move to Google Apps, and a set of actions to address through
training and communication to your users.
“Compiling a list of change impacts
with the client helps us to identify their
expectations and any key changes. This
information allows us to successfully
convey and prepare users for the
transition through both training and
communications.
Our goal is to have new users informed
and ready to work effectively on day one
in Google Apps.”
—
Jennifer Calderone, Training
and Knowledge Management,
Tempus Nova