Module 3 of StartCloud's Microsoft 365: Everyday Skills learning pathway, in five short units with a knowledge check: how to decide between a channel and a chat, why a file shared in a chat lands in your OneDrive while a file posted in a channel lands in the team's SharePoint library, how to set Teams notifications so you can live with them, and how mentions, tags, status and quiet hours keep a team reachable without being exhausting.
Teams Without the Noise
Channel or chat, and how to decide
Teams gives you two places to type and never explains which one to use. So most of us default to chat, because chat feels quicker, and over a couple of years an entire business quietly ends up with its decisions, approvals and files locked inside private conversations nobody else can see.
There is one difference worth remembering, and everything else follows from it. A chat belongs to the people in it. A channel belongs to the work.
A channel belongs to the work
A channel sits inside a team, and everyone in that team can read it. Post there and the conversation stays with the project, not with you. Someone who joins the business in March can scroll back through February and catch up without asking anyone a single question.
- Anything the team would want to find later
- Decisions, updates, questions with an answer worth keeping
- Files the team owns, rather than files you happen to have
- New starters can read it without being invited to anything
A chat belongs to the people in it
Chat is the corridor conversation. It is quick, it is casual, and it is completely invisible to everyone who is not in it. That is genuinely useful for the small stuff, and it is exactly why important things should not live there.
- Quick questions with a short shelf life
- Are you free at two, and did you eat my yoghurt
- Anything genuinely private between a few people
- Nobody can find it later, and that is the trade you are making
Would this be useful to somebody else, later? If yes, it goes in a channel. If you honestly cannot imagine anyone ever needing it again, chat is fine. That is the whole test, and it takes about a second to run.
You know the one. It started with three people and a question, it now has eleven people, a nickname, and six months of decisions in it. Once a group chat is making decisions and holding files, it has become a channel that nobody got around to creating. Move it. Everyone will grumble for a day and thank you for a year.
Standard. Visible to everyone in the team. This is the normal one, and the one you should reach for unless you have a reason not to.
Private. Only the people specifically added to it can see it, even other members of the team. Useful for genuinely sensitive work, and easy to overuse until nobody can find anything.
Shared. Lets you bring in people from outside the team, and in some setups from outside the business, without adding them to everything else.