Unrestricted team creation is how a three-hundred-person company ends the year with nine hundred team spaces, a third of them ownerless duplicates. Over-restricted creation is how employees move company work into personal consumer apps. The workable middle is a short set of rules, enforced where possible and explained everywhere.
Decide Who May Create
Three common stances: everyone may create (fast, messy), nobody may create without approval (tidy, slow, drives shadow IT), or everyone may create but certain types require approval (the pragmatic middle). Whatever you choose, publish it in one sentence on the intranet; unwritten policy is enforced inconsistently and resented universally.
Naming Conventions That Survive Contact With Reality
- Prefix by type or department: "FIN-", "PROJ-", "CLUB-" so the list self-sorts and outsiders can guess ownership.
- Forbid years and version words in names; teams outlive them and duplicates appear.
- Cap length ruthlessly — long names truncate in every interface that matters.
- Where the platform supports enforced naming policies (automatic prefixes or suffixes on the underlying group), use them; enforcement beats education.
Ownership Is Not Optional
Require at least two owners per team at creation time. Single ownership guarantees orphans when someone changes job; zero ownership guarantees silence when a compliance question arrives. Make the second owner a role account or a deputy rather than a favour asked of a colleague — favours lapse.
Templates do the teaching
Team templates provision a standard channel set, default tabs and settings in one action: a "project" template with plan, risks and decisions channels; a "department" template with announcements and general. People follow structure they are given far more reliably than structure they are told about in a wiki page.
Approval Flows Without a Bureaucracy
If you require approval, keep it to one question answered by one role within one business day: "does an existing team already cover this purpose?" Most duplicate sprawl is prevented by that single check. Route requests through a form that auto-creates the team on approval, so the requester never touches settings and the naming policy cannot be bypassed.
The First-Week Checklist for New Team Owners
- Write a one-line purpose in the team description — future members read it before joining.
- Create only the channels you need this month; empty channels invite nothing.
- Post a welcome message with the team's norms: where decisions go, where files go, response expectations.
- Add the second owner and set an expiry review date in your own calendar.
When to Say No to a New Team
A channel inside an existing team serves most requests better than a new team: same membership overhead, less administrative surface. Reserve new teams for genuinely distinct membership boundaries — different confidentiality, different lifecycle, or different external participants. Saying "yes, as a channel" is the most useful sentence in team governance.
Creation rules keep the estate tidy at birth. The next chapter covers the other end of the lifecycle: expiration, archival and the quiet art of deleting things without losing history.
