On my first day at a corporate job, my entire onboarding was essentially “we’ll add you to the right Teams channels.” I had no idea what that meant. If your company runs on Microsoft 365, Teams is probably where most of your day will happen — so here’s the practical map, including the unwritten etiquette that takes most people months to absorb.
What Teams actually is
Microsoft Teams is a collaboration platform: part instant messenger, part video-conferencing tool, part shared file system, all tied into the wider Microsoft 365 suite (Outlook, Word, Excel, SharePoint, and so on). The big idea is to pull conversations, meetings, and documents into one place instead of scattering them across email and other apps.
If you’ve used Slack, Teams is Microsoft’s equivalent — with deeper ties to Office files and corporate IT.
The four things you’ll use most
1. Chat
Chat is for direct and small-group messaging — the quick, informal stuff. One-on-one with a colleague, or a small ad-hoc group (“can you review this before 3?”). Chats are private to the people in them and aren’t organized by project. Think of it as texting your coworkers.
2. Teams and channels
This is the part that confuses everyone. A Team is a larger group space — usually a department, project, or whole initiative (e.g. “Marketing” or “Project Atlas”). Inside each Team are channels, which break the space into topics (“General,” “Design,” “Budget,” “Random”).
Conversations in a channel are visible to everyone in that Team. That’s the crucial difference from chat: channels are shared, semi-permanent, and organized; chats are private and ephemeral. Posting in the right channel means the whole relevant group can see and search it later.
Rule of thumb: if it’s quick and personal, use chat. If it’s about a shared project and others might need it later, post in a channel.
3. Meetings and calls
Teams handles video meetings (the corporate world’s default), screen sharing, and quick audio/video calls. Meetings can be scheduled (they show up in your Outlook calendar) or started instantly (“let’s hop on a quick call”). You’ll get used to “I’ll send a Teams invite” meaning a calendar event with a join link.
4. Files
Every channel has a Files tab backed by SharePoint. When you share a document in a channel, it lives there and multiple people can co-edit it in real time. This is why colleagues say “it’s in the channel” instead of emailing attachments — the file has one shared home, not twelve email copies.
The etiquette nobody tells you
- @mentions get attention. Typing
@namenotifies that specific person.@channelor@teamnotifies everyone — use it sparingly or you’ll annoy a lot of people. - Reply in the thread, not as a new message. Teams threads keep conversations tidy; starting a fresh post for a reply scatters the discussion.
- Status dots matter. Green means available, red means busy/in a meeting, yellow means away. Check before you call someone out of the blue.
- Use the right channel. Posting a design question in the “Budget” channel is a minor faux pas that quietly marks you as new.
- Quick stuff can wait for async. Not everything needs a meeting. A well-written channel message often beats a 30-minute call.
A typical Teams day
You arrive, scan your Activity feed (mentions and replies waiting for you), answer a few chats, post a status update in your project’s channel, join a scheduled meeting from your calendar, co-edit a doc someone shared in the Files tab, and end the day setting your status. Once the channels-vs-chat distinction clicks, the rest is muscle memory.
How to use the lingo
- “I’ll drop it in the channel so everyone’s got it.” (shared, findable later)
- “Let me DM you” or “I’ll chat you” (private message)
- “Can you hop on a Teams call?” (quick video/audio)
- “I @’d you in the Atlas channel.” (tagged you for attention)
Get comfortable with channels versus chats and meeting etiquette, and you’ll navigate a Teams-run company like you’ve been there for years.