All posts

Getting the Most Out of Microsoft 365 – Why Many SMEs Leave Value on the Table

Microsoft 365 Pascal Zumstein · May 18, 2026 · 10 min read

Microsoft 365 is standard equipment in most SMEs by now. The licenses are paid, Outlook is running, Word and Excel are used daily. And yet I hear the same sentence in nearly every consulting engagement: "We have Microsoft 365, but we really only use email and Office." This is not the exception. It is the norm. And it means that businesses are paying month after month for a platform whose greatest value they never touch.

The issue is rarely a lack of interest. Most managing directors and IT managers know that their M365 subscription contains far more than Outlook and Word. But day-to-day operations leave little room to explore it systematically. So the status quo persists: the platform is used as a slightly better email solution, while capabilities like SharePoint, Teams, Power Automate, or Planner remain untouched — or were introduced half-heartedly and quietly abandoned.

This article shows where the biggest leverage lies, why the typical rollout approach fails, and how SMEs can use Microsoft 365 in a way that actually makes a difference.

The core problem: technology without a concept

Microsoft 365 is not a single application. It is a platform with over thirty interconnected services — or disconnected ones, if you treat them in isolation. That is exactly what happens in many SMEs. Teams is introduced as a replacement for Zoom. SharePoint becomes a dump for a few documents. Planner serves as a personal to-do list. Each service is adopted on its own, without an overarching concept behind it.

The result is predictable: the tools generate no perceivable value, employees see no reason to change their established workflows, and after a few weeks everything reverts to the old way. Files are emailed again, information is stored in personal folders, coordination happens over phone calls and hallway conversations.

The fault does not lie with the employees. It lies in introducing a tool without first clarifying which problem it is supposed to solve. Microsoft 365 delivers value only when it is understood as a connected system — and when the rollout is built around specific workflows rather than feature lists.

Where the biggest value lies

Not every M365 service is equally relevant for every business. But there are four areas where the platform can make a measurable difference for virtually any SME — if it is used correctly.

Document management with SharePoint and OneDrive. This sounds unspectacular, but it is the area where most SMEs achieve the greatest immediate gain. Instead of storing files on a local file server where version chaos, inconsistent access rights, and poor search functionality are part of daily life, SharePoint provides a structured, searchable, and versioned repository. Every document exists in a single version. Multiple people can work on it simultaneously. And the search finds content — not just file names.

The difference in practice: an employee is looking for a quote prepared three months ago. On the file server, that means clicking through folders, guessing which version is current, perhaps asking a colleague. In a well-structured SharePoint environment, it means entering a search term, opening the document, and getting back to work. This sounds like a small difference. Multiplied across dozens of such searches per day and dozens of employees, it adds up to hours per week that could be spent more productively.

From practice: An engineering firm with 40 employees migrated its project documentation from a classic file server to SharePoint. The actual migration took two weeks. The real effort lay in the preparation: cleaning up the folder structure, defining an access rights concept, establishing naming conventions. After three months, the average document search time had dropped from an estimated eight minutes to under two. The file server was shut down.

Collaboration in Teams — properly structured. Microsoft Teams is already deployed in many businesses, but often only as a chat and video tool. Its real strength lies elsewhere: Teams can serve as a central workspace where communication, documents, tasks, and information related to a project or topic are bundled together. Instead of scattering information across email, chat, file servers, and verbal agreements, everything lives in one place.

For this to work, however, it requires clear structure. The most common cause of Teams frustration is not the tool itself but the way it is rolled out: everyone creates teams and channels at will, there are no naming conventions, no governance, no rules. Within a few months the environment is a mess, and employees return to email because at least they know their inbox.

The solution is not fewer teams but better-organized teams. A clear framework that defines when a team is created, how channels are named, where documents are stored, and who is responsible for maintenance. This sounds like bureaucracy but can be implemented with just a few rules in practice — and it is the difference between a chaotic and a productive Teams environment.

Automation with Power Automate. Many SMEs have repetitive processes that nobody questions because they have always been done that way: an Excel list manually updated every Monday, an email notification sent by hand when a document is approved, a sign-off process handled through print, signature, and scan.

Power Automate, included in most M365 license plans, can automate such workflows — without programming. A flow can automatically send a notification when a new document is uploaded to a specific folder. It can route approval requests to the right person and record the outcome. It can transfer data from a SharePoint list to an Excel table or vice versa.

A single automation may save only five minutes per week. But five such automations add up to nearly half an hour. Ten add up to an hour. And the real benefit is not just time savings but reliability: automated workflows never forget, never make typos, and keep running when the responsible employee is on vacation.

Task and project tracking with Planner and To Do. Not every SME needs a professional project management tool. For many teams, a simple visual task board integrated directly into their existing work environment is sufficient. That is exactly what Planner and To Do provide. Planner lets you organize tasks in a Kanban board, assign responsibilities, and track progress — directly within Teams. To Do adds personal task lists that sync with Planner and Outlook.

For SMEs that currently distribute tasks via email and check progress verbally, this represents a significant step forward. Not because the tool is particularly sophisticated — more capable alternatives exist — but because it is already available, costs nothing extra, and integrates seamlessly into the existing workday.

Why the typical rollout fails

Most M365 rollouts in SMEs follow the same pattern: the IT department or an external provider sets up the technical infrastructure. There may be a short training session. And then employees are expected to adopt the new tools on their own. This almost never works.

The first reason is that training often focuses on the wrong thing. It shows where to click but not why. An employee who is shown how SharePoint works will still not use SharePoint if they do not understand which problem in their daily work it solves. Training must start with the work process, not the tool.

The second reason is a lack of commitment. If both the old way and the new way remain acceptable, nobody will switch. Why would someone store documents in SharePoint when the colleague next door keeps sending them via email? Successful rollouts define a clear point in time when the new way becomes the expected way. This does not mean flipping a switch overnight. But it does mean there is a clear direction, and it is backed by leadership.

The third reason is insufficient support after rollout. The first week with any new tool is bumpy. If there is nobody during this phase to answer questions, help with problems, and absorb frustrations, the perceived pain outweighs the perceived benefit. And frustration drives people back to what they know.

From practice: A professional services firm introduced Teams and SharePoint simultaneously, accompanied by a two-hour training session. After six weeks, fewer than 20 percent of employees were actively using the new tools. The second attempt — six months later — went differently: the rollout was limited to one department, the training was built around specific work processes, and an internal contact person was available for questions for two weeks. After one month, the adoption rate in that department exceeded 80 percent. The other departments followed step by step.

A pragmatic path to better usage

The good news is that you do not have to do everything at once. And you do not need to use every feature of Microsoft 365 to see real value. The pragmatic path means focusing on where the biggest leverage lies — and moving forward step by step.

Step one: take stock. What is actually being used today? Where do the biggest friction points arise in daily work? Where do employees spend the most time searching for information? Where do decisions fall through the cracks? Where is work being duplicated? The answers to these questions reveal where the greatest benefit lies — and therefore, where to start.

Step two: implement one specific use case. Do not roll out the entire platform at once. Improve one specific workflow instead. For example: migrate one department's project documentation to SharePoint. Or move a team's internal coordination from email to Teams channels. Or automate one recurring manual process with Power Automate. A single concrete success builds trust in the platform and makes the benefit tangible.

Step three: define structure and rules. Before expanding to more departments or use cases, establish a basic set of rules: How are teams and channels named? Where are which documents stored? Who is allowed to create new teams? What happens to inactive teams? These rules do not need to be extensive — but they must exist before the environment grows.

Step four: bring people along. Provide training that shows how a tool helps with employees' actual workflows, rather than abstract feature overviews. Identify internal champions who serve as points of contact. And ensure leadership not only permits the new ways of working but models them. If the manager continues to distribute everything via email, the team will not adopt Teams channels.

What many underestimate: security and governance

Beyond productivity, there is another dimension that SMEs frequently neglect with Microsoft 365: security and governance. The platform offers extensive capabilities for protecting data, managing access rights, and meeting compliance requirements — but only when these features are actually configured.

In practice, I regularly encounter M365 environments where every employee can access all SharePoint sites, where no policies for external sharing exist, and where multi-factor authentication has not been enabled. These are not exotic security requirements. They are fundamentals that should be configured in every environment — and they can be implemented with the built-in tools that M365 provides.

Especially for Swiss businesses subject to regulatory requirements or processing sensitive client data, this is not an optional topic. It is an obligation. And the good news is that most security features are already included in common license plans. They simply need to be activated and properly configured.

Conclusion: buy less, use better

Most SMEs do not need additional tools. They need a better approach to the tools they already have. Microsoft 365 is present in the vast majority of businesses, but very few use it in a way that unlocks its full value.

Getting there is not a massive undertaking. It starts with an honest assessment, one specific use case, and a willingness to change how work gets done. The technology is there. The licenses are paid. What is missing in most cases is not budget or functionality — it is a clear concept, a structured rollout, and someone who builds the bridge between the platform's capabilities and the business's actual needs.

That is precisely what makes the difference: not more technology, but the right connection between technology and everyday work.

Want to get more out of Microsoft 365?

I help SMEs leverage Microsoft 365 with a clear concept, practical rollout, and measurable value for their day-to-day operations.

Book a free consultation