A client of mine, the operations lead at a charity, said something last week that sums up why most Microsoft Teams rollouts quietly fail.

"I need a poster behind my laptop that says: use the channel."

His team is the first in the organisation to move all internal collaboration into Teams channels. No internal email. No private side chats. Everything work-related, in the channel, where the team can see it.

And a few weeks in, he keeps catching himself pinging colleagues an email. He doesn't disagree with the change; he designed half of it. It just takes a couple of seconds to forget, and 25 years of email habit does the rest.

The fix for a stalling Teams rollout is rarely more training. It's two enforced habits: every internal conversation goes in the channel, even between two people, and every email that needs team input gets copied into the channel before anyone replies. Hold those two lines for a fortnight and the new way becomes the default.

When a business moves to channel-based working, somebody has to go first. And going first is structurally harder than going fifth.

The fifth team arrives into an organisation where channels are visibly working. The first team arrives into an organisation where everyone else still emails, still side-chats, still forwards things round. Every message the rest of the business sends is a small tug back toward the old way.

This is worth naming at the start of any rollout, because without naming it, the first team's struggle looks like evidence the change isn't working. It's the opposite. It's what the change is supposed to feel like at the front of the queue.

Habits follow the path of least resistance, and email is a 25-year-old motorway.

The pull is strongest at one specific moment: an external email arrives, and you need your team's input on it. The easy move is to forward it. Reply-all does the rest, and within three messages the team is collaborating in email again. Nobody decided to abandon the channel. The spiral just happened.

That moment, the inbound email that needs internal discussion, is where most channel adoption quietly dies. If you design for that moment, you've designed for the whole problem.

> Want the full set of communication rules, written down and ready to use with your team? They're in the [Chaos Cure](https://www.meetimeservices.com/chaos-cure), the self-guided playbook for getting Microsoft 365 working the way it should.

The counterintuitive rule first. Even a conversation between two colleagues about day-to-day work goes in the channel, so long as it isn't private or personal.

Two people don't need a channel to talk. That's true, and it's also not the point. The point is everyone else.

A channel with conversation in it is an advert. It tells the rest of the team, and the rest of the business, that the new way is real, in use, and safe to join. A channel with nothing in it teaches the opposite lesson: nobody posts here, so I won't be first.

Visible work is also useful in ways private messages can never be. A colleague spots a thread and adds the one fact that changes the decision. A new starter reads three weeks of channel history and understands how the team actually works. None of that happens in a direct chat.

Open is the default. Private is the exception.

For the inbound-email moment, the rule is mechanical.

When an email arrives and you want the team's input, don't forward it. Copy the relevant content into the channel, tag the person or people you need, and have the discussion there. When the team has decided, go back to the email and send the reply.

Yes, it's one more step than forwarding. That step buys you three things. The discussion is visible to the whole team instead of locked in a forward chain. The decision is findable later, attached to the subject it belongs to. And the team gets one more rep of the habit you're trying to build.

The outside world never notices. External people still get a normal email reply. Only the internal thinking has moved.

At the start, this needs to be closer to a rule than a suggestion. Not forever. For the first few weeks, while the habit forms.

That feels heavy-handed to most managers, and the discomfort is worth examining. Nobody hesitates to say "expenses go in the expenses system". Communication deserves the same clarity. If it's internal collaboration, it goes in the channel. That's not micromanagement, it's an agreement about where work lives, which is exactly the thing most businesses have never made.

In my client's case, the ops lead set the line for his own small team first: no internal email, no side chats, channel only. Within days his own verdict was that it was becoming habitual "surprisingly quickly". The enforcement phase is short. The default it creates is permanent.

The wider agreement, covering files, tasks, meetings and communication across Microsoft 365, is what I call the What Goes Where Agreement, and the same logic runs through all of it: decide once, as a team, where each kind of work lives, and stop re-deciding it message by message. The thinking behind it is the same as [structuring Microsoft Teams properly in the first place](https://www.meetimeservices.com/blog/how-to-organise-microsoft-teams-small-business).

The payoff arrives with the second team.

When the next department moves over, they don't arrive into a theory. They arrive into a working example: a channel full of real decisions, real threads, a team that visibly runs its week in there. Adoption for team two is easier because team one held the line. By team four or five, the old way is what looks strange.

That's the real return on those two slightly awkward weeks. The first team isn't just changing its own habits. It's building the proof that changes everyone else's.

If your business is moving to Teams and you want the communication rules, the channel structure and the What Goes Where Agreement done properly, the [Chaos Cure](https://www.meetimeservices.com/chaos-cure) is the full self-guided playbook and workbook.

If you'd rather talk through your specific rollout, [book a discovery call](https://www.meetimeservices.com/how-we-can-help) and we'll look at it together.

Should small teams really use a channel instead of just chatting or emailing each other?

Yes, for anything work-related that isn't private. The value isn't convenience for the two people talking, it's visibility for everyone else: colleagues can contribute, decisions are findable, and the channel demonstrably being used is what convinces the rest of the business to adopt it.

How do you handle external emails when your team works in channels?

Copy the relevant content of the email into the channel, discuss and decide there, then reply to the external person by email as normal. External people still get email. Only the internal collaboration moves into the channel.

How long does it take for channel-based working to become a habit?

Around two to four weeks of deliberate effort for most teams, provided the line is held consistently: no internal email, no side chats about work topics. Teams that enforce it loosely take months, because every exception rebuilds the old habit.

Why does the first team in a Teams rollout struggle more than later ones?

Because everyone else in the business is still working the old way, and every email or chat they send pulls the first team back into old habits. Later teams arrive into a working example, which makes adoption progressively easier.

Is banning internal email too strict?

Treat it as a short enforcement phase, not a permanent decree. A few weeks of a clear, strict line builds the habit; after that the channel is the path of least resistance and the rule mostly enforces itself. Truly private or personal matters stay in private conversations.