Microsoft Teams has a reputation as the tool companies buy, install and then never use. The mailbox carries on, the WhatsApp group carries on, and Teams sits empty outside of scheduled calls. The problem is rarely the feature set — it is that people have no habit, and the first steps in an unfamiliar tool take effort. So start with lunch.
Why #lunch and not #projects
Intuition says: roll out a work tool starting with work. Create a project channel, move the documents across, hold the first meeting. Logical in theory. In practice the barrier is too high.
A project channel means “I have to write work things here, in front of my boss and our clients, in a tool I do not know yet.” People avoid the risk of making a mistake in an unfamiliar environment, so they go back to email.
A #lunch channel means “I can post that the pizza place round the corner has a deal on.” No risk, no expectations. But the app opens, the notification arrives, the reply comes naturally. After a week people have the habit of opening Teams. After two, they are asking whether they can have a channel for their own department.
What Microsoft Teams actually is
Teams brings four things together in one place:
Messaging — direct (1:1) and group messages, with formatting, reactions, threads and replies to specific messages. The equivalent of Slack or WhatsApp, but integrated with the rest of Microsoft 365.
Topic channels — spaces for conversations grouped around a topic, a department or a project. Each channel has its own threads, files and history. People added later see the whole history, unlike with email.
Video calls and telephony — online meetings with recording, transcription and automatic notes. With the right licence (Teams Phone) Teams replaces a traditional phone exchange.
Files and collaboration — every channel has a folder in SharePoint. Files are edited straight in the browser (Word, Excel, PowerPoint) with no downloading. Several people can edit the same document at once.
A four-week rollout plan
Week 1 — a low barrier to entry
Create one general channel and one unofficial one (#lunch, #announcements, #random). Invite everybody. Do not explain “how to use Teams” — just write something in #announcements and in #lunch. Let people reply.
Goal: everyone has opened the app at least once and written one message.
Week 2 — the first working channels
Pick one live task or project and create a channel for it. Move the email thread about that project into Teams: “we’re carrying on in here.” Attach the relevant files.
Goal: one project channel is alive and three to five people are using it.
Week 3 — calendar integration
Schedule the first meeting from Teams rather than from Outlook. Use recording or transcription. Share the notes in the project channel.
Goal: Teams replaces whatever external tool you were using for video calls.
Week 4 — structure
Assess what is working. Add channels for the departments or topics that emerged on their own. Set notifications sensibly — not everything needs to ring. Delete or archive whatever is unused.
Goal: the channel structure reflects how the company actually works, rather than how somebody imagined it before the rollout.
Common rollout mistakes
Too many channels at once. A five-level structure of departments, sub-departments and projects on day one. The effect: people do not know where to write, so they write nowhere.
“Everyone must use Teams from Monday.” Compulsion without habit produces resistance and pretend usage. Email carries on and Teams collects week-old unread messages.
No moderator in the first weeks. Somebody has to actively reply, encourage, and move email conversations across. Without that, channels go quiet after three days.
Forwarding emails into Teams. Instead of writing naturally, people paste whole email threads in. Teams starts to look like a dumping ground. Better to summarise in one sentence and link to the original.
Ignoring notifications. Teams notifies about everything by default. If nobody configures that, people turn the app off entirely because “it pings too much”.
Files and calendar integration
Every Teams channel has its own SharePoint folder — not as a metaphor, but as a literal directory in OneDrive for Business. Files dropped into a channel are available through the “Files” tab and at the same time through the SharePoint or OneDrive app.
The practical consequences:
- one document the team edits together, with no more “v2_FINAL_revised_definitive.docx”
- the document’s change history is visible in SharePoint
- access to a file can be controlled without emailing attachments around
The Teams calendar is synchronised with the Outlook calendar. A meeting invitation sent from Teams appears in Outlook and the other way round. Meetings with a Teams link can be created straight from Outlook, since the add-in installs automatically with the Teams app.
What Teams replaces — at a glance
| Tool replaced | Feature in Teams | Licence required |
|---|---|---|
| Zoom, Google Meet | video calls with recording and transcription | Business Basic |
| Slack | topic channels and direct messages | Business Basic |
| the WhatsApp group | informal channels | Business Basic |
| phone exchange | telephony with DDI numbers | Teams Phone (add-on) |
| shared network drive | files in SharePoint, per channel | Business Basic |
Teams as the hub, not just another tool
Teams can replace several things at once:
- Zoom or Google Meet (video calls)
- Slack (team messaging)
- the WhatsApp group (informal channels)
- a traditional phone exchange (with a Teams Phone licence)
- shared network drives (SharePoint)
The key word is “can”. Only if the rollout is gradual rather than all at once. Start with one thing. Lunch will do. 🍕
