Managing growth.
WHAT GOVERNANCE COVERS
Who may create teams Naming conventions Classification and sensitivity Guest access Retention and archiving Ownership requirements
WHY IT MATTERS
Without it, hundreds of teams accumulate, most inactive, and content becomes unfindable.
WHAT TO IMPLEMENT
Naming policies, applied automatically Expiry policies, requiring owners to confirm a team is still needed A request process, if creation is restricted
WHAT EXPIRY POLICIES DO
Prompt owners periodically, and archive or delete teams nobody confirms.
WHAT TO CONFIGURE CAREFULLY
What happens on expiry, and whether content is recoverable.
WHAT TO DECIDE ABOUT GUESTS
Whether external people may be added, and by whom.
WHAT TO REVIEW
Guest accounts, periodically.
WHY
They persist long after the collaboration ended.
WHAT TO ESTABLISH ABOUT RETENTION
How long content is kept, and whether it may be deleted.
WHAT TO DOCUMENT
The rules, so administrators apply them consistently.
WHAT TO MEASURE
Active teams against total teams.
