Teams is a very powerful tool. But there are many common mistakes I have observed across customers. Here is a list of 50 mistakes – or – worst practices. Make sure you are not committing these Teams mistakes.
This is just a list. I will expand on some of these mistakes as separate articles or videos. If you do not understand a particular topic or have a different opinion, please post it as comments.
This list is in no particular order.
User level Teams mistakes
These Teams mistakes are mainly due to lack of awareness about features and also due to lack of guidance about which feature to use when.
- Continuing to misuse Inbox in spite of using Teams
- Starting a new conversation instead of choosing reply
- Too many notifications ON
- Banner notification is ON
- Using Chat instead creating a Team and vice versa
- Not synchronizing Teams files to local drive
- Creating too many Channels
- Creating too many private Channels
- Forgetting that there are external guests and posting confidential content
- Using Teams chat for unofficial purposes (forgetting that everything is archived)
- Not realizing that Teams chat and conversations are legal evidence (just like email)
- Using Teams for files which should ideally go into OneDrive (and vice versa)
- Creating Teams instead of Channels
- Creating Private Channels instead of Teams
- Not using Planner for shared task list (continuing to use Excel or something else)
- Forgetting to check updates in other Tenants
Thanks Ajay Sanglikar , Technology Strategist, Microsoft for pointing out the duplicate item. Corrected it now… and added another item instead (see no 29)
- Synchronizing only a sub-folder locally (instead of the full document library)
- Not using blur background during a video call (if the background is distracting)
- Not doing a test call to check audio and video BEFORE joining every meeting.
- Not putting yourself on mute while in a call / meeting
- Not informing all team members that meeting recording is available for future reference right within Teams
- Not realizing that the meeting recording is accessible by ALL team members (not just the ones who attended the meeting)
- Not knowing / using the transcript and people timeline feature of stream – which can give you automatic notes and allow you to jump to a particular person speaking
- Not knowing / using voicemail facility during a missed call
- Not noticing the swipe-up menu on the mobile app
- Now knowing that you can see a list of all tasks assigned to you in the Planner – My Tasks tab
- Not knowing that Planner tasks can be seen in Outlook calendar automatically
- Not noticing the … (ellipsis). These mean more options in today’s modern and mobile app type of user interface.
- Not noticing the Plus sign (add a Tab button) in each channel
- Keeping people hanging in the lobby while joining the meeting
- Not using direct photo capture from Teams mobile app (This is safer as the photo is not stored locally in the mobile device at all)
Thanks Pooja Rastogi (Microsoft) for the suggestion.
IT level Teams Mistakes
These Teams mistakes are primarily due to lack of understanding that Teams (and Office platform) is designed for enabling people to do more and better rather than for restricting what they can do. Restrictions are often put in an unreasonable and unwarranted manner – just because that is the way IT works. This approach leads to poor adoption, and eventually pathetic ROI.
- Not allowing users to create Teams
- Blocking External Sharing
- Blocking GIFs and Memes
- Not installing Teams mobile app
- Not installing Planner and ToDo apps
- Just focusing on Teams – not on OneDrive (and the rest of the platform)
- Continuing with traditional File Shares and Mapped Drives
- Blocking all add-ins and connectors
- Focusing too much on developing bots / LOB integration (while ignoring the base Teamwork)
- Not enabling Channel email IDs
- Not implementing banned word list
- Not implementing automatic governance policy for managing unused Teams
- Using SharePoint in places where Teams is more suited
- Using Yammer in places Teams is more suited
- Not focusing on Information Protection and focusing too much on Private Channels
Adoption related Teams mistakes (if any)
- Not having a long-term approach (only launch-centric plan)
- Not having a budget for adoption
- Not involving senior management in adoption efforts
- Not standardizing common usage practices
- Not knowing / using the Teams Broadcast feature for driving adoption through senior management
Here is a series of Teams articles I have written so far.
13 at the time of writing this article.