Two Apps, One Job
Teams and Outlook look like two different tools. They're really two front doors into the same job: talking to the people you work with. Email is asynchronous (I send, you reply when you can). Chat and meetings are synchronous (we talk, now or in a scheduled window). Getting a sense of which to use when is most of the skill.
Teams for the work happening now, Outlook for the work that needs a record or a reply by Tuesday.
Confusion between the two is the single biggest cause of noise in a modern workplace. A quick email turns into a Teams chat that needs three meetings to resolve. A decision that belonged in a channel ends up buried in five people's inboxes. The rest of this session is about picking the right door.
Teams, in the Right Shape
Teams has three kinds of spaces, and the first time you use it they can all look the same.
Teams are the big container, usually for a whole branch, project, or working group. A Team has members, files, and at least one channel. Behind every Team is a SharePoint site (covered in the OneDrive, SharePoint & File Sense session).
Channels are rooms inside a Team, usually for a particular topic or stream of work. A "Communications" channel, a "Weekly Sync" channel, a "Client X" channel. Posts in a channel are visible to everyone in the Team.
Chats are private conversations, one-on-one or small group, outside any Team. Nobody else can see them. Chat files go to your OneDrive, not SharePoint.
If a decision or a file needs to survive when someone leaves, it belongs in a channel, not a chat. Chats disappear with the sender's account. Channels stay with the Team.
Channels vs Chats, When to Use Which
Use a channel
When more than two or three people need to see the conversation.
When the decision matters later and someone might need to find it.
For project updates, status notes, and shared questions.
For files the team needs access to.
When you want new team members to catch up without re-sending everything.
Use a chat
For a quick question to one person.
For sensitive or personal conversations.
For small-group coordination that doesn't need a record.
For ad-hoc work that doesn't belong to a formal Team.
When you genuinely don't want it searchable by the whole team.
A rough question to ask yourself: "If I got hit by a bus, would anyone else in the team need to find this conversation?" If yes, channel. If no, chat is fine.
Meetings That Don't Waste Time
Meeting fatigue is a real cost. Some meetings genuinely need to happen. Many don't. A few Teams habits make the ones that do happen work better.
Put an agenda in the invite
Even three bullet points. It tells people whether they need to attend, what to prepare, and where the conversation should go. A meeting without an agenda is a meeting that runs long.
Use the meeting chat for links and side threads
Drop relevant files, links, and "I'll follow up on that" notes into the meeting chat during the call. Everyone has them afterwards. Saves the awkward "can someone send that thing?" email.
Turn on transcription for long meetings
Transcription (and recording, if your policy allows it) means the meeting's decisions and details survive. Copilot, covered in the Working with AI strand, can then summarise the transcript, pull out action items, and even catch you up if you missed the first ten minutes.
Make "channel meetings" your default for team meetings
A channel meeting is visible to the whole channel, and the chat and recording live in the channel afterwards. Much better than a private meeting that only the attendees can later find.
If the meeting could be an email, send the email
The hardest and best habit. Before you schedule, ask: "could this be a paragraph in the channel instead?" Often yes.
Outlook, Taming the Inbox
Email isn't going away. It's still the default for formal records, external contact, and anything that needs to be found in three years. The goal isn't zero email. The goal is an inbox that doesn't own you.
An inbox is a to-do list written by other people. Your job is to triage, not to read everything.
Process in batches, not continuously
Checking email every two minutes is a productivity killer. Three or four deliberate triage passes a day, with Outlook closed in between, is almost always more effective.
Use the four D's
For each email: Delete (or archive), Do (if under two minutes), Delegate (forward with a clear ask), or Defer (schedule a time to handle it, don't just let it sit).
Rules for newsletters and notifications
Anything automated (build notifications, newsletters, system emails) should land in its own folder, not your inbox. Five minutes setting up rules, hours saved over the year.
Focused Inbox, on or off, pick one
Focused Inbox hides less-important mail. Some people love it, some find it confusing. Decide and stick with it. Don't leave it on by accident.
Shared mailboxes, not CC-everyone
If a team needs to share an inbox (enquiries@, info@), use a shared mailbox. Everyone sees it, nobody owns it alone, and replies are logged for the team. Much cleaner than CC chains.
If more than two of the recipients are in the same Teams channel, the channel is probably a better home for it. Email it when you need a record, use a channel when you need a conversation.
Calendar Craft
Your calendar shapes your week more than any to-do list. A few habits keep it honest.
Block focus time
Put real work on your calendar, not just meetings. A two-hour "deep work, do not disturb" block is more useful than hoping for time between meetings. Set yourself to Do Not Disturb in Teams during those blocks.
Default meetings to 25 or 50 minutes
Outlook has a setting to make 30-minute meetings actually 25 minutes, and 60-minute meetings 50. That gives everyone 5-10 minutes between calls, which is the difference between a manageable day and a fried one.
Decline or propose new time without guilt
Meetings that don't need you are meetings that don't need you. "Unable to make it, would love the summary" is a complete sentence.
Use categories and colours
Colour-code by type (meetings, focus time, admin, external). A glance at the week tells you how it's shaping up.
Keep working hours set correctly
Outlook's "working hours" setting tells other people when you're available. If you don't work Fridays, say so. If you start at 7, say so. Stops people scheduling into the wrong times.
Planner, To Do, and OneNote
Three smaller apps that do a lot of the quiet heavy lifting in a team.
Planner, for team tasks on a board
A simple Kanban-style board (To do, In progress, Done). Add it as a tab in a Teams channel and the whole team sees the work in one place. Good for projects with clear tasks and owners, less good for freeform idea work.
To Do, for your personal list
Your own list of things to do. Flags email messages land here automatically, and Planner tasks assigned to you appear here too. A useful "single pane" of everything waiting on you.
OneNote, for the work around the work
A digital notebook. Meeting notes, project journals, shared team knowledge. Searchable across everything. Under-used because people don't know where to start. Start with one notebook per project, one section per theme, and trust search.
Forms, when you need structured input
A quick form for intake, surveys, or event registration. Results land in Excel for you automatically. Much better than chasing replies in a chat thread.
Small Etiquette That Reduces Noise
Habits that reduce noise for everyone.
- Use @mentions sparingly. @channel wakes everyone up; @person wakes one person. Match the ping to the need.
- Don't send "hi" and wait. Put the whole question in the first message, so the other person can answer on their time.
- React with an emoji to acknowledge, rather than replying "OK" eight times in a thread.
- Status matters. Set "Do not disturb" when you mean it. Set "Away" when you're actually away. Colleagues can then make sensible decisions without asking.
- Reply-all with care. Usually only a quarter of the recipients need your reply. Pick them.
- Long threads belong in a channel post, not a chat. Easier to find, easier to skim.
- If you're the organiser of a recurring meeting, cancel the ones that aren't needed. Nobody will object.