If you want to bring the entire team’s attention to a post without taking half a second to think about which Team you are actually using, you can use @team instead. @team will resolve to whatever Team into which the message is posted. These shortcuts are only available in Teams channel conversations – typing @team in a private chat won’t do anything.

There’s a shortcut for the current channel too — @channel

The message text is the same using @team and @channel or typing the actual team and channel name.

There are times when a question for a specific individual can be asked in the channel conversation by @mentioning the individual. But sometimes the question isn’t for general consumption … and sometimes I a message reminds me of something completely different that I need to tell someone. But switching to ‘Chat’ to send a message and then finding my way back to the channel conversation is time consuming. Did you know you can send a private message from the search bar?

Hit Ctrl+e or click in the search/command box along the top of the Teams window.

Begin typing an @Mention – either select the proper individual or type enough of the name that there’s only one …

Now you can send a message to the selected person right from the search bar.

Type your message – this is a quick text message, there isn’t typographical emphasis, colors, cute pictures – markdown doesn’t even render. But I can send a quick message without losing my place within the Channel conversation! Hit send (enter or the little purple circle at the end of the dialog box).

You’ll see a confirmation that your message was sent (and you can view the message in your persistent chats). And you can get right back to what you were doing 😊

There are a few posts to which I frequently refer – support contacts for a product, time reporting codes to use for our projects, etc. These posts aren’t updated frequently, so looking for them takes some scrolling. Searching for the post helps, but I still find myself scrolling through a dozen results.

You can save a post for later – essentially add a bookmark to the post – by clicking the little ribbon in the upper right-hand corner of the post.

To access saved posts, click on your avatar in the upper right-hand corner of Teams and select “Saved”.

Or, if you prefer to keep your hands on the keyboard, use CTRL + E to move to the command bar and type /saved

Either method brings you to the same place – your saved posts.

Do you know … if you should create a new Team or new Channel?

It’s certainly a good idea to break topics into different locations in Microsoft Teams – cognitive research on how efficiently people multi-task suggests this, it’s easier for non-impacted individuals to ignore information that’s not relevant to them if it’s not interspersed with information they need, and spreading topics out reduces the frequency of posts – ten new conversations don’t appear while you’re reading a thread. But should you create a new channel or a new Team?

There are a few technical limitations that make “Team” generally the right answer. Each channel in a Teams space has the same permissions – if you want to restrict access to confidential information or if you want to involve additional people – people who don’t need access to your other channels, you need to create a new Team.

You can archive a Team, but you cannot archive a channel. If you create a new channel for every project, your Teams space can become cluttered with old projects. The channels get collapsed into a “more channels” fly-out, but I still find myself renaming channels “zzSomething Or Other” to get really done projects sorted to the bottom of the more channels fly-out.

You cannot move a channel into another Team. If the project moves to another group (such transitions are common in IT – there’s a development/implementation phase, then the project moves to production support under a different group) … there’s no way to transition the information in a channel to another group. Even if that’s not standard operating procedure in your organization, reorgs happen. A supported system becomes big enough to warrant its own group or staff is re-aligned –having the historic knowledge of the Teams discussion available to the new organization is beneficial. (Not to mention, if you could move a channel into another team, you could indirectly archive channels by moving them into an archived Teams space!)

There are some scenarios where a new channel makes sense – that daily e-mail chain where people decide where to eat lunch could become a channel. There’s no reason to move the historic restaurant selection to another group – or, for that matter, retain it. If group lunches become ‘not a thing’ – just delete the channel. And anyone not heading to lunch today can ignore the channel. Similarly, “Water Cooler” discussions – a place where the comradery we took for granted when sitting in the same physical space can re-emerge – make sense as channels.

We’ve been using Microsoft Teams for most of this year, and I find it to be an incredibly efficient way to work. That’s not just a personal preference — years ago, I followed research on how human brains multi-task. TL;DR? Rarely well! Performing multiple natural activities, those that don’t put much demand on the prefrontal cortex, did not greatly diminish efficiency (I can walk and chew gum at the same time!). But fMRI scans performed by the Institut National de la Santé et de la Recherche Médicale in Paris showed that the prefrontal cortex has a left and right side which cooperate to focus on a single task but work independently when the subject was given two tasks. And when the subject was given three tasks? The rate at which a task was forgotten increased and errors were three times as likely for the tasks that were performed.

The recommendation was to dedicate chunks of time — 20 or 30 minutes — to a particular subject, then move on to a new subject rather than bounce back and forth between topics. Sounded great in theory, but each morning I’d sit down and start going through e-mail. The epitome of rapid topic shifting — read through something, switch to the next message/topic, maybe do a little work on that topic, go to the next one.

Starting my day in Teams is completely different — any channel that has had activity is bold. I can click on a channel, finish everything related to that topic, then move on to the next channel. Instead of jumping from topic to topic, and wasting time mentally “shifting gears”.

During a busy day, multiple channels light up with activity … but having each topic contained to its own location helps me maintain focus on that topic. Extrapolating — it makes sense to create a new channel or team for different projects instead of having multiple projects discussed within the same channel.

Sometimes a project is done. You’ve used Teams to plan, coordinate, and implement the projected … and there’s a lot of good information in the Teams space … but there’s no need to continue the discussion. Did you know a Team can be read-only? This is called “Archived” – members can search and read content, but no new files or posts can be created.

To archive a Team, view your Teams. At the bottom of the Teams list, click the little gear.

I recommend changing the Team description to let others know it is archived – this is especially valuable if your team is Public as people may join intending to participate in an active discussion. To modify the Team description, select the sideways hamburger menu next to the Team name and select “Edit team”.

I prefix the description with “ARCHIVED:” … hoping people at least glance at the description. Click ‘Done’ to save your change.

To archive your Team, click the sideways hamburger menu again. Select “Archive team”.

You will be asked if you want to make the SharePoint site for the Teams space read-only as well – the answer is generally yes, but if you’re using the SharePoint site for more than just the Team then you do not want to check this box. Click ‘Archive’ to archive the Team.

Should you need to begin accepting new content in your Teams space, you can find the archived teams by expanding the “Archived” section.

Click the sideways hamburger menu and select ‘Restore Team’. This will move your Team back to the “Active” section and allow members to continue posting content.

Several offices ago I sat across from a L.O.U.D talker. A loud talker who was constantly on a conference call. I’d try to remember to mute my line before joining a bridge but didn’t always remember. Random background noise isn’t so bad when you’re about to talk to two or three close colleagues, but background noise becomes inundating when the twenty-something people in my department all join a bridge.

Microsoft Teams helps you avoid a deluge of background noise in your call. When you join a “large” meeting –more than five people already in the meeting – your microphone is muted as you join. A notification is displayed prior to joining the meeting to remind you the microphone will be muted.

You can click the microphone button in the meeting control bar to un-mute your microphone and begin speaking.