Most Microsoft Teams setups fail. Not because the technology is wrong — but because nobody ever designed the system around it.

I worked with a company last year that had been using Microsoft 365 for three years. They'd had training. Everyone could create a channel, share a file, start a meeting. On paper, the rollout was a success.

In reality, half the conversations still happened in email. Files were scattered across OneDrive, SharePoint, desktops, and email attachments. Someone had set up 40 channels in the first week — nobody used any of them because nobody agreed what they were for. The weekly management meeting produced actions that disappeared into thin air because there was no shared task list and no follow-up process.

Three years of Microsoft 365. Thousands spent on licensing. And the team was working harder, not smarter.

Sound familiar? You're not alone. I've seen this exact pattern in hundreds of businesses — from five-person startups to multinational organisations. The details are always different. The pattern is always the same.

And the fix isn't more training. You can learn every Microsoft Teams feature from YouTube in twenty minutes. The hard part — the part that actually changes how your business operates — is building the structure and culture around the tools.

That's what this post is about.

Before you touch a single Teams setting, you need one document: a "What Goes Where" agreement. This is a one-page reference that tells everyone in your organisation where different types of communication and content should live.

It answers four questions: what goes in Teams channels? What stays in email? What goes in SharePoint? And what, if anything, belongs in chat?

I had a client last year — a 30-person professional services firm — where the managing director was sending project updates by email, the project managers were posting updates in Teams channels, and the admin team was using a shared drive. The same information was being duplicated in three places, and nobody trusted any single source. We sat down for an hour, built a What Goes Where agreement, printed it out, and stuck it on the wall next to every desk. Within two weeks, the duplicate communication had dropped by about 70%.
​
The agreement doesn't need to be complicated. A simple grid showing communication types on one axis and tools on the other is all you need. The important thing is that it exists, everyone has seen it, and it gets referenced when someone inevitably asks "should I email this or put it in Teams?"
​

The most common mistake when setting up Teams is creating channels based on the org chart. Marketing team, Sales team, Finance team. That mirrors your structure — but it doesn't mirror how work actually flows between those teams.

I once walked into a business that had created a Team for every department, then created identical channels in each one: "General", "Projects", "Admin", "Misc". Forty channels, all named nearly the same thing. Nobody could find anything. People were posting in the wrong channels because there was no meaningful difference between them. Within a month, everyone had gone back to email because it was "easier."

Instead, think about your channels in terms of what people actually collaborate on. Projects, clients, processes, and topics that cross departmental lines. A channel for a specific client project will get more use than a channel for "Marketing General" because it has a clear purpose and a defined set of people who need to be there.

Start with fewer channels than you think you need. You can always add more later, but you can't easily remove channels that people are already using. A good rule of thumb for a small business: one team per major function or project, with 3-5 channels in each. General, plus channels for specific workstreams.
​
Every channel should have a clear one-sentence description explaining what belongs there. If you can't explain a channel's purpose in one sentence, it's either too broad or unnecessary.
​

This is the part that most Teams rollouts skip entirely — and it's the reason most of them fail within six months.

You need explicit rules about how your team communicates in Teams. Not guidelines. Not suggestions. Rules that everyone agrees to follow. I've seen businesses transform their communication by implementing just five rules:

Rule 1: Use @mentions, not broadcast messages. In a channel, only @mention the people who need to act on or respond to your message. Everyone else can read it when they have time. This single rule prevents the notification overload that causes people to mute channels — which is the beginning of the end for any Teams rollout.

Rule 2: Channels for ongoing work, chat for quick questions. If a conversation will be useful to reference later, it belongs in a channel. If it's a genuinely quick, one-off question between two people, chat is fine. The test: "Will anyone else ever need to find this conversation?" If yes, it goes in a channel.

Rule 3: Email for external, Teams for internal. This is the simplest rule and the one that makes the biggest difference. If the communication is within your organisation, it belongs in Teams. Email is for external contacts, formal announcements, and anything that needs to reach people outside your M365 environment.

Rule 4: Files live in SharePoint, not in chat. When you upload a file to a Teams channel, it automatically saves to SharePoint — visible, searchable, version-controlled. When you upload a file in chat, it goes to your personal OneDrive. That means chat files are essentially invisible to everyone else. One of my clients discovered they had 18 months of project files trapped in old chat conversations that nobody could find. Get your team into the habit of sharing files in channels, not chat.
​
Rule 5: One topic per conversation. Don't hijack an existing thread to discuss something unrelated. Start a new conversation. This seems minor but it's the difference between channels that are searchable and useful versus channels that are an unreadable mess six months from now.

Here's something that's probably happening in your business right now.

Someone created a group chat in Teams as a quick way to keep the team in the loop. Made sense at the time. But every message in a group chat interrupts everyone by default — whether they need to see it or not.

So what happens? Everyone pragmatically mutes the chat. Now nothing gets seen. Topics go off on tangents you can't separate. New starters get added and are immediately overwhelmed by thousands of messages of context they can't parse. The whole thing becomes noise that everyone ignores.

That's what I call the group chat death spiral. And once it starts, it's almost impossible to reverse without starting fresh.

Channels fix this — but only when combined with the @mention rules above. Without rules, channels become the same noisy mess that group chats were. The structure is necessary, but not sufficient. Structure plus rules is what works.

If your team is currently using group chats for ongoing work conversations, the single biggest improvement you can make is migrating those conversations to properly structured channels with clear rules about who gets @mentioned and when.
​

Setting up Teams correctly is only half the battle. The other half is getting your team to actually use it — and keep using it after the initial excitement wears off.

This is where most DIY Teams rollouts fall apart. The structure is fine, the channels make sense, but six weeks in, people quietly revert to email because old habits are comfortable and nobody is holding them accountable to the new way of working. I've seen it happen so many times that I can almost predict the timeline: enthusiasm in week one, mixed usage in week two, creeping reversion in weeks three to four, and full retreat to email by week six.

A client once told me: "We rolled out Teams three times. Each time it stuck for about a month, then everyone went back to email." When I asked what they'd done differently each time, the answer was the same: they'd set up the technology and hoped people would use it. No communication plan, no rules, no accountability, no check-ins.

Effective change management for a small Teams rollout doesn't need to be complicated, but it does need to be deliberate. Communicate why you're making the change (not just what). Start with a pilot group before rolling out to the whole organisation. Set a 90-day timeline and check progress at regular intervals. And accept that the "uncomfortable middle" — weeks three through six, when enthusiasm dips and resistance peaks — is normal and temporary.

The businesses that see lasting results are the ones that commit to the method for three months and push through that middle phase. On the other side is a team that works differently. Better. Calmer. More productively.
​

How should I structure Teams channels for a small business?
Start with one team per major function or project, with 3-5 channels in each. Include a General channel plus specific channels for workstreams. Name them clearly, keep descriptions up to date, and don't create channels "just in case" — add them when there's a genuine need. Structure channels around how work flows, not around the org chart.

When should I use Teams chat vs channels vs email?
Use channels for ongoing work conversations that others may need to reference. Use chat for quick, one-off questions between two people. Use email for external communication and formal company-wide announcements. The simplest rule: internal goes in Teams, external goes in email.

What is a "What Goes Where" agreement?
It's a one-page document that tells everyone in your organisation where different types of communication and content should live — what goes in Teams, what stays in email, what goes in SharePoint, and what belongs in chat. It eliminates the daily confusion of "should I email this or put it in Teams?" and stops files from being duplicated across multiple locations.

How do I get my team to actually use Microsoft Teams?
Don't just set it up and hope for the best. Communicate why you're changing, not just what. Set clear communication rules that everyone agrees to. Start with a pilot team. Set a 90-day implementation timeline. Check progress at regular intervals and push through the uncomfortable middle phase (weeks 3-6) where people want to revert to email. The businesses that succeed are the ones that commit to 90 days.

Why isn't Microsoft 365 training working?
Training teaches features — how to create a channel, how to set up a Planner board. But knowing how to create a channel is worthless if nobody agreed which channels to create, or why, or what the rules should be for using them. What's missing is the system: the structure, the agreements, and the culture around the tools. That's what actually changes how a business operates — not knowing which buttons to click.

How do I stop my team using email instead of Microsoft Teams?
Set a clear rule: internal communication goes in Teams, external goes in email. Then enforce it. When someone sends an internal email, reply in Teams and reference the email — this gently trains the habit. The "What Goes Where" agreement makes the rule visible and shared. Most teams transition within 2-3 weeks once the rule is explicit and consistently applied.
​

This blog post covers the principles — the thinking behind a good Teams setup. But principles alone don't build an implementation plan for your specific organisation. The full MeeTime Method — the exact process I use with consulting clients — takes you from discovery (understanding what's actually going wrong) through design (building the structure) through to a 90-day implementation plan that makes it stick.

I've written the whole method down for the first time as a self-guided playbook and interactive workbook called The Microsoft 365 Chaos Cure. Only available to my email subscribers:

Join 1,400+ leaders getting weekly M365 tips — and get first access to the Chaos Cure →
​

Gavin Jones is the founder of MeeTime, a Microsoft 365 consultancy helping small and medium-sized businesses get more from the tools they already pay for. He has helped hundreds of businesses through direct consulting and hundreds of thousands of people through his YouTube channel.