M365 Playbooks

Workspace· Operations

Set up a Team that works

Last reviewed
Version
2
For
Workspace owner

Written by · 2 min read

Situation

We're setting up a new Team and every department wants private channels.

At a glance

Outcome

A Team with channels that match how the group works, the right permissions, and members who know how to use it from day one.

Benefits

  • Faster collaboration from launch. How to measure: Active members in the first month.
  • Fewer private and shared channels created by default. How to measure: Private and shared channels per Team.

Resources required

Who is involved
Two Team owners, a few members for the pilot.
Skills
Teams channel types and permissions.
Effort
Half a day to set up; an hour to launch.
Duration
One to two weeks.

Risk of not doing it

Channels sprawl and private channels hide information from the people who need it.

Put it in place

Change actions follow the lean change framework: Inform → Explain → Sustain.

Admin and change actions for each phase
PhaseAdmin actionChange action
Discover

List the work the Team supports and who needs access to what.

Inform

Tell the members why the Team is being created and what it replaces.

Pilot

Create standard channels first. Add a private or shared channel only where access truly differs.

Explain

Walk two or three members through the layout and adjust from their feedback.

Deploy

Add members, pin key files and set channel moderation where needed.

Explain

Launch with a short welcome post explaining where things go.

Handover

Record the owners, channel purposes and guest settings.

Sustain

Agree who answers questions and when the owners review membership.

Making it scale

Team templates and tenant defaults for guests and sharing set the basics, so every new Team starts the same way.

Partly enforced. The gaps are a risk until a mechanism covers them.

Avoiding common pitfalls

  1. A private channel for every department

    Use standard channels unless a group's access genuinely differs. Each private channel has its own separate site.

  2. Launching an empty Team

    Move the first files and conversations in before inviting everyone.

Checkpoints

  • Every channel has a stated purpose.
  • Two owners are in place.
  • Members have posted in the first week.

Sources

  1. Overview of teams and channels in Microsoft Teams (Microsoft Learn)
  2. Private channels in Microsoft Teams (Microsoft Learn)
  3. Shared channels in Microsoft Teams (Microsoft Learn)
  4. Get started with team templates in the Teams admin center (Microsoft Learn)
  5. Private channels in Microsoft Teams (Microsoft Learn)
  6. Shared channels in Microsoft Teams (Microsoft Learn)

Reviewed against

Changelog

Changelog (2 versions)
Published versions of this playbook
VersionDateAuthorChange
2Sev DerghazarianAdded guidance on shared channels. Placeholder entry to exercise the changelog.
1Sev DerghazarianFirst published. Placeholder text for the pilot build; replace before launch.