• thecloudblogger

Microsoft Teams Blog Series

Magic or Mayhem for Your Organization?


The Magic


When I first learned of Microsoft Teams, I thought, Skype and SharePoint had a baby and they’ve named it Microsoft Teams. MS Teams has everything you’ve ever wanted in a virtual communication tool. It offers the ability to conduct private chats just as you would in SKYPE or group chats or video with your team. In addition, Teams offers a platform to collect, store, and share documents, a calendar to manage schedules related to a specific project. I know, I know. This sounds familiar. As I said, they had a baby.


MS Teams is a great way to allow departments within your organization to collaborate without requiring admin privileges to a SharePoint site collection to create a site or having to a submit a help desk ticket to have a site created for you – whatever your organization’s governance dictates. (Wait, you do have a governance policy, right? Okay, let’s not go there just yet. We’ll come back to that later in the series.)


MS Teams is a huge step up for collaborating within your organization with Teams and Channels no matter how dispersed your staff. The video and chat feature afford remote teams the ability to collaborate and brainstorm in real-time just as if they were in the office. Teams provide the structure for a specific group or groups to collaborate on a project.


Let’s say the Sterling Cooper Draper Pryce Advertising Agency is working on a marketing project for its client, Pope & Associates. They can be private, open to the entire organization, or public but still managed by permissions. Within those Teams are what is called Channels which provide a means to compartmentalize the details of your project more granularly or breakdown your teams into even smaller groups while keeping everything organized under the same project. So, in our example, there could be several Channels such as Art, Production, Social Media, Multimedia, and Print.



As a consultant in the Washington, D.C. area, I’d be remiss, (and let’s face it, downright rude) if I didn’t include an example for my beloved and fellow government contractors. So, it’s October 15th and you’re working on proposal number 2,476 for the fiscal year 2020. MS Teams would be an easy, efficient, and streamlined way to collaborate. Picture Blue, Pink, Red, Green, Gold, and White Teams as actual MS Teams with individual Channels for each person to contribute their pieces of the JUMANJI puzzle known as the RFQ.



But this is a huge RFQ and it’s not just your company working on the proposal. Your company and representatives from 4 other subcontractors will be contributing to the proposal. How will you all collaborate using MS Teams without compromising proprietary company data to external contributors? I’ll address this issue and more and it will cover both public and private sectors, in the next post!


Thank you for reading! Stay tuned for more topics in the series:


- Cross Collaboration With External Users

- MS Teams in the Government

- Architecting and Governing Your MS Teams


I’d love to hear your feedback and experience with MS Teams in the meantime. 😊


Quote of the week: “Perpetual optimism is a force multiplier.” – Colin Powell

  • LinkedIn Social Icon
  • Facebook

16701 Melford Blvd., Suite 400

Bowie, MD 20715

(202) 505-5305