High Value Scenarios for Microsoft Teams
1 like232 views
The document discusses high-value scenarios for Microsoft Teams, highlighted by Erica Toelle, a product evangelist for RecordPoint. It includes various use cases such as bridging communication loops, video conferencing, and integrating workflows while emphasizing the importance of organizational culture in user adoption. Additionally, it offers resources for learning and implementing Microsoft Teams effectively.
High Value Scenarios for Microsoft Teams
- 2. High Value Scenarios for Microsoft Teams Erica Toelle RecordPoint, USA
- 3. 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!
- 4. How Does Microsoft Teams Fit Into Office 365?
- 5. What are the Office 365 Collaboration Options? Source: Microsoft
- 6. Office 365 Collaboration Use Cases Source: Microsoft
- 7. Scenarios By Role Get the Microsoft Teams Role Guide Here! Microsoft Teams High Value Scenarios Source: Microsoft Teams PG
- 8. Source: Ron Markezich at Microsoft Ignite 2017
- 9. Wednesday, 11/15 from 2:00 – 3:00pm in room W19
- 10. Scenario #1: Bridge the Inner and Outer Loops
- 13. Microsoft Teams Video Meeting
- 14. Scenario #3: Use Microsoft Teams in a Workflow
- 15. 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!
- 16. Scenario #4: Track Tasks with Planner
- 17. Scenario #5: Build a Bot
- 19. 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
- 20. 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
- 21. Resources to Learn More https://aka.ms/SuccessWithTeams Your hub for all things Microsoft Teams including vision, practical onboarding guidance, success stories, and support. https://FastTrack.microsoft.com Assistance for customers to realize their vision with Microsoft cloud services Resource Link Office Blog https://aka.ms/OfficeBlog Office Roadmap https://aka.ms/OfficeRoadmap Product Help Known Issues List https://aka.ms/TeamsSupport https://aka.ms/TeamsKnownIssues Team Developer Hub https://TeamsDeveloper
- 22. @CITCTV
- 23. THANK YOU! Erica Toelle me@ericatoelle.com Twitter: @EricaToelle