Ten years ago the mess was a shared network drive. A folder called Final, another called Final_v2, another called Final_USE_THIS, and one lonely folder named after somebody who left in 2018. Everyone agreed it was bad. Everyone also agreed that fixing it was somebody else’s job.
Then chat and collaboration platforms arrived and promised to end all that. In many ways they did. But if you have been on one a few years, look around: how many channels have not had a message since spring, how many teams exist for projects that shipped or died, and could a new hire find last quarter’s proposal template without asking three people? That is sprawl. It is the shared drive problem in new clothes, and cleaning it up is mostly a series of decisions rather than a technical project.
Why Sprawl Happens, and Why It Is Not Laziness
Sprawl happens because creating a workspace is easy and closing one is nobody’s job. Somebody needs a place to coordinate a hiring push, so they make one. The hire happens. The workspace stays. Multiply that by three years and a dozen enthusiastic people and you get an organization where the tool that was supposed to reduce clutter is now generating it.
There is a structural reason too. In the Microsoft collaboration stack, creating a team also creates a group behind the scenes, and that group brings a document library, a calendar, and a mailbox. One click creates several containers at once. Microsoft’s lifecycle governance guidance, which we read in 2026, describes this relationship and recommends governing the group lifecycle as the way to govern team lifecycle. Names and packaging change often, so confirm what your plan includes.
Sprawl also has a cousin: tools nobody approved. If your people are creating workspaces in three different platforms, you have a bigger issue than clutter, and we covered that in our piece on the hidden risk of unapproved software inside your own organization.
Start With an Audit of What Is Actually Alive
Do not start by deciding what to keep. Start by finding out what is used. Your administrative console has a teams list showing membership and status, and your usage reporting area shows activity over a rolling window. Pull both, then sort every workspace into one of three buckets.
- Active and healthy. Regular messages, a clear owner, files people open. Leave it alone. Resist the urge to reorganize things that work.
- Finished. The project ended. The content still matters. These get archived, not deleted.
- Genuinely empty. Created by accident, one message, no files. These are the only real candidates for deletion.
Archive First, Delete Almost Never
According to Microsoft’s Teams documentation as we read it in 2026, archiving a team keeps the content in place. You can still view all the team activity in standard and private channels, along with files and chats, and the material stays searchable. You can still add or remove members and update roles, and you can choose to make the associated document library read only for members while owners keep the ability to edit. Archived teams can be reactivated later from the administrative console.
Deleting is a different animal. The same documentation from 2026 says deleting a team also deletes the activity in its channels, its files, and its chats, and warns that you cannot directly restore a deleted team. There is a soft delete window on the underlying group, documented at 30 days, during which an administrator can restore it. Microsoft’s advice is blunt and correct: archive first, and postpone deletion until you are sure.
Naming Conventions People Will Actually Follow
Every naming convention document we have seen was too long. Here is the whole thing: a person scanning thirty names should be able to tell what each one is for and whether it concerns them. Everything else is decoration.
- Lead with the category. Something like Dept, Client, Project, or Ops at the front of the name. Sorted alphabetically, related workspaces cluster together for free.
- Let the platform enforce it if it can. Microsoft documents naming policy features that can add a required prefix or suffix and block specific words in group names. Whether that is available to you depends on your licensing, which changes, so check what your current plan includes.
Chat, Channel, or Document Library?
Most of the confusion in a collaboration platform is not about where things are stored. It is about people using the wrong container for the job. A simple rule set clears up more than any reorganization will.
- Chat is for things that expire. Are you free at two? Running late. Did you see that email. Nobody will ever search for these, and nobody joining the company later needs them.
- A channel is for a conversation someone else may need to read. Decisions, context, why we chose the vendor we chose. If the answer to who might need this later is anyone but the two of us, it belongs in a channel.
- The document library is for things that have a final version. Contracts, templates, policies, the current price sheet. If a document is the answer to a question rather than a step toward one, it should live in a library with a real folder structure.
- Never attach a file to a chat if it matters. Files shared in one to one chat land in the sender’s personal storage. When that person leaves, the file goes with them unless someone intervenes. This is the single most common way small companies lose documents.
A Creation Policy That Does Not Strangle Anyone
Here is where we get a little contrarian. The instinctive fix for sprawl is to take away the create button and route everything through IT. We usually advise against it.
Microsoft’s own lifecycle governance guidance, reviewed in 2026, warns that limiting group and team creation can slow productivity, because many services in the platform require a group to exist in order to function. Lock the door too hard and people do not stop collaborating. They go collaborate somewhere you cannot see, which trades a tidy problem for a genuinely risky one. Restriction also has a cost you will feel in your own time, and we have made the case before that saving time usually beats saving money.
A middle path works better for most small and mid sized businesses. Let people create, but attach three light conditions.
- Two owners, always. One owner is a single point of failure the day that person resigns or goes on leave.
- A one line purpose in the description field. Thirty seconds of typing at creation saves an hour of archaeology later.
- An expiration and renewal check. Microsoft documents an expiration policy where the clock starts at creation or last renewal, owners are notified as the date approaches, active groups renew automatically, and workspaces that go unrenewed are removed with a restore window. Feature availability depends on licensing, so confirm what you have.
The Bottom Line
Audit what is alive. Archive what is finished instead of deleting it. Rename the confusing ones. Teach people the difference between a chat, a channel, and a document library. Then add a light creation policy and a reminder to run the same pass twice a year. That is a day of work up front and an hour a year after, and it is the difference between a tool your team trusts and one it tolerates.
If your collaboration platform has quietly turned into a place where files go to hide, we can sort it out without a disruptive migration or a policy nobody reads. We will pull the real usage data, tell you what is active, archive the rest safely, and set up a naming and creation approach your team can live with. Contact us today.
Sources:
Comments are closed