{"id":8808,"date":"2024-08-28T17:08:46","date_gmt":"2024-08-28T16:08:46","guid":{"rendered":"https:\/\/www.markwilson.co.uk\/blog\/?p=8808"},"modified":"2024-08-28T17:31:06","modified_gmt":"2024-08-28T16:31:06","slug":"how-to-communicate-in-teams-channels-or-chats-standard-private-or-shared","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2024\/08\/how-to-communicate-in-teams-channels-or-chats-standard-private-or-shared.htm","title":{"rendered":"How to communicate in Teams: channels, or chats; standard, private or shared?"},"content":{"rendered":"\n

Love it or loath it, over the last few years Microsoft Teams has emerged as the dominant collaboration tool for companies, large and small. But, let’s face it, how much has the typical organisation invested into getting the most out of Teams? The same can be said for most of Microsoft 365 – we buy the licences and expect people to just get on and use it. <\/p>\n\n\n\n

I could, and probably should, write a post about technology adoption, but this one is about Teams. Specifically about when to create a chat and when to use a channel. And what sorts of channels to use when. And if you want a post about technology adoption, here’s one I wrote several years ago<\/a>…<\/p>\n\n\n\n

You see, a few weeks ago, I was fortunate enough to attend the Commsverse conference. And one of the talks I found insightful was Robert Mulsow (in\/robert-mulsow<\/a>)’s “How to select the right communication in Teams: Feedback from the field”.<\/p>\n\n\n\n

What’s the problem?<\/h2>\n\n\n\n

Teams has two forms of text-based chat:<\/p>\n\n\n\n

    \n
  1. Chats, created from a conversation. Informal. Ad-hoc. No real management.<\/li>\n\n\n\n
  2. Channels, created as a shared space within a Team. Designed to scale, supported by SharePoint.<\/li>\n<\/ol>\n\n\n\n

    My (organisational) team has both! And no-one knows where to post:<\/p>\n\n\n\n