1. Employee engagement Close out presentation

2. Agenda Introduction Engagement overview
Vision, Launch and success plan
Next steps and Actions 1 2 3 4

3. Close-out Presentation
Example
Close-out Presentation
The purpose of this meeting is to:
Review vision, objectives and engagement approach
Review and agree on recommendations and roadmap
Discuss and agree on next steps and actions

4. Engagement Overview

5. Employee engagement envisioning workshop
Phase 1
Kick-off
Phase 2
Workshop
Phase 3
Recommendations
Project scope
Outcomes
Timelines
Team
Stakeholders
Understanding value
Explore scenarios
Prioritize a scenario
Build launch and success plan
Summarize findings
Provide recommendations
Provide gaps and dependencies
Build high level roadmap

6. Timelines, duration and effort
Example
Timelines, duration and effort
Important
Effort & duration may vary depending on the scope of the engagement, customers commitment and the partner readiness
We are here
Estimated duration 2-3 weeks
1-2 hrs.
2 days
2 hrs.
Engagement start
Kickoff meeting
Customer preparation
Secure executive sponsor and align resources to complete the envisioning workshop
On-site workshop
Conduct the employee engagement on-site workshop.
Present & Recommend
Analyze findings and prepare recommendations.
Present the findings, discuss recommendations and next steps. Deliver prioritized roadmap

7. Launch and success plan

8. Current State Example Email distribution list Intranet portal
Current employee engagement channels
distribution list
Intranet portal
Newsletters
All hands meeting
Challenges with employee engagement channels
One way communication
Lack of feedback loop
Lack of mobility support
Lack of archive and playback

9. Vision statement Example Organization’s core values
Organization’s business initiatives for this fiscal year
Vision statement for employee engagement
Bullets
Bullets
Bullets

10. Desired business outcomes
Example
Desired business outcomes
With your vision in mind, put together a list of business outcomes that executive engagement can help your company achieve.
Your of Business Outcomes
Department 1
Department 2
Department 3
Business Outcomes
Business Outcomes
Business Outcomes

11. Key Stakeholders Example
Microsoft Office
2/16/2019
Example
Key Stakeholders
Fill in the table below with the details of your stakeholders. Some roles may be filled by the same people.
Role
Responsibilities
Department
Name(s)
Project Manager
Oversee the entire launch execution and rollout process.
Community Manager
Manage day-to-day network activity; provide guidance and best practices.
Executive Sponsor
Communicate high-level vision and values of executive engagement to the company.
Power Users
Help train users and manage objection handling.
IT Specialist
Oversee all technical aspects of the rollout, including integrations.
Business Owner
Provide guidance, approval and support throughout the overall rollout.
Group Leaders
Senior leadership roles who would actively engage in answering questions, sharing updates and discussing initiatives
Education Lead
Manage and communicate training content about Yammer.
Communication Lead
Oversee company-wide communications about Yammer.
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

12. Your Launch Plan Example
Microsoft Office
2/16/2019
Example
Your Launch Plan
Select communications and events for your launch and organize them here in chronological order. Below is a sample timeline that can be adjusted for your organization.
Time
Communication or Event
Owner(s)
Status
Now
Meet with stakeholders to define you vision, identify business outcomes & develop use cases.
Create a Yammer Help Group and upload educational content.
Create a Yammer Ideas Group. Throughout the launch process, encourage your coworkers to share ideas here about how Yammer can help improve work processes at your company.
3-4 weeks before launch
Send executive introduction.
2 weeks before launch
Send department introductions via .
Notify your company about the launch YamJam, trainings and Lunch & Learn.
1 week before launch
Remind your company about the launch YamJam, trainings and Lunch & Learn.
Week of launch
Host training with first high-priority department.
Host training with second high-priority department.
Host training with third high-priority department.
Host Lunch & Learn.
Host YamJam.
Link to YamJam Documentation
© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

13. Success criteria Example Success criteria Method/source Metrics
2/16/2019
Example
Success criteria
Success criteria
Method/source
Metrics
Example goal
Increased adoption
Increased usage correlates to user adoption of the technology.
Quantitative
Office 365 reports
Mailbox usage
SharePoint usage
Skype IMs and conferences
Minutes of Skype audio used
Comparison of pre and post-rollout usage reports will show increasing adoption of 10% per month.
Training effectiveness
Increased usage correlates to training effectiveness.
Qualitative
End-user surveys
Yammer groups and feedback
Employee satisfaction
Comparison of pre and post-training usage reports will show increasing adoption per month.
Employee net user satisfaction score is 130+ based on the final training survey.
Reduced operating costs
Increased adoption correlates to reduced third-party conferencing usage, travel time, and resource allocation.
Office 365 reporting
Finance/accounting reports
Help desk reports
Travel and phone expense reports
Output measures
Audio conferencing billing and usage
Travel and phone expenses
Help desk calls
Comparison of pre and post-Office 365 reports will
\show cost savings.
Post-rollout usage of third party phone conferencing should show decreasing usage of 10% per month.
Increased productivity
Increased adoption correlates to faster communication and decision making, shorter time to complete tasks.
Time required to complete projects
Time to complete customer orders should drop by 15% within 6 months.
Improved collaboration
Increased cross-team and cross-location communications.
Time saved
Teams that work from multiple locations will report improved feelings of connection with their teammates within 3 months of the Skype rollout.
Improved employee satisfaction
Flexible working options improve employee satisfaction through increased engagement, reduced stress, improved work-life balance.
Employee satisfaction improves by 15% within 6 months.
Here are sample success criteria goals and metrics.
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

14. Next Steps and Actions

15. Next Steps and Actions Example Party Responsible Completion Date
Next Step, Action
Notes