I have sat in plenty of rooms where someone suggests lowering the bar to get more people involved. Make the rules softer. Reduce the expectations. Stop being so particular about process, documentation, security, handover, client communication, whatever the current friction point happens to be.

It always sounds reasonable at first.

But there is a pattern I have seen too many times to ignore: when a room has no clear standards, it does not attract the best people. It attracts the people who prefer ambiguity because ambiguity lets them avoid accountability.

That is a hard lesson for many MSPs to learn.

The bar tells people what matters

Standards are not about making life difficult. They are about making expectations visible.

If your team has a standard for documenting client environments in SharePoint, then everyone knows where the source of truth lives. If meeting notes and actions are captured in Teams or Loop, people know what was agreed and who owns it. If Copilot is being used to summarise client discussions, draft follow-up emails in Outlook, or prepare service review notes in Word, there should be a clear expectation about what information is appropriate to include and what must stay out.

Without that, everyone invents their own version of good enough.

That is when things drift.

One person writes detailed notes. Another leaves three vague lines in a ticket. One engineer checks conditional access changes against a peer review process. Another makes the change directly because “the client needed it quickly.” One account manager records agreed actions. Another relies on memory and an inbox search three weeks later.

The issue is not that people are bad. The issue is that the organisation has allowed different definitions of acceptable work to exist at the same time.

That never scales.

Lowering standards rarely solves the real problem

When standards feel hard to meet, the answer is not always to lower them. Sometimes the answer is to make them easier to follow.

That is where Microsoft 365 and Copilot can help, but only if the business already knows what good looks like.

For example, if your MSP expects every client meeting to end with clear actions, use Copilot in Teams to help summarise the discussion, then review and clean it up before sending it from Outlook. If your team struggles to keep project notes consistent, create a simple Word or Loop template that defines the structure. If client documentation is scattered, fix the SharePoint libraries and permissions before telling people to “just ask Copilot.”

Copilot does not remove the need for standards. It exposes where they are missing.

If your process is messy, Copilot will help you move faster through the mess. If your permissions are sloppy, Copilot will show people more of what they already had access to. If your team has never agreed what a good client handover looks like, Copilot will not magically create that discipline for you.

AI makes good standards more valuable, not less.

A serious business needs serious expectations

I am not talking about perfection. No MSP runs perfectly. Every team has busy days, awkward clients, rushed escalations, incomplete tickets, and moments where someone has to make a judgement call.

But there is a difference between flexibility and having no standard at all.

A good standard says, “This is how we do things here.” It gives strong people confidence because they know the work will not be undermined by shortcuts. It gives newer people a path to improve. It gives leaders something fair to manage against.

Most importantly, it protects the business from becoming a place where the lowest acceptable behaviour becomes normal.

If you want a better team, better clients, and better outcomes from tools like Copilot, start by being clear about the room you are building.

The people worth having will not be scared away by standards.

They will be attracted by them.