Have you ever opened your laptop on a Monday morning and felt tired before you even started?
Not because of the people. Not because of the work.
But because you already know what’s waiting for you:
If that sounds familiar, you are not alone.
I have spent more than 35 years helping everyday users and busy leaders work smarter with Microsoft 365; Teams, SharePoint, OneNote, Outlook, Copilot, and more. In that time, I have trained over 28,000 professionals across Canada, the USA, Australia and beyond.
And despite all the powerful technology available, one thing keeps showing up, over and over:
Work feels harder than it should.
That is not a feature problem. It is not a training problem. It is a chaos problem.
And that is exactly why I created the Microsoft 365 Chaos Scale.
Let me paint a picture you might recognize.
You are leading a project. Everyone is working hard. But…
➡️ Files are stored in four different places, depending on who touched them last.
➡️ Someone mentions a “new version” you have never seen.
➡️ You search your email and find five attachments that all look similar.
➡️ Copilot gives you an answer that sounds plausible, but you are not sure if it is based on the right files.
By the time you sort out what is real, half the meeting is gone.
Nobody did anything wrong. There is no villain in this story. It is just what happens when structure grows by accident instead of by design.
That is Microsoft 365 chaos.
You feel it as frustration, duplication, hesitation, “Is this even the right file?”, and exhaustion: “Why is this so hard?”
And it shows up long before anyone starts using words like “governance” or “information architecture.”
For years, I watched leaders try to solve this feeling with more tools.
➡️ “Let’s add a new app.”
➡️ “Let’s do another demo.”
➡️ “Let’s roll out Copilot, maybe AI will fix it.”
Sometimes those steps help. But more often, they just add another layer on top of an already messy environment.
What was missing was a way to name the chaos in plain language. Not a technical audit. Not a maturity model buried in a consulting report.
Just a simple, honest scale that lets you say:
“We are here right now. This is what it feels like. This is what it is costing us.”
That is the role of the Microsoft 365 Chaos Scale. It turns a vague sense of “things are messy” into a clear picture you can actually talk about, with your team, your leadership, and your IT department.
I worked with an organization that believed they were, in their own words, “pretty organized.”
They had SharePoint sites for every department. Teams channels for major projects. A few naming conventions written down somewhere. On paper, it looked reasonable.
But when we walked through what actually happened on a typical day, a different story came out:
➡️ Marketing kept its master files in SharePoint.
➡️ Finance kept its master files on a network drive.
➡️ Operations kept its master files in email.
Everyone had a system. Nobody had the same system.
In a single meeting, I watched three versions of the same spreadsheet get referenced, two different sets of numbers get presented, and one person quietly unsure which version was “official.”
They did not have a technology problem. They were living at what I call Level 2 to 3 on the Chaos Scale: File Chaos and Team Chaos.
Once they could see that clearly, the conversation shifted. Instead of “we need more training,” it became: “we need one place for the truth, and habits that match it.”
That is the power of having a framework. It moves you from vague frustration to a clear starting point.
As you read through each level, notice which one feels most like your daily reality right now.
This is where chaos begins, and it is more common than most people realize.
You see it when:
✔️ Email is the default home for everything, decisions, files, updates, approvals.
✔️ Attachments are how documents travel through the organization.
✔️ Important information is buried in long threads with twelve people CC’d.
Microsoft Outlook is a fantastic communication tool. But when Outlook quietly becomes your document management system, chaos begins.
You feel Level 1 as: “My inbox is my to-do list” and “If it’s important, it’s somewhere in my email.”
At Level 2, files are scattered across locations and nobody is entirely sure what is current.
Common signs:
✔️ Network drives with nested folders nobody can explain.
✔️ Personal OneDrive files being used as official documents.
✔️ SharePoint sites, Teams channels, and shared drives all holding similar content.
Daily conversations sound like: “Can someone send that to me again?” and “Which version is correct?” and “Do you have the one with the latest numbers?”
You feel Level 2 as friction. Work stops while everyone hunts, checks, and re-sends.
Level 3 shows up when each team is organized in its own way, but the organization as a whole is not.
You see it when:
✔️ Different departments maintain their own copies of shared documents.
✔️ Status reports vary depending on who you talk to.
✔️ People distrust central information because their team has a “better version.”
Every individual team may feel fine on its own. But cross-team work feels slow and confusing.
You feel Level 3 as: “I’m not sure whose information to trust” and “I wish everyone saw the same thing.”
At Level 4, the way work gets done is inconsistent and hard to describe.
Signs of Process Chaos:
✔️ Common workflows rely on unwritten steps.
✔️ New staff learn processes by shadowing one person instead of reading clear guidance.
✔️ Automation is difficult because nobody agrees on the right process.
People are doing their best. They just do not have a shared map.
You feel Level 4 as: “We reinvent this process every time” and “We can’t easily scale or delegate this work.”
Level 5 is where chaos becomes truly expensive.
This is what happens when critical knowledge leaves your organization:
✔️ Only one person understands a key system or workflow.
✔️ Documentation is missing, outdated, or impossible to find.
✔️ Retirements, resignations, or reorganizations quietly erase years of experience.
After someone leaves, you hear: “We’re not sure how they did it” and “We think the files are somewhere, but we can’t piece it together.”
You feel Level 5 as risk and regret: “We should have captured this sooner.”
I have seen this scenario play out more times than I can count, and it is always painful. The good news is that it is entirely preventable with the right habits and the right tools.
Here is something leaders often underestimate: chaos rarely lives at just one level.
It moves.
↗️ Email Chaos becomes File Chaos.
↗️ File Chaos becomes Team Chaos.
↗️ Team Chaos becomes Process Chaos.
↗️ Eventually, Knowledge Loss shows up when your key people move on.
By the time you feel the pain at Level 5, the seeds were planted years earlier, often at Level 1.
That is why it is so important to stop and honestly ask: “Where on this scale are we today?”
It is not about blame. It is about clarity.
You might be wondering: where does Copilot fit into all of this?
Here is the short answer: Copilot does not sit outside the Chaos Scale.
It sits on top of it.
If you are operating at Level 3, 4, or 5:
↗️ Copilot can surface three versions of the same report.
↗️ It can summarize conflicting information from different teams.
↗️ It can answer questions using outdated or incomplete files.
AI is powerful, but it depends entirely on your underlying information structure.
If the structure is chaotic, AI will amplify that chaos.
Clean input leads to trustworthy output. That is true for people, and it is true for AI.
Before you invest heavily in a Copilot rollout, it is worth asking: How much File Chaos do we have? Are our processes documented? Where are we most vulnerable to Knowledge Loss?
Getting those answers first will make your AI investment go much further.
The Microsoft 365 Chaos Scale is not just a diagnostic. It is a conversation starter, and a roadmap.
Here is how you can use it with your team:
This is where Microsoft 365 training stops being about features, and starts being about how work actually happens.
If this framework is resonating with you, I would invite you to bring one question into your next leadership conversation:
“Where would we honestly place our organization on the Microsoft 365 Chaos Scale today?”
Not where you wish you were. Where you actually are.
From there, you can decide together whether your next investment should be cleaning up information, standardizing where files live, capturing critical knowledge before it walks out the door, or all three.
Technology should reduce friction, not create it.
The Chaos Scale is here to help you see where friction is hiding, so you can finally start removing it.
I teach all of the Microsoft 365 tools that help with exactly this, Teams, SharePoint, OneNote, OneDrive, Outlook, Planner, and more, in plain language, at a pace that works for real people with real jobs.
Learn more about MS365 Apps
⬅️ Need to find out more about what you have included in your Microsoft 365 Apps? Check out our blog so you can understand all the hidden apps and how they can help you.