Every collaboration platform ships with the same explosion risk: creation is open, naming is free-form, and the result is a list nobody can read by next summer. Rules cost a little now, while the alternative — a cleanup project with a steering committee — costs a lot later.
Name the scheme, then hide the rest
A workspace name is metadata the machine reads first. Give it three parts: unit, topic, audience. Enforce the prefix through templates, name examples in the rollout guide, and let the sensible middle stay flexible — specific naming conventions collapse when they touch every corner of a growing organisation.
- Define who creates workspaces: everyone (with naming rules), a nominated pool, or no one outside IT.
- Define ownership: at least two owners per workspace — one person leaving is a normal event, not an exception to the archive rule.
- Define the archive day: a workspace that has never had a conversation in ninety days gets reviewed, renamed or retired.
Bottom line
Templates do the work of ten managers. A starter structure — General, Announcements, Planning — lands every new workspace in the same shape, gives newcomers the same landmarks, and turns the naming decision from a creative act into a fill-in-the-blank.
Rules must have a mechanism, not an opinion
Governance fails as a document and works as a mechanism. If the rule is “annual review”, put the review in the calendar system with a reminder that arrives in the owner’s inbox. If the rule is “two owners”, make the second owner automatic — the platform, unlike a policy page, is excellent at remembering to nudge.
