Microsoft Teams & Yammer Enterprise Social: Better Together
Download as PPTX, PDF•7 likes•1,544 views
The document discusses the integration of Microsoft Teams, Yammer, and Outlook, emphasizing their roles in communication and collaboration within organizations. It highlights the differences in usage scenarios for immediate and delayed communication, audience size, and confidentiality approaches while suggesting strategies for effective collaboration and integrating tools. Real-world examples are provided to illustrate how to leverage these platforms for tasks such as requesting support, employee recognition, and announcing new initiatives.
Microsoft Teams & Yammer Enterprise Social: Better Together
- 2. @RHarbridge #SPSNH RICHARD HARBRIDGE My twitter is @RHarbridge, I’m super friendly & I am proud to work at 2toLead. CTO & MVP | SPEAKER & AUTHOR | SUPER FRIENDLY
- 3. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 4. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 5. INNER LOOPS & OUTER LOOPS Technologies serve a targeted purpose. For communication and connection while the content may be stored in SharePoint where we connect/communicate can shift. Outer LoopInner Loop Me We All Of Us SharePoint Files, Sites, & Content Collaboration Stream Video & Live Events
- 6. INNER LOOPS & OUTER LOOPS Brad Grissom had a great alternative and more detailed way of thinking about inner and out loops copied below and available at https://regarding365.com/where-work-gets-done-8d1d653ef48d.
- 7. YAMMER, TEAMS & OUTLOOK INSIGHTS High level definitions that dive a bit deeper than the loop model/explanation tool. Microsoft Teams Yammer Outlook Conversation Structure Microsoft Teams Channels Threaded Conversations Chats Yammer Groups Topics/Hashtags Threaded Conversations Chats Inbox Folders Threaded Emails Typical Urgency & Speed Immediate / Near Immediate Primary for instant communication and meetings - active daily use. Messages typically have immediate/near term value. Messages can lose value over time. Near Immediate, Delayed By Hours, Days Or Weeks While there is a chat/inbox and it can be responsive for Q&A scenarios – responses may not be as immediate. Messages typically gain value over time. Delayed By Hours Or Days The modern day voice mail. Marking as important/urgent may get a faster response, but typically responses are delayed. Messages typically lose value over time. Typical Audience / Group Size Small Designed for smaller teams where there is shared work or activities/responsibilities. Primary tool for 1:1 ad-hoc instant messaging. Large Organization-wide, cross- functional, cross departmental, departmental, and business unit. Ideal for communities. Additional reporting available for managing large audiences and groups. Any Typically not collaborative in nature and primarily used to schedule or inform. Used for 1:1, 1:Few & 1:Many discussions when the audience isn’t using Teams or Yammer.
- 8. YAMMER, TEAMS & OUTLOOK INSIGHTS High level definitions that dive a bit deeper than the loop model/explanation tool. Microsoft Teams Yammer Outlook Collaboration Approach? Real-Time Collaboration As the primary meeting facilitation tool in an Office 365 business as well as the primary place for teams to work this is the most collaborative communication environment for work today. Often also used to schedule meetings. Collaboration Via Discussion Typically not a real time collaborative environment and often not a place where collaboration on content occurs. It is often more focused on sharing of ideas, sharing of content, referencing content or collecting feedback/ideas from others and discussing content. Sequential Collaboration You can only email content and information and await a response, there is limited immediacy and it takes lot’s of effort to consolidate changes. Excellent for scheduling meetings. Typical Confidentiality Approach? Shared Ownership Typically this is a shared circle of trust. Viewers are also contributors by default. Content often has a sense of shared ownership. Shared Context & Often Public Often more for sharing openly, getting feedback outside a core team, or sharing across the organization. Many groups are (and should be) publicly open to a very large audience (often across internal org units/boundaries). Limited Ownership Often used for more confidential or secure communication (sometimes with rights protection) or may use with shared links to SharePoint content that is secured for limited audiences.
- 9. YAMMER, TEAMS & OUTLOOK INSIGHTS High level definitions that dive a bit deeper than the loop model/explanation tool. Microsoft Teams Yammer Outlook Typical Communication Approach? Ad-hoc Typically informal or project/team level discussions. Ad-hoc & Planned From corporate communications and leadership communications to ad-hoc Q&A. Mixed style and formality levels depending on the Group/Community. Typically more formal than Teams. Planned While ad-hoc communication happens here often it’s planned and in many instances a bit of formality is expected (e.g. signatures, etc.). More formal than Teams and often more formal than Yammer. Integration Options? All of these support access and sign on integration, and O365/AD group integration, quick IM and quick call via People Cards. Dependent & Highly Integrated With Office 365 • Can be associated with SharePoint sites. • Outlook can mail channels. • Yammer can post to channels. • Tabs and Connectors. • Chat Bots Integrated With Office 365 • Can be displayed on SharePoint pages (multiple web parts/styles). • Can be provisioned with SharePoint sites. • Outlook can respond to posts and mail Groups. Integrated With Office 365 • Outlook conversations can be provisioned with SharePoint sites. • Yammer and Teams can notify in Outlook.
- 10. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 11. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 12. MOBILITY MATTERS Both Microsoft Teams and Yammer have rich and powerful mobile experiences. Want a set of configurable and unified notifications? Your phone can provide that right now.
- 13. YAMMER & TEAMS INTEGRATION We can have Yammer posts show up in Teams to kick of internal informal discussion before providing the more formal answer, or to keep a team informed of important updates.
- 14. YAMMER & TEAMS INTEGRATION You can bring a Yammer feed into the Teams experience. Today via website – soon via a Yammer option for Teams. Above is a great suggestion by Simon: https://buildbod.com/2017/10/02/adding-yammer-feeds-to-a-microsoft-team/
- 15. YAMMER & TEAMS INTEGRATION More integration is coming with easy sharing from Yammer to a teams channel and more.
- 16. YAMMER & TEAMS INTEGRATION Over time powerful capabilities like search will better integrate these places people work.
- 17. CONSIDER INTEGRATING OR ENHANCING • Unify Teams notifications into your Intranet with the SharePoint framework. • Automate the provisioning of a new Project site by also setting up a link to teams conversations in SharePoint, adding appropriate tabs, Teams connectors and other Teams configuration to reduce manual effort and integration. • Improve navigation across teams by creating a great teams directory navigation experience with the SharePoint framework. There are always ways to improve and better align these tools and their capabilities with your own working environment or working needs. Unified Experience: Notifications
- 18. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 19. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 20. SCENARIO 1: REQUESTING SUPPORT • You might broadcast to your team if you believe your team knows the answer to get the fastest response. • If you know who might know you may also use Teams (or any O365 experience via the People card) to instant message that specific individual and/or @mention them. • Teams is more tightly integrated with Microsoft Planner and services like Trello or other task management solutions as well, so it makes the most sense to use Teams for content collaboration but Yammer to help identify collaborators who can help. We need to get support to a specific question, or help answering a question.
- 21. SCENARIO 1: REQUESTING SUPPORT • You might broadcast to a Group in Yammer if you believe one of the Groups knows the answer to get a response. • If you know who might know you may also use Yammer (or any O365 experience via the People card) to instant message that specific individual and/or @mention them. • Teams may even be configured and integrated to post into a Microsoft Team that actively works on questions/support requests. That team would still optimally respond via Yammer (for posterity). We need to get support to a specific question, or help answering a question.
- 22. SCENARIO 2: EMPLOYEE RECOGNITION • Often it’s best to start by creating a publicly visible note of praise in Yammer. This is because praise often should be recognized outside of your team/project. • When we highlight it in our next team meeting, or in Microsoft teams via an appropriate channel we can link to the Yammer praise post. That way comments and discussion on the praise is more broadly visible across the organization. Recognition matters and sometimes we want to find great ways to celebrate great work.
- 23. SCENARIO 3: ANNOUNCE NEW WEBSITE • You might have conducted the pilot and posted updates in Yammer highlighting progress, teasing new capabilities in the site, or coordinating and communicating with during the pilot or pre-launch. • You might coordinate and plan in Teams to confirm who does what, what the communication looks like, where you will announce, and when the communication will take place. After months of hard work you are ready to announce the new company website (or product, or customer portfolio/case study, or other similar situations).
- 24. SCENARIO 3: ANNOUNCE NEW WEBSITE • You might broadcast via email to provide a clear, formal and succinct summary of the new website and why it matters. In this model you would most likely use a BCC and/or classify it to not allow reply all. • You might post additionally in Yammer even if you emailed it to encourage discussion and feedback about the new site. In fact highlight that Yammer post in the email to give people a voice. After months of hard work you are ready to announce the new company website (or product, or customer portfolio/case study, or other similar situations).
- 25. SCENARIO 3: ANNOUNCE NEW WEBSITE • You might highlight it in the next Microsoft Teams meeting discussing the feedback captured in Yammer, the ideas suggested, and lessons learned from the launch. • You might share a broader update in Yammer summarizing the key feedback and learnings to further engage employees and foster discussion. After months of hard work you are ready to announce the new company website (or product, or customer portfolio/case study, or other similar situations).
- 26. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 27. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 28. EMBRACE TEAMS & YAMMER If you are a larger organization these two tools can provide an incredible set of combined experiences. Teams can only scale so much and Yammer fills that community gap. I LOVE YOU! I LOVE YOU TOO!
- 29. EMBRACE TEAMS & YAMMER If you are a larger organization these two tools can provide an incredible set of combined experiences. Teams can only scale so much and Yammer fills that community gap. BF? BFF!
- 30. EMBRACE TEAMS & YAMMER If you are a larger organization these two tools can provide an incredible set of combined experiences. Teams can only scale so much and Yammer fills that community gap. LET’S HUG! TOTALLY!
- 31. EMBRACE TEAMS & YAMMER If you are a larger organization these two tools can provide an incredible set of combined experiences. Teams can only scale so much and Yammer fills that community gap.
- 32. EMBRACE TEAMS & YAMMER If you are a larger organization these two tools can provide an incredible set of combined experiences. Teams can only scale so much and Yammer fills that community gap.
- 33. INNER LOOP & OUTER LOOP YAMMER & TEAMS INTEGRATION REAL WORLD SCENARIOS & EXAMPLES RECOMMENDED NEXT STEPS
- 34. Thank You! Microsoft,Sponsors,&YouForMakingThisPossible… 200+AwesomePresentationsAt.. Slideshare.Net/RHarbridge 300+PagesOfWhitepapersAt.. 2toLead.com/Whitepapers WhenToUseWhat.com Office365Intranets.com Office365Metrics.com Office365Campaigns.com Office365Extranets.com Office365Resources.com Message Me On LinkedIn or Email [email protected] CTO & MVP | SPEAKER & AUTHOR | SUPER FRIENDLY Let’s connect and find ways to do more and work together.
Editor's Notes
- #2: Organizations today need to be more responsive as people are more connected than ever. While many organizations understand the benefits social technology can provide it’s often not as clear how we can go about implementing these technologies to complement our organization’s investments in collaborative technologies like Yammer, Microsoft Teams, and SharePoint. Join Richard Harbridge as he shares practical, real-world guidance for enterprise social and the future of work. Richard explains how and where customers are investing in social, what is changing and important to understand, and what technology investments have been made and are being made by Microsoft to help customers connect and work in a cloud-first and mobile-first world.
- #3: Richard Harbridge is the Chief Technology Officer and an owner at 2toLead. Richard works as a trusted advisor with hundreds of organizations, helping them understand their current needs, their Soon needs, and what actions they should take in order to grow and achieve their bold ambitions. Richard remains hands on in his work and has led, architected, and implemented hundreds of business and technology solutions that have helped organizations transform both digitally and organizationally. Richard has a passion for helping organizations achieve more; whether it is helping an organization build beautiful websites to support great content and social strategy, or helping an organization leverage emerging cloud and mobile technology to better service their members or the communities that they serve. Richard is an author and an internationally recognized expert in Microsoft technology, marketing and professional services. As a sought-after speaker, Richard has often had the opportunity to share his insights, experiences, and advice around branding, partner management, social networking, collaboration, ROI, technology/process adoption, and business development at numerous industry events in around the globe. When not speaking at industry events, Richard works with Microsoft, partners, and customers as an advisor around business and technology, and serves on multiple committees, leads user groups, and is a Board Member of the Microsoft Community Leadership Board.