Microsoft Teams

Joining a Teams meeting is the most common Microsoft 365 task most people do daily. Knowing the basics, plus the small things most people skip, makes meetings feel professional rather than chaotic.

Joining a Teams meeting sounds basic — and at one level, it is. Click the link, click Join, and you’re in. But the small details around joining are where meetings go right or wrong. Audio settings, video on or off, blurred background, the right device chosen, joining a few seconds early to test things — these tiny choices shape whether you arrive prepared or scrambling. Most people pick up the basics in their first week and never refine; the difference between competent and confident is usually about four small habits.

There are three ways to join: from the Teams desktop app, from a browser, or from a mobile device. Desktop is the default for serious meetings — full features, best audio, screen sharing works properly. Browser is the fallback when you’re on a borrowed device or guest tenant. Mobile is for travel and emergencies, not main attendance — small screen, harder to share, harder to multitask. Match the device to the importance of the meeting.

The pre-join screen is genuinely useful and most people skip it. Take 5 seconds to check your camera, microphone, blur or background, and audio device. The pre-join screen exists precisely so you can fix these before everyone’s watching. Joining cold — without checking — is how you end up with the wrong microphone selected, your camera off when you wanted it on, or no idea your background looks like a war zone.

Why this matters

Joining well isn’t about technology — it’s about respect for the meeting:

Late joins disrupt everyone. Aim to be in the meeting 30 seconds before start time, not arriving 2 minutes after.

Audio issues cost the whole room time. Five minutes of ‘can you hear me?’ across 8 attendees is 40 person-minutes wasted.

Pre-join settings prevent surprises. Bad microphone, embarrassing background, blurry camera — fixable in pre-join, painful mid-meeting.

When you’ll use this

• Every time you have a Teams meeting (so, daily for most people).
• When you’re joining as a guest from outside your organisation.
• When you’re joining from an unfamiliar device.
• When you’re presenting and need to confirm everything works.

How to do it

1. Click the meeting link from Outlook calendar, Teams calendar, or the meeting invitation.
2. On the pre-join screen, check your camera, microphone, and audio device.
3. Apply background blur or a background image if needed.
4. Click Join now.
5. If you arrive in a lobby, wait to be admitted (some meetings require this).
6. Once in, mute when not speaking and turn camera on if appropriate.

Best practices

• Use the desktop app for important meetings. Best audio, best features, best stability.
• Aim to be ready 30 seconds before start. Late by 2 minutes = 16 person-minutes wasted across an 8-person meeting.
• Always check pre-join settings. 5 seconds saves 5 minutes of in-meeting fumbling.
• Mute by default. Unmute to speak. The reverse causes the ‘unmute yourself, Sarah’ moment.

Common mistakes

• Joining on mobile when desktop is available. Mobile is for emergencies; desktop is for participating.
• Skipping the pre-join screen. Wrong mic, no camera, embarrassing background — all preventable.
• Joining from a downloaded version of the link instead of the calendar. Sometimes loses meeting features. Use the calendar link.

↑ Back to top ↑ Back to list

Bad audio is the single most common Teams problem. Two minutes setting up your devices properly saves you from ‘we can’t hear you’ for the rest of your career.

Most audio problems in Teams come down to the wrong device being selected. You have a headset plugged in, but Teams is using your laptop microphone. Or you have an external speaker, but Teams is routing audio to your headphones. Or your microphone is muted at the system level, not the Teams level. Each of these is fixable in 30 seconds — once you know where to look.

Teams device settings live in Settings → Devices. From there, you choose your audio device (speaker and microphone), your camera, and you can run a test call to confirm everything works. Do this once per device or location. Set it once, and Teams remembers your preferences across meetings — until you swap headsets or move to a different desk.

The bigger insight: invest in a decent headset. Laptop microphones pick up keyboard noise, room echo, and the dog. A wired or wireless headset (£40-80 range) makes you sound dramatically more professional with no other change. The cost is trivial compared to the impression you make in dozens of meetings a year. People notice.

When you’ll use this

• When you’ve just installed Teams or are using it on a new device.
• When you’ve changed your headset, microphone, or camera.
• When you’re getting persistent feedback or sound issues.
• Before any important meeting where you’ll be speaking.

How to do it

1. Open Teams.
2. Click your profile picture (top-right) and choose Settings.
3. Open Devices.
4. Choose your Speaker, Microphone, and Camera.
5. Click Make a test call to confirm audio works in both directions.
6. Adjust noise suppression and other audio settings as needed.

Best practices

• Invest in a decent headset. The single highest-impact upgrade for how you sound.
• Run a test call before important meetings. 60 seconds beats discovering issues live.
• Use noise suppression at ‘High’ if you’re in a noisy environment.
• Position your camera at eye level. Looking up your nose at a laptop screen is universally unflattering.

Common mistakes

• Using laptop speakers and microphone for everything. Picks up echo, keyboard noise, room sounds.
• Forgetting to switch devices when changing setup. Plugged in a headset but Teams is still using built-in audio.
• Camera angle showing your ceiling. Raise the laptop or use a stand.

↑ Back to top ↑ Back to list

Scheduling well — clear title, agenda, attendees, right meeting type — is the difference between productive meetings and meetings that waste everyone’s time.

Most calendar invitations are minimal: a vague title, an attendee list, no agenda. The recipient sees it on Monday morning, has no idea what it’s about, and either skips it or attends without preparation. Meetings live and die by the quality of the invite. Five extra minutes when scheduling — clear title, brief agenda, named outcome — produces dramatically better meetings without anyone trying harder.

Teams makes scheduling itself straightforward. Click New meeting from the Teams calendar (or in Outlook), set the time, add attendees, write a clear subject. The bit most people skip is the body. Add a 3-line agenda: what we’re discussing, what we need to decide, what attendees should bring. Suddenly the meeting has structure before anyone joins.

Choose the right meeting type. One-off meeting for ad-hoc discussions. Recurring meeting for ongoing rituals (weekly standup, monthly review). Channel meeting for project work where the whole team should see it (the meeting appears in the channel; recordings, files, and chat live with the team). Channel meetings are particularly underused — they make team meetings part of the team’s record, not just a calendar event.

When you’ll use this

• When you need to schedule a meeting (so, often).
• When recurring rituals need to be set up (standups, reviews, retros).
• When a meeting is part of a project workstream (use a channel meeting).
• When you’ve inherited a calendar of vague meetings and want to clean them up.

How to do it

1. In Teams, go to Calendar and click New meeting.
2. Add a clear, specific title (not ‘Catch-up’ — say what about).
3. Set the date, time, and duration.
4. Add required attendees (the ones who must attend) and optional (FYI).
5. For project work, link the meeting to a channel.
6. Write a 3-line agenda in the body: what / why / decision.
7. Click Send — the invite goes to everyone.

Best practices

• Specific titles only. ‘Q3 marketing budget review’ beats ‘Budget catch-up’.
• Always include an agenda. Three bullets is enough; zero bullets is too few.
• Required vs optional matters. Don’t make everyone required — be honest about who’s needed.
• Use channel meetings for project work. Keeps recordings, files, and chat in the team.

Common mistakes

• Vague titles. ‘Catch-up’ tells nobody what to prepare for.
• No agenda. The meeting starts with ‘so… what are we here for?’.
• Everyone marked required. Wastes optional attendees’ time who could have skipped.
• Recurring meetings that should have ended six months ago. Audit your recurring meetings quarterly.

↑ Back to top ↑ Back to list

Meeting recordings are valuable for people who couldn’t attend — but only if you set expectations, manage privacy, and store recordings somewhere people can find them.

Recording a Teams meeting is one click — Start recording, and Teams captures audio, video, screen share, and transcript. The recording is automatically saved to OneDrive (for personal meetings) or to the channel’s SharePoint site (for channel meetings). Anyone with permission can play it back, including with searchable transcript and chapter markers if available.

What goes wrong with recordings is usually about expectations and storage. People feel uncomfortable being recorded without notice — always announce at the start, and consider whether everyone needs to be on camera. Recordings tucked away in someone’s OneDrive disappear when they leave. Recordings in the wrong channel are inaccessible to people who need them. Treat recording as a deliberate act with implications, not just a button.

The biggest practical issue is search. A recorded meeting from three months ago needs to be findable when someone wants it. Use clear meeting titles (the recording inherits the title), store recordings in the right channel, and use the auto-generated transcript so people can search by keyword. A recording you can’t find isn’t a recording — it’s storage cost.

When you’ll use this

• When team members can’t attend live and need to catch up later.
• When the meeting includes important decisions or training that need to be referenced.
• When you’re running an external presentation that you want a record of.
• When stakeholders ask for proof of what was discussed.

How to do it

1. Start the meeting.
2. Click More actions (the three dots) and select Start recording.
3. Announce that the meeting is being recorded.
4. Recording captures audio, video, screen share, and chat.
5. Stop recording when finished (or it stops automatically when the meeting ends).
6. The recording saves to OneDrive (private meetings) or the channel’s SharePoint (channel meetings).
7. Share the link with attendees and absent team members.

Best practices

• Always announce when you start recording. Privacy expectation is non-negotiable.
• Use channel meetings for team recordings. Stays with the team, not lost in someone’s OneDrive.
• Use clear meeting titles. The recording inherits the title; vague titles produce unfindable recordings.
• Don’t record sensitive discussions. Personnel matters, confidential strategy, anything where the recording itself is a risk.

Common mistakes

• Recording without announcing. Privacy violation, trust damage, sometimes legal issue.
• Recording stored in personal OneDrive for team content. Disappears when person leaves.
• Vague meeting titles. Recording becomes unfindable two weeks later.
• Recording everything by default. Most meetings don’t need recording. Be deliberate.

↑ Back to top ↑ Back to list

Background blur or a custom background hides clutter, protects privacy, and makes you look more professional — without changing your environment.

Background effects in Teams come in three flavours: blur (your background blurred out, you in focus), built-in backgrounds (Microsoft’s library of office and abstract images), and custom backgrounds (your own images). All three solve the same fundamental problem: you can’t always control your environment, but you can control how it appears on camera.

For most people, blur is the right default. It’s less distracting than custom backgrounds, looks professional, and works well even with imperfect lighting. Custom backgrounds (an office, a brand backdrop, a clean wall) work but require good lighting to look natural — bad lighting plus a custom background equals visible green-screen edges and a slightly uncanny effect. Use them deliberately for important external meetings; use blur for everyday calls.

The setting can be applied before joining (on the pre-join screen) or during a meeting (More actions → Apply background effects). Once you set it, Teams remembers your preference. Most people set blur once and never change it — which is fine. The point isn’t to keep changing your background; it’s to look professional regardless of what’s behind you.

When you’ll use this

• When you’re working from home and your background is messy or distracting.
• When you want a consistent professional look regardless of location.
• When you’re in a shared space and want privacy from people walking past.
• When you’re presenting externally and want a clean look.

How to do it

1. Before joining: on the pre-join screen, click Background filters.
2. Choose Blur or select a built-in background.
3. To use a custom image, click Add new and upload (high-resolution, landscape).
4. During a meeting: click More actions → Apply background effects.
5. Apply and continue.

Best practices

• Default to blur. Less distracting than custom backgrounds, works in any lighting.
• Use custom backgrounds deliberately. Important meetings, branded calls — not everyday standups.
• Test your background in pre-join. Sometimes blur catches the edge of objects in unflattering ways.
• Use a real background if your space is professional. A clean wall beats artificial backgrounds.

Common mistakes

• Distracting custom backgrounds. Beach photos and animated backgrounds compete with you for attention.
• Custom backgrounds in poor lighting. Visible edges, uncanny effect, less professional than blur.
• Forgetting to apply blur in private spaces. Your kitchen mess is now in your client meeting.

↑ Back to top ↑ Back to list

Showing your screen lets the meeting follow along — but the wrong choice exposes more than you intend. Default to a window, not your whole screen.

Screen sharing in Teams has three options: Screen (your whole desktop), Window (one specific app), and PowerPoint Live (the dedicated presentation mode). Each has its place, but the default for most people should be Window — it’s focused, it’s safer, it shows only what the audience needs to see.

Sharing the whole screen is risky. Notifications pop up. Tabs in your browser are visible. Other apps appear when you Alt-Tab. Anything you don’t want strangers to see — emails, sensitive documents, half-written drafts, that personal browser tab — becomes visible the instant you slip. Use whole-screen sharing only when you genuinely need to switch between apps during the share, and even then, prepare carefully.

PowerPoint Live deserves its own mention: when presenting slides, it’s better than sharing the PowerPoint window. The audience can navigate slides themselves at their own pace, accessibility features work better, and you see your presenter notes alongside slides. It also handles network issues better than screen sharing — slides keep updating even when the bandwidth dips.

When you’ll use this

• When you need to demonstrate something visually.
• When you’re presenting slides (use PowerPoint Live).
• When you’re walking through a document, dashboard, or system.
• When debugging a problem live with someone.

How to do it

1. In the meeting, click Share.
2. Choose Window (preferred) or Screen.
3. For slides, choose PowerPoint Live instead.
4. Select the specific window or PowerPoint file.
5. If sharing video or audio, turn on Include computer sound.
6. Use the presenter toolbar at the top to switch content or stop sharing.
7. Click Stop sharing when finished.

Best practices

• Default to Window, not Screen. Safer and more focused.
• Close sensitive apps and tabs before sharing. Even Window mode can leak if you Alt-Tab carelessly.
• Use PowerPoint Live for slides. Better experience for everyone.
• Confirm the audience can see clearly. ‘Can everyone see okay?’ takes 5 seconds.

Common mistakes

• Sharing whole screen by default. Exposes notifications, other tabs, sensitive content.
• Screen-sharing PowerPoint instead of using PowerPoint Live. Worse for everyone.
• Forgetting ‘include sound’ for video shares. Audience watches in silence and asks why.

↑ Back to top ↑ Back to list

Letting another attendee control your shared screen is the right tool for hands-on collaboration — when both of you need to interact with the same thing.

When you’re sharing your screen and another attendee needs to actually interact with what you’re showing — type, click, demonstrate — Teams lets you give them control. They take the keyboard and mouse on your screen, do what they need, and you can take control back at any time. It’s the right tool for genuine hands-on collaboration: helping someone with a process, demonstrating a fix, or letting a colleague edit something that’s on your screen.

The mechanic is straightforward but the discipline matters. Only give control to people you trust. Once they have it, they can do anything you can do — open files, install software, navigate the internet, click into emails. Teams logs the activity, but the damage from misuse can be done in seconds. Use give-control sparingly, only with attendees you’d let touch your laptop physically.

An alternative for many cases is to invite the other person to take over the share. They share their screen instead, and you watch. This is often cleaner — they’re working in their own environment, with their own files and credentials, and there’s no question of permissions. Default to ‘pass the share’ over ‘give control’ when both options work.

When you’ll use this

• When you’re sharing and the other person needs to interact with the content.
• When walking someone through a fix or process hands-on.
• When pair-programming or pair-editing live.
• When showing someone how to do something they’ll need to repeat.

How to do it

1. While sharing your screen, click Give control in the presenter toolbar.
2. Choose the person you want to give control to.
3. They can now control your screen.
4. When done, click Take back control in the toolbar.

Best practices

• Give control only to trusted people. Same trust threshold as physical access.
• Take back control as soon as the task is done. Don’t leave control with someone for hours.
• Prefer ‘they share their screen’ for most cases. Cleaner, no trust question.
• Close sensitive apps before sharing if you might give control.

Common mistakes

• Giving control to external participants casually. Bigger risk than internal.
• Forgetting to take back control. The other person retains access until you do.
• Using give-control when ‘pass the share’ would work. Unnecessary risk.

↑ Back to top ↑ Back to list

Meeting notes that nobody can find afterwards are wasted notes. Teams’ built-in tools — meeting notes, transcript, AI recap — make notes shareable, searchable, and durable.

Most meeting notes are lost the moment they’re taken. Someone scribbles on paper. Someone types into their personal OneNote. Someone messages themselves a few bullets. None of this is reliably findable later. Teams has multiple built-in alternatives — meeting notes attached to the meeting itself, automatic transcript, AI-generated recap — that make notes part of the meeting’s permanent record.

Meeting notes in Teams (accessed via the meeting’s chat or the Notes button during the meeting) are a shared OneNote-like space attached to the calendar event. Multiple people can edit. Notes persist after the meeting and are accessible to anyone in the meeting. For recurring meetings, notes accumulate across instances — a built-in record of every standup, every review, every retrospective.

If your tenant supports it, transcription and AI recap change the calculus further. Transcription captures every word automatically. AI recap summarises what was decided, what was discussed, and (often) what action items came out. You stop having to take notes at all for many meetings; you can listen, contribute, and trust the system to capture the record. Verify the AI output, but don’t dismiss it — for most meetings, it’s better than what humans were producing manually.

When you’ll use this

• When the meeting includes decisions, actions, or context that needs to be captured.
• When team members couldn’t attend and need to catch up.
• When the meeting is recurring and a running record is valuable.
• When you’d otherwise be writing notes that get lost in personal storage.

How to do it

1. During the meeting, click More actions → Notes (or use the meeting chat).
2. Capture key points, decisions, and actions.
3. Multiple people can co-edit — agree who’s primary if helpful.
4. If your tenant has it: enable Transcription for verbatim record.
5. After the meeting, find the notes via the meeting in your calendar.
6. Share or copy notes to a more durable location (channel post, OneNote, project doc) if needed.

Best practices

• Use meeting notes, not personal scratchpads. Notes everyone can find vs notes only you can find.
• Capture decisions explicitly. ‘We agreed X’ is more useful than verbatim transcript.
• Capture action items with owner and date. The single highest-value output.
• For important meetings, combine notes + transcript + AI recap. Layered redundancy.

Common mistakes

• Notes in personal OneNote. Disappear when person leaves; team can’t access.
• No notes at all because ‘we’ll remember’. You won’t.
• Verbatim transcript with no summary. Hard to use; capture decisions and actions explicitly.

↑ Back to top ↑ Back to list

The hand-raise feature lets you signal you want to speak without interrupting. Especially valuable in larger meetings or when there’s a strong dominant voice.

In meetings of more than 4-5 people, knowing when to speak becomes a problem. Interrupting is rude. Waiting for a gap that never comes is frustrating. Sending a chat message gets missed. Teams’ raise-hand feature solves this elegantly — click the hand icon, and the meeting host (and other attendees) sees that you want to speak. They can call on you when there’s a natural break. The signalling is clear; the interruption is avoided.

Raise-hand is most useful in meetings with structure: presentations with Q&A, large team meetings, formal reviews, training sessions. In smaller meetings (3-5 people having a flowing conversation), raising your hand can feel formal and over-engineered — just speak up. Match the tool to the meeting type.

A common pattern in large meetings: the presenter or facilitator periodically checks raised hands and calls on people in order. This is dramatically more equitable than ‘whoever speaks loudest gets heard’. Quieter team members get the floor; the dominant voices wait their turn. Done well, raise-hand culture creates more inclusive meetings without anyone trying harder.

When you’ll use this

• When you want to speak in a meeting and there’s no natural gap.
• When the meeting has 5+ attendees and chaotic interrupting isn’t working.
• When a presenter is explicitly inviting hand raises for Q&A.
• When you want to defer interrupting because the current speaker is mid-thought.

How to do it

1. During a meeting, click the Hand icon in the meeting toolbar.
2. A small hand icon appears next to your name in the participant list.
3. Wait for the host or current speaker to acknowledge.
4. Once called on, speak — then click the hand again to lower it.
5. If the host doesn’t see, drop a quick chat message as backup.

Best practices

• Use raise-hand in larger meetings. Where flow-conversation breaks down.
• Lower your hand after speaking. Don’t leave hands raised forever.
• Hosts: actively check the raise-hand list. Otherwise the feature doesn’t work.
• Combine with chat for backup. If your hand goes unnoticed, a brief chat message works.

Common mistakes

• Hosts ignoring raised hands. Defeats the system; people stop using it.
• Leaving hand raised after speaking. Confuses the queue.
• Using raise-hand in 3-person meetings. Over-engineered for small flowing conversations.

↑ Back to top ↑ Back to list

Quick reactions (👍 ❤️ 😂 👋) let you respond without interrupting. They’re not just decoration — they’re how you contribute to a meeting without speaking.

Meeting reactions in Teams are short-lived emoji that appear next to your name when you tap them. Like, heart, applaud, laugh, surprised. They float briefly and disappear. They’re trivial-looking, but they solve a real problem: how do you signal agreement, appreciation, or laughter in a meeting without interrupting? Without them, the answer is ‘you don’t’ — and the meeting becomes a series of monologues.

Reactions especially matter in larger meetings or all-hands sessions where most people aren’t talking. A presenter can see a wave of 👍 reactions when they make a good point. A speaker gets 👏 acknowledgement after a strong contribution. Someone telling a difficult story sees a row of ❤️ reactions instead of awkward silence. The meeting feels populated and responsive — instead of feeling like talking into a void.

The discipline is in not overdoing it. Reactions during every sentence become noise. Reactions to a small handful of moments (a key point, a difficult moment, a good joke, a milestone) feel natural. Use them like punctuation — emphatic but rare.

When you’ll use this

• When you want to acknowledge or respond without interrupting.
• In larger meetings where most attendees aren’t speaking.
• When a presenter makes a good point and you want to reinforce it.
• In all-hands meetings or town halls where reaction is the main contribution.

How to do it

1. During the meeting, click the React icon in the toolbar.
2. Choose the appropriate reaction (👍 ❤️ 😂 👋).
3. The reaction floats briefly above your name and disappears.
4. Use sparingly to keep impact.

Best practices

• Use reactions for emphasis, not constant flow. A few well-placed reactions; not a constant stream.
• 👍 for agreement, ❤️ for appreciation, 👏 for milestones. Match the reaction to the moment.
• In all-hands, reactions are the main contribution. Use them to make the speaker not feel alone.
• Don’t overuse 😂. Loses meaning if applied to everything.

Common mistakes

• Reactions every five seconds. Becomes noise; loses meaning.
• Inappropriate reactions in serious moments. Read the room.
• Hosts ignoring reactions. Meeting feels less alive than it could.

↑ Back to top ↑ Back to list

Meeting chat is where parallel conversation, links, and quick notes live during a meeting. Used well, it’s a second channel that enriches the main one.

Every Teams meeting has a chat panel — a sidebar where attendees can type messages, share links, ask questions, or discuss in parallel. Meeting chat exists during the meeting and persists afterwards (in Teams chat for the participants). It’s effectively a second conversation alongside the spoken one, and it’s one of the most powerful and most-underused features in Teams.

What meeting chat does well: capture links shared during the meeting (so people don’t have to type from memory afterwards). Hold side discussions that don’t need to derail the main thread. Let quieter people contribute via text instead of voice. Surface questions that the host can answer when it makes sense. Provide a place for the AI transcript to live alongside contextual notes.

What meeting chat does badly: replace the main conversation. When everyone’s typing simultaneously and nobody’s listening, the meeting becomes confused. The skill is using chat to support the main conversation — links, supporting context, side notes — not to replace it. If chat is dominating the meeting, something is wrong.

When you’ll use this

• When you want to share a link or reference during the meeting.
• When you have a quick question that doesn’t need to derail the main conversation.
• When you want to follow up on something a previous speaker said.
• When you’re more comfortable typing than speaking.

How to do it

1. During the meeting, click Chat (the speech bubble icon).
2. Type your message and send.
3. Share links, references, or quick questions.
4. Use @mention to flag a specific person.
5. After the meeting, the chat persists in Teams chat for the participants.
6. For channel meetings, the chat lives in the channel.

Best practices

• Use chat for links and references. ‘Here’s the doc we discussed’ beats verbal description.
• Don’t have parallel conversations that compete with the main one. Chat supports, doesn’t replace.
• @mention people for specific follow-ups. Easier than asking verbally.
• Save important chat content somewhere durable. Chat in personal meetings disappears from view eventually.

Common mistakes

• Letting chat dominate. Everyone typing, nobody listening, meeting becomes confused.
• Important decisions only in chat. Capture them in notes too — chat scrolls away.
• Inappropriate side chat about other attendees. Chats can be viewed later by hosts; behave accordingly.

↑ Back to top ↑ Back to list

Recurring meetings save scheduling time but create their own problem: stale meetings nobody questions. Set them up well, audit them regularly.

Recurring meetings are how teams maintain rhythm. Weekly standups. Monthly reviews. Quarterly retrospectives. They land in everyone’s calendar automatically, the agenda is implicit, and the team builds a cadence around them. Teams makes setting them up easy — pick a frequency (daily, weekly, monthly), pick an end date (or ‘no end date’ for ongoing rituals), and the meeting series is created.

The trap with recurring meetings is that they outlive their usefulness. The weekly standup that was essential during a project launch is still happening six months after the project ended. The monthly review with three different teams that no longer have anything in common still appears. Nobody questions them; everyone keeps attending out of inertia. The cost across an organisation is staggering — meetings that produce nothing, attended by people who can’t say no.

The discipline is to audit recurring meetings quarterly. Look at every recurring meeting in your calendar. Ask: is this still useful? Has the original purpose evolved? Are the right people invited? Should the cadence change? Cancel the ones that no longer earn their place. The hardest is the meeting you created — you feel ownership, but other people are paying the cost. Be ruthless with your own recurring meetings.

When you’ll use this

• When a meeting needs to happen on a regular cadence (daily, weekly, monthly).
• When you’re setting up a team rhythm (standup, retro, review).
• When a long-running project requires regular check-ins.
• When you want to remove the cost of repeated scheduling.

How to do it

1. Open Teams calendar and click New meeting.
2. Add title, attendees, and an agenda.
3. Set the date, time, and duration.
4. Choose Repeat and pick the cadence.
5. Set an end date (six months out) rather than ‘no end date’.
6. Send the invitation.
7. Audit recurring meetings quarterly.

Best practices

• Always set an end date. Forces an active decision to renew.
• Audit recurring meetings quarterly. Cancel anything that’s coasting.
• Document the purpose in the invite body. So new joiners know why this exists.
• Re-evaluate cadence as needs change. Weekly might become fortnightly; monthly might end.

Common mistakes

• Recurring meetings with no end date. Become indefinite without anyone choosing.
• Inviting too many people ‘just in case’. The cost compounds across the recurrences.
• Never auditing. Stale recurring meetings drain organisational time.

↑ Back to top ↑ Back to list

Files shared in a channel meeting end up in the right place — the team’s SharePoint site. Not in someone’s OneDrive, not lost in chat.

When you share a file in a Teams meeting, where does it actually live? It depends on the meeting type, and the answer matters more than people realise. Private meeting chat: file goes to your personal OneDrive (with a sharing link to attendees). Channel meeting: file goes to the channel’s SharePoint folder, accessible to everyone in the team. The first vanishes when you leave the org; the second stays with the team forever.

The implication is that channel meetings are dramatically better for project work. Anything shared during the meeting — slides, supporting documents, screenshots — automatically lands in the team’s structured location. New joiners can find it. Future you can find it. The team’s content accumulates in one searchable place instead of scattering across personal OneDrives.

The behaviour to avoid is uploading files to the meeting chat in private meetings, then assuming the team can find them later. That file lives in your OneDrive, with permissions that get murky over time. Six months later, half the attendees can’t access it, and you have to re-share or re-upload. Channel meetings prevent this entirely.

When you’ll use this

• When you’re running a meeting that’s part of an ongoing project.
• When you want files shared during the meeting to be accessible to the team afterwards.
• When you’d otherwise be uploading files to chat that should live in the team.
• When the meeting is part of a recurring rhythm (standup, review).

How to do it

1. Schedule the meeting as a channel meeting (linked to a specific channel).
2. During the meeting, share files via meeting chat or attach to the meeting.
3. Files automatically save to the channel’s SharePoint folder.
4. After the meeting, files are accessible from the channel’s Files tab.
5. Anyone in the team can find them, even those who didn’t attend.

Best practices

• Use channel meetings for project work. Files stay with the team.
• Upload to channel Files tab if pre-share is needed. Don’t email attachments.
• Verify files landed correctly after the meeting. Quick check that everything’s accessible.
• Tag/file files into the right folder. Channel Files can become messy without structure.

Common mistakes

• Sharing files in private meeting chat for team content. Lives in your OneDrive; team can’t find it later.
• Uploading the same file repeatedly to different meetings. Multiple copies; no source of truth.
• No structure in channel Files. Becomes a dumping ground.

↑ Back to top ↑ Back to list

Meeting notes attached to the calendar event become part of the meeting’s permanent record — accessible, searchable, durable.

Most meeting notes are taken in the wrong place. Someone’s personal OneNote. A Word doc on someone’s desktop. A scratchpad that never makes it back to the team. Teams’ built-in meeting notes solve this by attaching notes directly to the meeting itself — accessible from the calendar event, the meeting chat, and (for channel meetings) the channel.

Multiple people can co-edit meeting notes during or after the meeting. Decisions, actions, and discussion points captured live. After the meeting, attendees can review, add additional points they remembered, and confirm what was agreed. The notes persist permanently — for recurring meetings, they accumulate as a running record of every instance.

Combined with AI recap (where available) and transcription, meeting notes become one piece of a layered record. Notes capture key decisions and actions. Transcript captures verbatim what was said. AI recap summarises. Different tools for different needs — but the foundation is having notes attached to the meeting in the first place. Personal scratchpads are not enough.

When you’ll use this

• When the meeting has decisions, actions, or context worth capturing.
• When team members couldn’t attend and need to catch up.
• When the meeting is recurring and benefits from a running record.
• Almost always for any meeting longer than 30 minutes.

How to do it

1. During or before the meeting, click Notes (or visit the meeting in calendar).
2. Open the shared notes space.
3. Type or paste decisions, action items, and key discussion points.
4. Multiple people can co-edit — agree primary note-taker if helpful.
5. After the meeting, review and tidy notes; share a link to attendees.
6. For recurring meetings, notes accumulate as a running record.

Best practices

• One person leads notes, others contribute. Avoids chaos.
• Capture decisions and actions, not verbatim transcript. Different tool for different need.
• Action items: owner + date. Without these, actions don’t happen.
• Review notes within 24 hours. Clarity fades fast; clean them up while it’s fresh.

Common mistakes

• Notes in personal scratch space. Disappear; team can’t find.
• Verbatim notes with no structure. Hard to use; capture explicit decisions.
• Never reviewing notes afterwards. The cleanup is where notes become usable.

↑ Back to top ↑ Back to list

Teams chat is the right place for quick, internal, conversational messages. Not for everything — but for the right things, far better than email.

Teams direct messages are the everyday workhorse of internal communication. Quick questions. Fast updates. Informal back-and-forth. Anything that would have been a 30-second email or a hallway conversation. The medium suits the message — fast, informal, threaded by person, with rich features (mentions, reactions, formatting, file attachments) when you need them.

Where chat is right: anything brief and internal between colleagues you talk to regularly. ‘Got 5 minutes for a quick question?’ ‘Just finished the draft, link is here.’ ‘Free to grab a coffee?’ Anything that would have clogged inboxes for no reason. Where chat is wrong: formal communications, external correspondence, anything you might need an audit trail for, anything across many people who’d benefit from a channel post.

The skill is knowing when to escalate from chat. A chat conversation that goes for 50 messages probably needed to be a meeting. A chat thread that includes important decisions probably needed to be summarised somewhere durable. A chat conversation that grew to involve five people probably needed to be a channel post. Chat is great for what it’s great at — recognising when something has outgrown chat is just as important.

When you’ll use this

• When you have a quick internal question or update.
• When you’re having an informal back-and-forth with a colleague.
• When you’d otherwise be sending a one-line email.
• When formality and audit trail aren’t needed.

How to do it

1. In Teams, click Chat in the left sidebar.
2. Click New chat (or open an existing chat).
3. Type the recipient’s name in the To field.
4. Type your message.
5. Use formatting, mentions, attachments, or reactions as needed.
6. Send.

Best practices

• Use chat for quick internal messages. Email gets the formal stuff.
• Use @mentions when you need a specific response. Brings attention without ambiguity.
• Escalate to channels when conversations grow. 5+ people = channel post.
• Capture decisions made in chat somewhere durable. Chat scrolls away.

Common mistakes

• Using chat for formal external communication. Email is the right tool.
• Letting decisions live only in chat. Lost when you scroll past.
• Burying important things in long chat threads. Either summarise or move to a channel.

↑ Back to top ↑ Back to list

A group chat is for ad-hoc conversations across a few people. For ongoing team work, use a channel — group chats don’t scale.

A group chat in Teams is just a regular chat with three or more people. You start a new chat, add multiple recipients, and you have a thread that all of you can see and contribute to. Useful for short-lived conversations across a small group — coordinating a project, planning an event, discussing a one-off topic that doesn’t justify a whole channel.

What group chats are bad at is everything that lasts. Files shared in group chats live in the originator’s OneDrive. The chat history is searchable but disconnected from any team or project structure. New people can’t be added without losing some history. The membership is fixed; the topic drifts. Six months in, the group chat is a bag of mixed conversations nobody can navigate.

If a group chat is becoming the home for ongoing team work, that’s the signal to graduate it to a channel. Create a Team (or use an existing one), set up a channel for the topic, and continue the conversation there. Files stay with the team. New members can join. The structure scales. Group chats are for the conversation that ends; channels are for the conversation that continues.

When you’ll use this

• When you have a short-lived conversation across 3-6 people.
• When you’re coordinating something one-off (an event, a one-time discussion).
• When the people involved aren’t all in a single Team that already has a relevant channel.
• When formal channel creation would be overkill for the topic.

How to do it

1. In Teams, click Chat → New chat.
2. Add multiple recipients in the To field.
3. Optionally name the group (helpful for finding it later).
4. Send your first message.
5. Pin the chat if you want quick access.
6. If the conversation grows, consider moving to a Team channel.

Best practices

• Name the group chat. ‘Q3 Planning Crew’ is easier to find than ‘5 unnamed people’.
• Set the topic clearly in the first message. Anchors the chat’s purpose.
• Migrate to a channel when it grows. Group chats don’t scale beyond ~50 messages of substance.
• Don’t store important files only in group chats. They live in someone’s OneDrive — better in a channel.

Common mistakes

• Using group chats for ongoing team work. Files lost in OneDrive, history fragmented.
• No name on the group. Hard to find later among other chats.
• Important decisions only in group chat. Hard to surface; no audit trail equivalent.

↑ Back to top ↑ Back to list

Pinning the chats you use most lets you skip the daily scroll-and-search. A few well-chosen pins, and your most-used conversations are always one click away.

Most people have a small number of chats they actively use — maybe 3-8 — buried in a long list of older conversations. Without pinning, finding them every day means scrolling, searching, or remembering exactly what you called the chat. Pinning lifts your active chats to the top of the chat list, where they stay until you unpin them. The cost of accessing them drops to near-zero.

Pin selectively. The whole point is fast access, which means being choosy about what gets pinned. Five pins is excellent. Ten is workable. Twenty defeats the purpose — you’re back to scanning. Pin the people and group chats you actually use daily; let the rest live in Recent or Search.

Periodic pruning matters. Workloads shift. Yesterday’s daily collaborator might be next month’s monthly check-in. Take 60 seconds every couple of months to unpin chats that no longer match your current work. The pin list should reflect now, not three projects ago.

When you’ll use this

• When you have a small number of chats you use daily and want one-click access.
• When you’re constantly hunting for the same few conversations in a long list.
• When onboarding to a role and want quick access to key contacts.
• When you’ve inherited someone else’s chat list and want to organise it for yourself.

How to do it

1. In Teams, find the chat you want to pin.
2. Hover over it in the chat list.
3. Click More options (three dots) and select Pin.
4. The chat moves to the Pinned section at the top.
5. Repeat for each important chat (keep it under 10).
6. Unpin chats you no longer actively use to keep the list focused.

Best practices

• Pin 5-10 chats max. More than that, you’re scanning again.
• Pin daily collaborators and important groups. Not casual chats.
• Prune pins periodically. 60 seconds every couple of months.
• Combine pinning with channel-following for full access pattern.

Common mistakes

• Pinning everything. Defeats the purpose; you’re scanning a long pinned list.
• Never updating pins. Pinned chats from a year ago sit at the top while current ones are buried.
• Pinning chats you only need occasionally. Use Search for those.

↑ Back to top ↑ Back to list

Muting silences notifications without removing you from the conversation. Essential for chats and channels you need to stay in but don’t need to be notified about.

Notification fatigue in Teams is a real thing. Every chat, every channel, every @mention pings. After a few weeks, your phone vibrates so often you stop noticing — which means you also miss the urgent ones. Muting is the antidote. Mute the chats and channels you need to be a member of but don’t need real-time alerts from. The notifications stop; you can still read them when you’re ready.

What muting does: stops notifications and (for channels) lowers the visual prominence in your activity feed. What muting doesn’t do: remove you from the chat, hide the content, or prevent @mentions from notifying you. @mentions still ping even on muted chats — which is the point. You skim what you want, but get pulled in when someone specifically needs you.

Use mute liberally. The default state of a busy chat or channel can be ‘muted with @mentions on’. You’re still a member; you can read at your pace; you get pinged when you’re specifically needed. The opposite — ‘every message pings’ on every chat — leads inevitably to ignoring everything. Mute aggressively, then unmute the few you need to monitor live.

When you’ll use this

• When a chat or channel produces too many notifications to be useful.
• When you’re a member for visibility but don’t need real-time alerts.
• When you’re focusing and want to reduce distractions.
• When notification fatigue is making you ignore everything.

How to do it

1. Find the chat or channel you want to mute.
2. Hover and click More options (three dots).
3. Select Mute (chat) or Channel notifications → Off (channel).
4. Notifications stop, but you remain a member.
5. @mentions still notify you.
6. Unmute when needed.

Best practices

• Mute aggressively. Default state for most chats can be muted-with-mentions-on.
• Trust @mentions to surface what matters. They cut through mutes.
• Unmute deliberately for chats you actively monitor.
• Review notification settings quarterly. What you needed alerts on six months ago might not match now.

Common mistakes

• Leaving every chat unmuted. Notification fatigue; eventually you ignore all alerts.
• Leaving the chat entirely instead of muting. Loses access; muting is usually the right answer.
• Forgetting to unmute critical channels. Some channels do need real-time monitoring.

↑ Back to top ↑ Back to list

Joining the right Teams gives you access to the work and conversations that matter for your role. The more curated your Teams list, the faster you find what you need.

Most people are members of more Teams than they actively use. The Teams left over from the project you finished six months ago. The all-hands Team you joined for one announcement. The cross-functional Team you were added to without asking. The list grows; the active subset doesn’t. Curating which Teams you’re actively engaged with — and leaving the ones you’re not — keeps your workspace usable.

There are two ways to join: discover and request a public Team, or be added by an Owner to a private Team. For public Teams, browse the directory, find one that matches your interests, and join (sometimes with approval, sometimes immediately). For private Teams, you need an Owner to add you — request access via your manager or the Owner directly.

After joining, the discipline is to follow the channels you actually want to track and mute the rest. A new Team often has 5-10 channels by default; you only care about 2-3. Following surfaces the channels you care about in your activity feed; muting the rest keeps them out of your notifications. This curation is what makes a Team feel useful instead of overwhelming.

When you’ll use this

• When you’re starting on a new project or role and need access.
• When you’ve been pointed at a public Team that’s relevant to your work.
• When a Team Owner has invited you and you need to accept.
• When you’re trying to build the right set of Teams for your role.

How to do it

1. In Teams, click Teams in the left sidebar.
2. Click Join or create a team at the bottom.
3. Browse public Teams or search by name.
4. Click Join team for public Teams.
5. For private Teams, request access or get added by an Owner.
6. After joining, follow the channels you care about and mute the rest.
7. Periodically leave Teams you no longer use.

Best practices

• Curate your Teams list. Be in fewer Teams, more deeply.
• Follow specific channels rather than tracking all of them. Activity feed should surface what matters.
• Mute Teams that are noisy. Don’t get notification fatigue.
• Leave Teams you no longer need. Reduces clutter and notifications.

Common mistakes

• Joining every Team you’re invited to and never leaving any. List grows; usefulness drops.
• Tracking every channel in every Team. Overwhelm; nothing gets the attention it needs.
• Not curating notifications after joining. Default settings produce noise.

↑ Back to top ↑ Back to list

A new Team is a serious commitment — a SharePoint site, channels, permissions, ownership. Create deliberately, not casually.

Creating a new Team is genuinely easy in the interface — five clicks and you have a Team with channels, a SharePoint site behind it, default permissions, and a place for chat and meetings. The ease is the trap. Teams sprawl is one of the most common SharePoint problems: too many Teams, half of them inactive, none clearly owned, and impossible to navigate.

Before creating a Team, ask: does this need to be a new Team, or could it be a channel in an existing Team? Most projects can live as a channel. Most cross-functional groups can. Most short-term initiatives can. New Teams should be reserved for genuinely separate workstreams that have ongoing membership, distinct content, and a clear owner. The bar should be high.

When you do create one, do it properly. Clear, specific name (not ‘Project X’ — name what it is). Two named Owners (not one). 3-5 channels to start (not 15 — add as needed). A pinned welcome post explaining purpose and norms. Permissions reviewed. The first 30 minutes of investment in a new Team prevents months of structural debt.

When you’ll use this

• When a project or workstream genuinely needs separate membership and content.
• When the work is large enough and durable enough to justify the structural overhead.
• When existing Teams aren’t a fit (different members, different ownership).
• When you’ve considered using a channel and confirmed a Team is right.

How to do it

1. Confirm a new Team is genuinely needed (vs a new channel in an existing Team).
2. In Teams, click Join or create a team → Create team.
3. Choose ‘From scratch’ or a template if relevant.
4. Choose Public, Private, or Org-wide based on the membership model.
5. Name the Team clearly and specifically.
6. Add Members and assign at least 2 Owners.
7. Create 3-5 starter channels for the main workstreams.
8. Pin a welcome message explaining purpose and norms.

Best practices

• Always have at least 2 Owners. Single-owner Teams are fragile.
• Specific Team names. ‘Acme 2026 Migration’ beats ‘Project Team’.
• Start with 3-5 channels, add more as needed. Over-channelling at start creates clutter.
• Document Team purpose and norms. Pinned post in General channel.

Common mistakes

• Creating Teams casually. Each one is a structural commitment.
• One Owner only. When they leave, the Team becomes orphaned.
• Creating channels for every micro-topic. Most can live as conversations in fewer channels.
• Generic Team names. ‘Project Team’ tells nobody what it is.

↑ Back to top ↑ Back to list

@mentions cut through the noise. Use them when you specifically need someone’s attention — and not when you don’t.

@mentions are how Teams notifications actually work for most people. A standard chat or channel message might be muted, scrolled past, or ignored. An @mention with your name pings you specifically — even on muted chats — and shows up in your Activity feed at the top of Teams. It’s the difference between ‘somebody said something’ and ‘somebody needs you specifically’.

Use mentions deliberately. The right time to @mention someone: when you specifically need their response, when you’re assigning them an action, when you want them to be aware of something they’d otherwise miss. The wrong time: when they’d see the message anyway, when it’s information not a request, when you’re CC-ing for the sake of CC-ing.

Channel-wide mentions (@channel, @team) are powerful and should be rare. They notify everyone — sometimes hundreds of people. Use them only when something is genuinely urgent or relevant to the whole group. The team that uses @channel for every announcement is the team whose @channel notifications get muted. Then when something is actually urgent, no one sees it.

When you’ll use this

• When you specifically need a particular person to respond or act.
• When you’re assigning a question or action.
• When you want to make sure a comment doesn’t get missed.
• When following up on someone’s earlier message and want them to see your response.

How to do it

1. In a chat or channel, type @.
2. Start typing the person’s name and select them from the list.
3. Add your message.
4. Send — the person gets a notification with your message.
5. Use @channel or @team only for genuinely team-wide announcements.

Best practices

• Mention specifically when you need a response. ‘Sarah, can you…’ is clearer than ‘Anyone able to…’.
• Use @channel rarely. Reserve for genuinely team-wide urgency.
• Don’t @ everyone in long threads. Pick the people who actually need pinging.
• Combine with a clear ask. ‘Sarah, please confirm by EOD’ beats ‘Sarah, this is about your area’.

Common mistakes

• @mentioning everyone, all the time. Notification fatigue; mentions stop meaning anything.
• @channel for routine announcements. Erodes the urgency signal of channel-wide mentions.
• Vague mentions. ‘Hi @Sarah’ isn’t a mention — it’s a wave. State what you need.

↑ Back to top ↑ Back to list

Teams’ Urgent option keeps notifying the recipient until they read it. Use sparingly — for genuine urgency, never as a ‘please read this now’ workaround.

Most messages in Teams send a single notification and move on. The recipient sees it (or doesn’t) and life continues. For genuinely urgent messages, Teams has an Urgent option that re-notifies the recipient every two minutes for 20 minutes — until they read the message or the time expires. It’s powerful and it’s annoying, which is exactly the point.

Use Urgent only when the situation actually warrants it. A real urgency: production system is down and only one person can fix it. A real urgency: a meeting is starting in 5 minutes and the speaker hasn’t joined. Not an urgency: ‘I want a response soon.’ Not an urgency: ‘this is important to me.’ Misusing Urgent is how you become the person whose messages get muted.

There’s also Important as a softer option — flags the message visually but doesn’t repeatedly notify. For ‘this matters but it’s not on fire,’ Important is the right tool. Most messages don’t need either flag; the default is fine. Save Urgent and Important for the moments when they genuinely add value.

When you’ll use this

• When something is genuinely time-critical and the recipient must respond now.
• When a meeting is starting and you need someone immediately.
• When a system or process needs urgent intervention.
• Almost never for routine work that ‘feels urgent’ but isn’t.

How to do it

1. Compose your message in chat or channel.
2. Click the delivery options icon (looks like an exclamation).
3. Choose Urgent for re-notify behaviour, or Important for visual flag.
4. Send.
5. The recipient gets repeated notifications (Urgent) or a visual flag (Important).

Best practices

• Urgent is for genuine emergencies only. The bar is high for a reason.
• Use Important for things that matter but aren’t on fire.
• Default to no flag for normal messages. Don’t over-signal.
• If you find yourself using Urgent often, the system isn’t working. Investigate why people aren’t seeing your normal messages.

Common mistakes

• Marking everything Urgent. Becomes noise; actual urgencies don’t stand out.
• Using Urgent for political pressure. ‘I want a response now’ isn’t urgency.
• Important on every message. Same dilution problem.

↑ Back to top ↑ Back to list

Channels organise a Team’s work into focused workstreams. Get the structure right and channels feel intuitive. Get it wrong and they become chaos.

A channel is a workstream within a Team. Each channel has its own conversation, its own files (in the team’s SharePoint), and its own tabs. The Team’s structure is determined entirely by the channels you create — and most Teams have either too few channels (everything jammed into General) or too many (15 micro-channels, half of them dead).

The right structure for most Teams is 3-7 active channels organised by major workstream or topic. General is created automatically and should be for team-wide announcements and the welcome post. Then 2-6 topic channels: Planning, Execution, Reporting, or Project A, Project B, Project C, depending on how the Team works. Add channels as the work expands; archive ones that go quiet.

Channel naming matters. Clear, specific, plain English. ‘Sprint Planning’ beats ‘Planning’. ‘Q3 Marketing Campaigns’ beats ‘Marketing’. The name tells members and visitors what belongs there. Vague channel names lead to vague usage — ‘Discussion 1’ means everyone posts random things and the channel becomes meaningless.

When you’ll use this

• When a Team is being created and you’re setting up the initial structure.
• When the Team’s work has expanded and existing channels are getting overcrowded.
• When a new workstream needs its own dedicated space.
• When you’re refactoring a Team’s structure to reduce confusion.

How to do it

1. Open the Team and click More options (three dots) on the Team name.
2. Select Add channel.
3. Name it clearly and specifically.
4. Add a description so members know what belongs there.
5. Choose Standard, Private (limited members), or Shared (cross-team).
6. Add a welcome post pinned to the channel describing its purpose.
7. Configure tabs (Files, OneNote, Planner, links to key resources).

Best practices

• 3-7 active channels per Team. Goldilocks zone.
• Specific channel names. ‘Sprint Planning’ beats ‘Discussion’.
• Pin a welcome post. Quick orientation for new members.
• Archive dead channels. Don’t let them clutter the navigation.

Common mistakes

• Creating channels for every micro-topic. 15 channels, most dead.
• Putting everything in General. Becomes a firehose with no structure.
• Vague channel names. ‘Discussion 1’, ‘Stuff’, ‘Team’ — meaningless.
• No welcome post. New members don’t know what the channel is for.

↑ Back to top ↑ Back to list

Following a channel surfaces its activity in your feed without overwhelming you with notifications. Curating what you follow shapes how Teams feels.

When you join a Team, you’re a member of all its channels by default — but you only see activity in the channels you actively look at. Following a channel makes its activity prominent in your Activity feed, so you see what’s happening even if you don’t visit the channel directly. It’s the middle ground between ‘nothing’ (no notifications, you might miss things) and ‘everything’ (constant pings).

The discipline is curation. Most Teams have channels that are genuinely active for you (you contribute, you need to know) and channels you’re a member of but don’t actively engage with. Follow the active ones; mute the rest. Suddenly your Activity feed becomes focused on what matters to you, instead of being dominated by every Team you’re loosely involved in.

Teams’ default settings are often too noisy. Take 10 minutes when joining a new Team to configure what you follow and what you mute. The investment pays back across the months you’re a member. Without configuration, Teams becomes ‘too much information’ and you eventually disengage from the activity feed entirely — which means you miss things you should have seen.

When you’ll use this

• When you’ve joined a Team and want to set up your engagement level for each channel.
• When you want to track activity in a channel you visit occasionally.
• When the Activity feed is too cluttered and needs curation.
• When you’re making a long-term shift in your Teams workload.

How to do it

1. Find the channel you want to follow.
2. Hover and click More options (three dots).
3. Select Channel notifications.
4. Choose level: All activity (everything), Custom (specific events), or Off (mute).
5. For most channels, Custom with @mentions on is right.
6. Repeat for each channel — be deliberate.

Best practices

• Follow active channels at Custom — @mentions only. Cuts through, doesn’t overwhelm.
• Mute channels you’re not actively engaged with. Still a member; just no notifications.
• Set up notifications when joining a Team. Don’t accept defaults blindly.
• Review notification settings quarterly. Workload changes; settings should follow.

Common mistakes

• Defaults left unchanged. Either too noisy or too quiet for your actual work.
• ‘All activity’ on every channel. Notification fatigue.
• Muting everything. Missing things you should be seeing.

↑ Back to top ↑ Back to list

A document shared in a channel becomes part of the team’s record — accessible, governed, and findable. Different from chat in important ways.

When you share a file in a channel, it lives in the channel’s Files tab — which is actually a folder in the team’s SharePoint site. This means the file gets the team’s permissions, shows up in everyone’s search, can have metadata applied, and persists with the team forever. It’s the right place for any document the team needs ongoing access to.

By contrast, a file shared in a private chat lives in the originator’s OneDrive. When that person leaves, access becomes complicated. The file isn’t part of the team’s record. It can’t easily get team metadata. It’s findable only if you remember the chat. For team-relevant content, channels are dramatically better than chats — full stop.

Practical pattern: when you have a document the team needs to see, upload it to the channel’s Files tab (or post it in the channel chat, which also stores it in the channel’s folder). Don’t share it via DM. Don’t email it as an attachment. Don’t paste it in private chat. The channel is the team’s filing cabinet — use it.

When you’ll use this

• When you have a document the team needs to access.
• When you’d otherwise be sharing the file in chat or email.
• When the document needs to persist with the team beyond your involvement.
• When the team should be able to search and find this file.

How to do it

1. Open the channel where the file should live.
2. Click Files tab.
3. Upload the file (or drag from File Explorer).
4. Optionally apply metadata (Document Type, Status, Owner).
5. Post in the channel chat with a link to the file if you want to call attention.
6. The team can find it in Files, search, and the channel chat.

Best practices

• Channel files for team work; OneDrive for personal. Different tools, different jobs.
• Apply metadata for findability. Even simple Document Type / Status helps.
• Don’t email attachments to team members. Send a link to the channel file.
• Use folder structure inside Files for organisation. Don’t dump everything at the root.

Common mistakes

• Sharing team files in private chat. Stored in OneDrive, lost when you leave.
• Emailing attachments. Defeats the team’s filing system.
• No structure in channel Files. Becomes a dumping ground.

↑ Back to top ↑ Back to list

Channel tabs pin important resources at the top of a channel — a doc, a planner, a website, a OneNote, a Loop component. The team’s key references in one click.

Channels have tabs at the top — Posts, Files, and any others you add. The default Posts and Files cover the basics. The power comes when you add custom tabs: pin a key document for instant access; embed a Planner board for the project’s task list; add a OneNote for the team’s running notes; pin an external website (a dashboard, a system, a wiki). Tabs turn a channel from a conversation into a workspace.

What goes wrong with tabs is usually too many or too few. Too few (just Posts and Files) and the channel is plain — every important resource has to be hunted for in chat. Too many (12 tabs of mixed dashboards and docs) and the tab bar becomes chaos. The right number is usually 3-6: the genuinely-most-useful resources, pinned for everyone.

Maintenance matters. Tabs that point to outdated documents, dead websites, or abandoned planners become noise that erodes trust. When a tab is no longer relevant, remove it. Channels need the same kind of tidying as any shared workspace.

When you’ll use this

• When you want to pin a key resource at the top of a channel.
• When the team frequently needs to access the same document or board.
• When you’re adding a Planner, OneNote, or external system to the channel’s workspace.
• When you want to give new team members instant access to key references.

How to do it

1. Open the channel.
2. Click + at the right of the tab bar.
3. Choose what to add: a file, OneNote, Planner, website, etc.
4. Configure the tab (point at the right doc, name it clearly).
5. Save — the tab is pinned for the whole channel.
6. Periodically review and remove tabs that are no longer relevant.

Best practices

• 3-6 tabs is the right range. More than that, the tab bar gets cluttered.
• Pin the genuinely most-used resources. Not every document the team has ever opened.
• Name tabs clearly. ‘Project Plan’ beats ‘Document’.
• Remove stale tabs. Don’t let them rot.

Common mistakes

• Too many tabs. Dilutes the value of pinning.
• Tabs pointing to files in personal OneDrive. Stops working if the originator leaves.
• Never updating tabs. Outdated tabs erode trust.

↑ Back to top ↑ Back to list

A direct call in Teams is faster than scheduling a meeting for a quick conversation — with audio and video options to match the moment.

Sometimes you don’t need a meeting. You need a 90-second conversation. Teams direct calling is the right tool — click someone’s name, click Call, and you’re talking. No invitation. No calendar coordination. No ‘when’s a good time?’. Just a quick call, like phoning someone, except integrated with all the Teams features (sharing, recording, chat).

Use it for quick, informal conversations: clarifying something you read in chat, a quick question that’s easier verbally than in writing, checking on a colleague, brief coordination. For longer or formal conversations, a scheduled meeting is better — calls are for the immediate, the brief, the ad-hoc.

Etiquette matters more than people realise. A direct call lands as a ringing notification — it interrupts. So: don’t call someone you haven’t messaged first (‘Got 5 minutes?’). Don’t call repeatedly if they don’t pick up — they’re probably busy. Don’t make calls outside reasonable hours. The fact that calling is easy doesn’t mean every conversation should be a call.

When you’ll use this

• When you have a quick question that’s easier verbally than in writing.
• When chat back-and-forth is becoming inefficient.
• When you need clarification on something complex.
• When informal connection matters and a meeting is overkill.

How to do it

1. Open Teams chat with the person.
2. Click the Audio call or Video call icon at the top of the chat.
3. They get a ringing notification.
4. When they pick up, talk.
5. End the call when finished.

Best practices

• Send a chat first. ‘Got 5 minutes for a quick call?’ is courtesy.
• Match the call type to the conversation. Audio for quick chat, video for richer interaction.
• Keep calls short. Anything over 15 minutes probably should have been a scheduled meeting.
• Don’t call repeatedly if no answer. They’re busy. Send a chat instead.

Common mistakes

• Cold-calling without warning. Especially across time zones or seniority.
• Calling for things that should be in writing. Decisions that need a record belong in chat or email.
• Calling repeatedly when ignored. Annoying; they’ll see your message when they can.

↑ Back to top ↑ Back to list

When chat is becoming inefficient — too many back-and-forth messages, too much context to type — a quick switch to a call resolves it in 60 seconds.

Some conversations don’t fit in chat. The tone is hard to read. The context is hard to type. The back-and-forth has gone on for 15 messages and you’re still circling. The right move at that moment is to switch to a call — but most people miss it because they’re focused on typing the next message instead of stepping back to ask ‘is this conversation working?’.

The signal is usually clear: when you find yourself drafting a long message because the question is genuinely complex, when you’ve sent five messages and the other person seems to be missing something, when there’s emotional content that’s hard to convey in text. These are the moments to call. The 90-second call resolves what might have taken 30 messages and an hour of fragmented attention.

How to switch elegantly: just suggest it. ‘This is getting complicated — can I call you for 5 minutes?’ or ‘Easier on a call?’. Almost everyone says yes — and the conversation finishes faster, with better understanding, in less time. The only tax is the small social cost of suggesting it. Pay that tax; it’s worth it.

When you’ll use this

• When chat back-and-forth has gone on for too long.
• When the question is too complex to type efficiently.
• When emotional or political content is hard to convey in text.
• When you can sense the other person isn’t quite getting it.

How to do it

1. Recognise the chat isn’t working.
2. Send a chat asking: ‘Easier on a call?’ or ‘Can I call for 5 minutes?’.
3. If yes, click the audio or video call icon.
4. Have the conversation in 90 seconds.
5. Send a quick chat summary afterwards if decisions were made — ‘Just to confirm, we agreed X.’

Best practices

• Recognise the moment fast. 5 messages of back-and-forth is enough.
• Frame it positively. ‘Easier on a call’ suggests efficiency, not impatience.
• Capture decisions in chat afterwards. Calls don’t leave a record by default.
• Keep the call short. The point is to resolve, not to escalate to meeting territory.

Common mistakes

• Persisting with chat when it’s clearly not working. Wasted hour vs 90 seconds.
• Calling without warning when the conversation isn’t expecting it. Send the chat suggestion first.
• No summary after the call. Decisions evaporate without a written trail.

↑ Back to top ↑ Back to list

PowerPoint Live lets co-presenters drive the slides themselves — without sharing screen control or running into clunky ‘next slide please’ interruptions.

Co-presenting in Teams used to be awkward. The slide-sharer had to manually advance slides whenever the other presenter wanted to move on, leading to constant ‘next slide please’ or clumsy hand-offs. PowerPoint Live changed this. When the slides are shared via PowerPoint Live, anyone designated as a presenter can navigate the slides themselves — independently of who’s speaking.

The mechanic is: open the deck, share via Share → PowerPoint Live, and assign other presenters via the People panel. They can now move forwards and backwards through the deck, jump to specific slides, and drive the visual experience while the speaker focuses on speaking. Presenters can hand off seamlessly: ‘Now over to Sarah for the next section.’ Sarah takes over the slides and the talking, no clumsy transition.

PowerPoint Live also gives audience members the ability to browse slides at their own pace (if enabled), and provides accessibility features (translated captions, high-contrast modes) that screen-share doesn’t. For any meeting where multiple people will present from the same deck, it’s the right tool. Stop screen-sharing PowerPoint; start using PowerPoint Live.

When you’ll use this

• When multiple people will present from the same deck.
• When you’re handing off sections of a presentation to different people.
• When you want a smooth transition between presenters.
• When accessibility or audience self-pacing matters.

How to do it

1. Open the PowerPoint deck (must be in OneDrive or SharePoint).
2. In the meeting, click Share → PowerPoint Live.
3. Select the deck.
4. In the People panel, set co-presenters as Presenter role.
5. Co-presenters can now navigate slides themselves.
6. Hand off verbally and let the other presenter drive.

Best practices

• Use PowerPoint Live for any multi-presenter deck. Smooth transitions vs clunky screen-share.
• Brief co-presenters on PowerPoint Live before the meeting. First-timers get confused.
• Test the deck in PowerPoint Live first. Some animations behave differently than in screen-share.
• Use the presenter notes feature. Each presenter sees their own notes for their slides.

Common mistakes

• Screen-sharing PowerPoint instead of using Live. Inferior on every dimension.
• Not setting co-presenters before the meeting. Hand-off becomes awkward.
• Forgetting the deck must be in OneDrive/SharePoint. Local files don’t work in Live.

↑ Back to top ↑ Back to list

After a meeting, the recording is the easiest way to bring absent attendees up to speed — but only if it’s findable and shareable.

Recordings are most useful for people who couldn’t attend. Sending them the recording link lets them catch up on their own time, at their own pace. The mechanics are simple: the recording is automatically saved (to OneDrive for private meetings, to the channel’s SharePoint for channel meetings) and shows up as a link in the meeting chat. Forward the link, done.

The thing to remember is permissions. The recording inherits permissions from where it’s stored. For channel meetings, anyone in the channel can play it back. For private meetings, only the original attendees have access by default — if you want to share with someone who wasn’t invited, you need to share the file explicitly (the recording is in your OneDrive at /Recordings/).

The other consideration is context. A 60-minute recording is a lot for someone to watch. Pair the recording link with a short summary: what was discussed, what was decided, what’s the action. Better still: share the AI recap and the action items alongside the recording. Now the absent attendee can decide whether to watch the recording in full or just read the recap. Most will choose the recap.

When you’ll use this

• When someone couldn’t attend a meeting and needs to catch up.
• When you want to give a stakeholder visibility into what was discussed.
• When training material needs to be re-shared.
• When external attendees missed an internal meeting.

How to do it

1. After the meeting, find the recording in the meeting chat or channel.
2. Confirm permissions are right — for external sharing, set explicit access.
3. Copy the recording link.
4. Send the link to absent attendees with a short summary.
5. If your tenant has AI recap, share that alongside.
6. Highlight key time-stamps if the recording is long.

Best practices

• Pair the recording with a summary. Most people will read the summary, not watch the recording.
• Check permissions before sending. Especially for external recipients.
• Highlight key time-stamps. ‘Decision at 23:40, action items at 47:10’ saves the recipient time.
• Share AI recap if available. Often it’s all the recipient needs.

Common mistakes

• Sending the recording with no context. Recipient has to watch the whole thing.
• Forgetting to check external permissions. Link doesn’t work for the recipient.
• Sharing recordings of meetings that probably shouldn’t have been recorded. Sensitive content; consider whether sharing is appropriate.

↑ Back to top ↑ Back to list