Cleaning up Microsoft Teams: clear ownership instead of digital clutter

“We need to clean up Teams.” It sounds like a job for IT, but the underlying questions usually concern the business: Where does authoritative work happen, who decides on access, and what happens when a project ends? Without answers, new workspaces accumulate after every cleanup. Reducing their number does not automatically improve collaboration.

An SME with fifty well-managed workspaces can be better organised than one with ten ambiguous dumping grounds. What matters is whether employees can find the right place, recognise current information and identify someone who can answer questions. Our recommendation is to assess each workspace by its purpose and ownership rather than starting with a blanket deletion deadline.

This article combines Microsoft documentation checked on 28 September 2026 with ZUMENTIQ’s own operating model for Swiss SMEs. Suggested intervals, responsibilities and examples are recommendations, not product requirements or claimed customer outcomes. Licensing and available administration features need to be checked in the organisation’s actual tenant.

A team is connected to a Microsoft 365 group and other services. An inventory should therefore include documents and connected work tools. Microsoft outlines these relationships and the creation, operation and closure stages in its Teams lifecycle planning guidance. A visible team name is not a complete inventory.

Start with a simple register: name, purpose, accountable person, deputy, participating departments, external collaboration and next review date. Record where authoritative results are held and which dependent processes are known. A monthly export, linked form or automated workflow may matter to the business even when nobody posts much in the channel.

Avoid designing a register that nobody can maintain. Twelve carefully maintained fields are more useful than forty mandatory questions. Ask what decision each field enables. If there is no clear answer, it probably does not belong in the first version. The register should support work rather than become a separate project requiring constant explanation.

A workable policy fits on one page. It explains when a new workspace is justified, who owns it and how its closure is managed. Describe familiar working situations rather than every technical setting. The following table is our suggested minimum operating model.

These rules need a contact person who can explain them. Provide a short template for new workspaces and demonstrate it with an example. A naming convention such as “Project – Customer – Topic” may help, but do not put confidential information into widely visible names without considering who can see them.

Allow deliberate exceptions. A permanent service team does not need an artificial project completion date, but it does need a recurring review. A short-lived working group may not need a separate workspace if an existing structure already covers its purpose and participants. Follow the work rather than pursuing uniformity for its own sake.

Microsoft describes archiving and deletion as different operations. Archived teams can be reactivated. Archiving offers an option to make the associated SharePoint site read-only for members, while owners can still edit. Archiving therefore does not automatically make information immutable.

Your operating process should answer three separate questions: Is active collaboration still needed? Which information must remain available? When may the workspace be removed? Have the relevant business owners answer these questions before IT performs a technical action. An attractive, empty list is not a sufficient acceptance criterion.

Do not treat archiving as a substitute for a recovery strategy either. Recovering an accidentally modified file or an earlier version requires an appropriate, tested process. Requirements for evidence and retention need separate decisions. This article does not prescribe a universal legal retention period for Teams.

Before closing a workspace, make sure people know how to find information later. A brief closure note stating the outcome, information location, contact and date may be more useful than another layer of folders. Explain how someone can request that collaboration be resumed. Closure should leave a comprehensible record rather than an unexplained change in the interface.

Start with ten workspaces from different departments, deliberately including active, completed and ambiguous cases. The aim is to improve the process before applying it across the organisation. Use this suggested decision aid as the basis for a conversation:

If nobody responds, escalate to the responsible manager. During the first cycle, silence should not count as consent. Ownerless workspaces demonstrate that the previous responsibility model failed. Automatically deleting them would conceal the organisational issue rather than resolve it.

Keep decision records brief: date, decision maker, reason, action and unresolved dependencies. For disputed cases, record who must decide and by when. This turns a long list of ambiguous spaces into an actionable set of tasks with visible progress. It also prevents the same uncertainty from being rediscovered during every review.

Microsoft supports team expiration and renewal through group policies. Activity can trigger automatic renewal. Technical activity and business need are therefore different signals: an occasional visit does not establish that a workspace remains the right place to work.

Microsoft also documents ownership, inactivity and periodic business-need confirmation policies in SharePoint site lifecycle management. These capabilities belong to SharePoint Advanced Management. Check permissions, licensing prerequisites and actual effects before making them part of your process.

Our recommendation is to automate reminders and reporting first. A message to the responsible person with three clear options is often more useful than an elaborate workflow: still needed, prepare closure or clarification required. Each answer must lead to traceable action. An unattended mailbox is not an effective control.

Add automatic follow-up actions only after a successful manual cycle. Test absences, staff changes, unanswered requests and incorrect ownership assignments deliberately. Decide who can stop an operation. Automation accelerates misunderstandings too when the decision that precedes an action has not been clearly defined. Begin with a small scope whose outcomes somebody can actually review.

During week one, IT and an accountable business department agree the five minimum rules. Appoint someone to coordinate the process. Assemble the small register and select ten test cases. Explain that the initial objective is clarity. Employees should not feel compelled to distribute extra copies because they fear losing information.

During week two, discuss each case with its owners. Ask about actual working practices rather than just the date of the last message. Where are quotations finalised? Which documents does holiday cover need? Where would a new colleague look? These questions reveal whether the workspace fulfils its purpose and which information must remain available after closure.

During week three, implement approved corrections: add ownership, improve descriptions, repair outdated references and archive selected completed spaces through an agreed process. Verify access changes with the people affected. Hold a short support session so that questions do not disappear into separate private conversations. Record recurring questions as improvements to the guidance.

During week four, assess the outcome. How many cases are resolved? Which decisions took too long? Which rules were misunderstood? Adapt the template and choose the next manageable batch. A rolling process is usually easier to operate than one large annual campaign followed by months of inactivity. Give the next cycle an owner and actual calendar time.

The number of deleted teams is a poor headline metric. It rewards removal regardless of value. Instead, measure the proportion of reviewed workspaces with confirmed purpose and reachable ownership, the number of overdue decisions and the time needed to resolve questions. Set realistic targets after the first cycle rather than inventing them in advance.

Add a small practical exercise: someone unfamiliar with a project should use the workspace description to find the current result and the appropriate contact. If they cannot, orientation is probably missing. This is a qualitative working aid, not a scientific measurement or an assessment of individual employee performance.

Include ongoing maintenance effort in the assessment. Suppose twenty owners each spend fifteen minutes per quarter confirming their workspaces. That is five hours in total, excluding follow-up and technical administration. This hypothetical example makes effort visible; it does not promise savings. The relevant question is whether the additional clarity justifies the work.

Good rules also make staff transitions easier. Include workspace ownership in joining and leaving processes. A departing employee should not leave an unresolved business decision that only surfaces months later during the next cleanup. Make the transfer explicit and check that the new owner understands the purpose of the workspace.

Review the process itself periodically. If people repeatedly choose “still needed” without understanding the question, improve the prompt and guidance. A high response rate is useful only when the responses support real decisions. Keep the administrative burden proportionate to the business importance of the information.

Workspaces used jointly by several departments can be particularly difficult. A technical owner role does not by itself establish who can make a business decision. Appoint a lead for each shared workspace. Other departments should be involved in decisions affecting their information, but each next step still needs one clear sponsor.

Consider a hypothetical example: sales and engineering have prepared a customer quotation together. After the decision, the project channel is rarely used, but technical documentation remains important for operations. The relevant question is not whether the channel is old. Establish which outputs remain authoritative, who will maintain them and how participants will find their future location.

Do not rush to move or copy information. Check references, access and ongoing workflows. For a planned change, specify how affected colleagues will be informed and who will subsequently verify that required information remains accessible. Responsibility does not end with a successful technical click.

A simple escalation rule is often sufficient: the lead gathers unresolved points, the responsible manager decides on business need, and IT explains technical consequences. Questions about specific retention requirements go to the appropriate responsible specialists. The service desk should not have to guess at business decisions for which it has neither a mandate nor the necessary context.

Cleaning up Teams is a shared responsibility between business departments and IT. The business decides on purpose and need; IT implements the agreed treatment correctly. A small set of rules, reachable owners and regular decisions provide the foundation.

Start with ten workspaces this week. If you can then identify the purpose, owner and next action for each, you have achieved more than a cosmetic cleanup. ZUMENTIQ helps Swiss SMEs make collaboration and operations easier to understand and manage.