This document outlines 7 key elements for a successful Microsoft Teams strategy: 1) having a clear vision, roadmap, and business goals; 2) executive sponsorship and engagement; 3) a governance plan for provisioning, lifecycles, security, etc.; 4) defining quality metrics and KPIs; 5) identifying clear business outcomes; 6) an adoption change management plan including champions; and 7) a training plan and app development plan focusing on personas and user stories. The document provides guidance and best practices for planning a Teams rollout and strategy to maximize success and value.
3. Poll: Where
are you in your
Teams
Adoption
•Using Skype but plan to
migrate
•Using Both Skype & Teams
•Pilot of Teams
•Teams for Unified
Communications and
Collaboration
•Not Started
This Photo by Unknown Author is licensed under CC BY
4. 7 Critical
Elements for a
Successful Teams
Strategy
Clear Vision,
Roadmap &
Business Goals
Exec Sponsor
&
Engagement
Governance
Plan
Quality
Metrics KPIs
Clear Business
Outcomes
Adoption
Change
Management
+ Champions
Training Plan
& Office
Hours
AppDev Plan:
Personas and
User Stories
@joeloleson
5. Clear Vision, Roadmap and
Goals
This Photo by Unknown Author is licensed under CC BY-SA-NC
8. The future of digital working will offer tools that let us tie
communications, content, tasks, applications, collaborative work
and other elements together around work streams. – Efraim
Freed 2015
11. Teams is the Center of Digital Transformation
Modern Intranet
UC: Voice, Video, Comms
Documents & Files
Modern Content Services
Business Process
Modern Chatbot
HR & Service Desk
Predictive
Global Search
Communication
Collaboration
Engagement
AI and Machine Learning
Line of Business Apps
IoT Analytics
Alerting & Monitoring
12. Governance Plan:
Provisioning, Lifecycle, Offboarding,
Security & Compliance, Data Loss
Prevention, RACI
(This is not just a document…)
This Photo by Unknown Author is licensed under CC BY-SA-NC
13. Chaos by default…
Governance critical to success…
• Who can create a Team?
• How do we intend to use Teams?
• What should NOT be used or connected to Teams?
• How long should they exist before archived or validated?
• Naming conventions?
• Teams templates?
• Who owns the platform? Who owns the data? RACI required.
• What if a flow could create and validate services, security, auditing, DLP
policies blocks and warnings, and usage reporting?
• How should a Team be provisioned? Powershell, UX, Admin, Graph
• How are new features rolled out and discovered or disabled who is
watching?
This Photo by Unknown Author is licensed under CC BY-SA-NC
19. Success Criteria & Metrics
Desired Outcomes
This Photo by Unknown Author is licensed under CC BY-NC
20.
21.
22. Adoption Change
Management & Champion
Program
This Photo by Unknown Author is licensed under CC BY-SA
Only 34% willingly adopt new technology
23. Deployment
Technical
migration and
deployment
Activation
People See new
features but don’t
know what to do
with them.
Awareness
People know
about the change
and are aware of
how to get help
Enablement
People use the
solution on a
regular basis
Proficiency
People change
their behaviors and
leverage the full
solution
MS Teams Maturity & Value Model
Value/ROI
Time &
Difficulty
often achieved poorly achieved rarely achieved
25. Poll: How are
you using
Teams in Your
Organization?
•Project Teams
•Departmental Teams
•Executive Engagement
•Support – Screen Sharing
•Events - Live Video
This Photo by Unknown Author is licensed under CC BY
26. Poll: How do
you plan to
Use Teams in
the Future?
•Project Teams
•Departmental Teams
•Executive Engagement
•Support – Screen Sharing
•Events - Live Video
This Photo by Unknown Author is licensed under CC BY
27. Training Plan: Train the
Trainer & Office Hours
This Photo by Unknown Author is licensed under CC BY-SA
31. Dev and App Plan
Personas, Team Stories
This Photo by Unknown Author is licensed under CC BY-NC-ND
32. Microsoft Teams provides a powerful and
extensible platform
Build apps with a rich set of capabilities to reach
your users through chat, channels, notifications and personal
workspace.
Integrate with new or existing business processes and services
Connectors
Post rich updates to channels
Activity Feed
Engage users via feed
notifications
Bots
Help users get tasks done in
conversations
Adaptive Cards
Add rich interaction to your
connector cards
Message Extensions
Allow users to query and share
rich cards in conversations
Tabs
Surface rich content as well as
SharePoint Framework* based
solutions
Build in intelligence and connect
to data that drives productivity
Microsoft Graph App Store
Drive engagement by
submitting your app to our app
store or just to certain company
stores
Most popular!
Low-code/No-code options are available!
35. Recap: 7 Critical Elements for Successful Teams Strategy
Clear Vision,
Roadmap &
Business Goals
Exec Sponsor
&
Engagement
Governance
Plan
Quality
Metrics KPIs
Clear Business
Outcomes
Adoption
Change
Management
+ Champions
Training Plan
& Office
Hours
AppDev Plan:
Personas and
User Stories
Stress the end results and outcomes. PRFT is driving Proficiency on the platform. Most are driving adoption…
Teams applications can add a number of features to the Teams UI
Tabs and Bots are the two most important, and both are possible using low-code/no-code solutions
With the addition of code, you can add even more; some of our upcoming workshops go deeper into the coding and discuss these other options.
******************************************************************************************************************************************************
Tabs allow you to surface rich content within Teams, so you can bring the tools and services your team cares about right into a channel or private chat. Add rich dashboards and data visualization, collaborate on documents and note taking, manage tasks across the group, and share designs.
Bots help users get tasks done in conversations in Teams. Bots can do things like kick-off workflows and provide related status, give and receive kudos from team members, create lightweight surveys to gauge employee satisfaction, and answer natural language questions about sales and customer usage data.
Connectors help bring useful information and rich content from external services into channels in Microsoft Teams. Get social media notifications, updates about pull and push requests, and news updates.
With Actionable messages, you can add rich content to your connector cards.
Message extensions allow users to query and share rich cards in conversations.
Activity feed notifications engage users via feed notifications.
To learn more about the Teams developer platform, visit the Office Dev Center at Developer.Microsoft.com/Microsoft-Teams.
And with this rich set of capabilities, many the result of partner feedback, it has opened up significant opportunities for you as partners to create a very wide range of customized solutions for your customers.
There is a spectrum of options for extending Teams.
There’s a tradeoff here … From left to right each option requires more technical expertise and usually more work, and gives you more potential features and flexibility
You can:
- use applications from the Teams store – check it out! There’s a lot already there!
- use low/no-code options like PowerApps, Flow, and even QnA Maker bots
- begin from an open source reference solution (make sure you have the ability to support it!)
- start from scratch with completely custom development