My company was recently acquired. The acquiring company uses Microsoft Teams.<p>I'm not excited about this. For those of you who have been on a similar transition, what tips or tricks do you have for:<p>* making Teams more effective as a communications medium
* being able to stay on top of recent conversations
* managing notifications/interruptions<p>Browser extensions? Specific settings you'd turn on or off? Open to any ideas at all here.
Right-click the Send button to schedule messages.<p>Turn off gif auto-loading.<p>Use @Everyone to notify everyone in a chat (versus channels).<p>Create a new chat to yourself as a pastebin.<p>Some bots can be @-mentioned personally, so you can try subcommands (like help docs) without pinging everyone in the channel.<p>When creating bullet lists, Shift-Enter can add to the current bullet. Nifty to paste a link, S-Enter, then include an explanation. Press Enter to start the next item.<p>Press ```<Space> to start a code snippet.
- Do not rely on teams to store useful messages. Search is hard.<p>Better to move such important info to a journal app like obsidian<p>- you can pop out chats into separate sub window. Use it for important chats<p>- teams channels are the worst thing I have ever seen and am forced to use. No one in right mind prefers it.
write to your future self: when you judge a message will need to be found, reply to it with a custom #tag. (#futureme-projectA)<p>later search for it.<p>Unfortunately, so far, did not find how to read local db to build parallel search index.
Microsoft Teams really sucks. It's one of the reasons I'm leaving my current company. I can't stand it anymore. We sometimes use a page with WebRTC to communicate to avoid it.<p>It's so unstable on a Mac, it always breaks, resets my configuration and leave me in bad place during meetings, all while wasting a lot of computing resources.<p>Maybe get a Windows computer if you want to be less frustrated, but you'll get frustrated by other reasons then.
One of the first options that open many doors is power automate, you add a lot of functionality that might make the transition easier.<p>we have one client that uses teams and basically uses power automate to repost all the messages to slack. So the MS side and the slack people both get what they want out of it.<p>There is a vast array of prefab templates<p>You can also do most of this via graph if you would rather, but I find both to be bit painful to deal with, with power automate the infrastructure is provided so there is that, but its largely designed to be a no code drop block style environment which limits its functionality.<p>Graph will give you a lot of control, and allow you to create things in a consistent manager, but the management of it, and time to develop often out way the value of the functionality.
The chat/channel/whatever list is horrible. You can't group anything and there is no way to search. It's just scrolling up and down in the unordered list to find something.<p>I thought Slack was bad but Teams is absolutely the worst. I don't have any tips to share, sorry.
1. uninstall Teams<p>2. install Slack or something else that doesn't have "Teams" in the name<p>Teams has reputation of being the worst team in the world. Don't rely on the worst team in the world.
You can't fix Microsoft Teams, only Microsoft can do that. It's wild to me how Microsoft, Slack and others have taken what has existed for decades, eg irc, and completely ruined it. In both applications the UX is horrid and search either doesn't work or is a terrible experience. Teams on Mac is so buggy you might as well uninstall it, your communication over teams will be just as effective as if it was installed.
Group chats for everything. Channels are horrible.<p>If you are on Linux install chrome and install Teams as a WPA. On Firefox i think its purposely made bad.
My health region is in the process of switching to using teams for paging so I am in a similar boat. Somewhat brutal for notifications and reliability.