Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

High Value Scenarios for Microsoft Teams


Published on

Microsoft Teams is a collaboration tool that empowers teams to work together more effectively, providing persistent chat and a user interface that ties together multiple Office 365 tools. In this session, we will discuss where Teams fits in the Microsoft collaboration toolkit, and review Teams scenarios that have been proven to provide value in real life situations. We will then discuss lessons learned from organisations that have been using Teams and have deployed it throughout their organisations.

Benefits of Attending this Session:

Identify high value scenarios for Microsoft Teams
Hear real life stories about what has worked for organisations and what has not
Understand where Teams fits in your collaboration toolkit

Published in: Technology
  • Be the first to comment

  • Be the first to like this

High Value Scenarios for Microsoft Teams

  1. 1. High Value Scenarios for Microsoft Teams Erica Toelle RecordPoint, USA
  2. 2. About Erica Product Evangelist for RecordPoint based in Seattle, USA • Started using Microsoft Teams in August 2016 • Consulted for the Teams Product Group to identify high value scenarios for Microsoft Teams • Led the Microsoft Teams pilot at Expedia and Trek Bicycles • …And I love Microsoft Teams!
  3. 3. How Does Microsoft Teams Fit Into Office 365?
  4. 4. What are the Office 365 Collaboration Options? Source: Microsoft
  5. 5. Office 365 Collaboration Use Cases Source: Microsoft
  6. 6. Scenarios By Role Get the Microsoft Teams Role Guide Here! Microsoft Teams High Value Scenarios Source: Microsoft Teams PG
  7. 7. Source: Ron Markezich at Microsoft Ignite 2017
  8. 8. Wednesday, 11/15 from 2:00 – 3:00pm in room W19
  9. 9. Scenario #1: Bridge the Inner and Outer Loops
  10. 10. Scenario #2: Video Conferencing
  11. 11. Microsoft Teams Video Meeting
  12. 12. Scenario #3: Use Microsoft Teams in a Workflow
  13. 13. User Story: “User submits new observation/insight. Which is saved in register. Based on lesson type it is posted to relevant community team channels via connector. Issue is discussed among SME’s via Teams app and observation is upgraded to candidate lesson”. As new insights are logged the SME’s may choose to create entirely new lesson based on multiple insights Solution Credit: Paul Clumsee Learn more here!
  14. 14. Scenario #4: Track Tasks with Planner
  15. 15. Scenario #5: Build a Bot
  16. 16. Create Your Own FAQ Bot Resource: Create Your Own FAQ Bot in Less Than an Hour Create a Q&A Service Build Bot & Connect to Q&A Service Connect Bot to Teams Channel
  17. 17. Lessons Learned • Adoption depends on your culture • Start with one feature that addresses one pain point & add more each week • Don’t worry too much about information architecture • Collaboration tool fatigue is a real thing • Change champions are not optional • Use Teams to support change champions • Replace Slack with Teams…maybe
  18. 18. Resources to Learn More Your hub for all things Microsoft Teams including vision, practical onboarding guidance, success stories, and support. Assistance for customers to realize their vision with Microsoft cloud services Resource Link Office Blog Office Roadmap Product Help Known Issues List Team Developer Hub https://TeamsDeveloper
  19. 19. @CITCTV
  20. 20. THANK YOU! Erica Toelle Twitter: @EricaToelle