Teams Governance: Order Without Killing the Thing People Like About It

Every business that adopts Microsoft Teams runs the same experiment, and it always produces the same result: within eighteen months there are 240 teams for 60 people — “Marketing,” “Marketing 2024,” “Marketing NEW,” a team per client, a team per whim, half of them silent since creation, each secretly a SharePoint site with permissions and data. The sprawl isn’t a user failure; it’s the default settings working as designed — anyone can create anything, forever. Governance is the fix, and it has its own failure mode worth naming up front: clamp down too hard and people simply retreat to email and unsanctioned tools, which is worse. The goal is the light-touch version: enough order that the platform stays navigable and governable, little enough friction that people still want to work there. Here it is.

Why sprawl actually costs (it’s not aesthetics)

A messy Teams list looks like a tidiness problem; the real costs are structural. Findability: when three teams plausibly hold the client’s files, people guess, duplicate, and fragment the record. Security surface: every team is a site with membership, sharing, and possibly guests — 240 of them is 240 access lists nobody reviews. Orphaning: teams outlive their creators, and an ownerless team is ungoverned data — nobody to approve a member, answer for the contents, or decide its fate. Lifecycle debt: stale teams accumulate retention-relevant data and clutter every future migration, audit, and backup conversation. None of these hurt on day 30; all of them compound.

The five light-touch rules

1. Put a speed bump — not a wall — on creation. The single highest-leverage setting: restrict who can create new teams (a group of sensible owners per department, or a lightweight request that’s answered within a day — speed is what makes people use the sanctioned path). The point isn’t gatekeeping; it’s that a five-second “does this already exist?” check at birth prevents most of the sprawl at zero ongoing cost. Channels within existing teams stay wide open — that’s where the day-to-day flexibility lives, and it costs nothing.

2. Name things like you’ll have 200 of them. A convention — DEPT - Purpose or CLIENT - Project — plus a rule against “New/Final/2024” suffixes. Trivial-sounding; it’s the difference between a directory and a junk drawer, and it makes every later audit, access review, and migration cheaper.

3. Two owners per team, always. Owners approve members, manage guests, and answer for contents — and single-owner teams orphan the day that person leaves. Two owners is the whole redundancy plan, enforced at creation and repaired at offboarding.

4. Govern guests where the data says to. Guest access is legitimately valuable — external collaboration is the point — but it’s access into your SharePoint, so it follows the classification map: open on project teams, restricted or off on the sensitive ones, and reviewed periodically like the vendor access it is — “which guests remain in which teams, and is each engagement still live?”

5. Give teams an ending. The rule nobody sets and everyone needs: teams expire. Microsoft 365 supports expiration policies natively — owners get prompted to renew; unrenewed teams archive automatically (recoverable, then eventually subject to your retention decisions). Set it to a year, and the stale majority prunes itself with no meetings, no cleanup projects, no archaeology — the entire lifecycle problem, solved by one policy quietly asking “still using this?”

Rolling it out in an installed base

Greenfield governance is easy; most businesses adopt it at team #240. The sequence that works: turn on the rules for new teams first (creation, naming, owners, expiration) — the sprawl stops growing immediately · then run one honest cleanup pass on the backlog: owners confirm keep/archive per team, ownerless teams get adopted or archived, with backup in place before anything is deleted · then let the expiration policy hold the line forever. Announce the why in one paragraph — findability and security, not tidiness for its own sake — and the pushback mostly evaporates; people hate sprawl too, they just hate friction more.

The bottom line

Teams governance done right is five settings and a naming habit: a speed bump on creation, names that scale, two owners, guests governed by data sensitivity, and automatic expiration. It’s an afternoon to configure, it’s nearly invisible to daily users, and it’s the difference between a collaboration platform and a landfill with a search bar — while leaving intact the one thing that made Teams win in the first place: it’s easy. Keep it easy. Just not that easy.