I hear culture talked about as if it is something written on a wall, captured in a values statement, or mentioned during onboarding. That is the easy version. The harder version is what happens on a normal Tuesday when something is broken, unclear, duplicated, delayed, or ignored.

That is where culture shows up.

Not in the big presentation. Not in the annual planning day. In the small moments where someone decides whether to leave the problem sitting there or do something useful about it.

The warning sign is hesitation

One of the quietest culture problems in any business is when good people start waiting for permission to care.

They see a clumsy process, notice a client communication could be clearer, or hear a decision drift past without an owner, and tell themselves it probably belongs to someone more senior.

None of that looks dramatic. Everyone looks polite, busy, and professional.

But the business is paying a tax every time that happens.

The work gets slower. The standards get softer. Small issues become normal. People learn that caring too much creates extra work, so they keep their heads down. That is how ordinary cultures become fragile cultures.

Ownership has to be visible

If I want a team to lift its standard, I cannot just tell people to take responsibility. I have to make it practical.

That means making it clear that improvement is not reserved for managers. If a client onboarding checklist in SharePoint is out of date, the useful response is not to complain about it in the background. Fix it, or at least raise it clearly in the right Teams channel with enough context for someone to act.

If a meeting ends with vague actions, do not let them vanish into the air. Use Copilot in Teams to summarise the discussion, check the actions, and then make sure the next steps land somewhere visible, such as Planner or a shared work tracker.

That is not bureaucracy. That is housekeeping.

The point is not that every person can change every decision. The point is that every person can make the problem clearer, remove friction, and stop the next person tripping over the same thing.

Quiet leadership matters

The best ownership I see is often quiet. It is not the person dominating the room. It is the person who notices a gap and calmly closes it.

They ask the extra question. They document the missing step. They follow up after the meeting. They update the shared note. They make the next handover cleaner than the last one.

In an MSP or any service business, that behaviour compounds quickly. Clients feel it when internal ownership is strong. Tickets are cleaner. Handover notes make sense. Recurring issues get spotted earlier. The client does not have to re-explain the same problem three times.

That is culture in operational form.

I am not interested in a team where people only do what is printed beside their name. That might keep the lights on, but it will not build something excellent.

The better standard is this: if you are close enough to see the issue, you are close enough to help move it forward.

That does not mean being reckless or ignoring roles, approvals, or security boundaries. It means acting like the quality of the whole business matters, not just your own narrow lane.

Shared ownership is not a slogan. It is a habit. It is built in the everyday choices people make when there is no applause attached.

And if you want to know the real strength of your culture, do not just listen to what people say in the meeting. Watch what they clean up afterwards.

I can usually tell when a team is disconnected from the work it produces.

Not because the work is terrible. Often it looks fine from the outside. The newsletter goes out. The video gets posted. The webinar happens. The support article lands in SharePoint. The client update gets sent from Outlook.

But inside the business, nobody is really paying attention.

The team does not watch the video. They do not read the newsletter. They do not know what was promised in the webinar. They do not see the questions clients are asking after the content goes live.

That is where the problem starts.

Your own team is the first audience

I think many businesses make a mistake here. They treat content, education, communication and client resources as something created by one person or one small group. Everyone else is expected to be “too busy” to engage with it.

I see it differently.

If you work in the business, you need to understand what the business is saying.

That does not mean everyone has to become a marketer. It does not mean every technician needs to write articles. It does not mean every account manager needs to appear on camera.

It means the people who serve the client should know the message the client is hearing.

If a Microsoft 365 security update goes out to clients, the service desk should know about it before the client rings. If a Copilot readiness article is published, the account manager should know the point of view before the next review meeting. If a training video explains why governance matters, the project team should have watched it before they start implementation work.

That is not bureaucracy. That is alignment.

Consumption creates better feedback

The other thing people miss is that internal consumption makes the work better.

A team that reads, watches and listens can challenge weak ideas before clients see them. They can say, “That example will confuse people.” They can say, “Clients are already asking about this.” They can say, “We need a simpler explanation for the business owner.”

That feedback is gold.

This is where Microsoft 365 can really help, but only if it is used deliberately. I like the idea of having a dedicated Teams channel where published content, draft ideas and client questions are visible. Drop the newsletter link in there. Pin the SharePoint page. Use Copilot in Teams to summarise the discussion after people have commented. Capture the useful follow-up items in Planner rather than letting them disappear into chat history.

The tool is not the culture. But the tool can make the culture easier to practise.

The important part is that everyone understands the loop.

Create something. Share it internally. Let the team react. Improve the next version. Listen to what clients say. Bring that back to the team. Repeat.

That loop builds judgement. It also builds ownership.

Make it expected, not optional

I do not have much time for the idea that “mandatory” automatically means heavy-handed.

Some things should be expected.

If the business publishes advice to clients, the team should know what that advice is. If the business takes a position on AI, security, productivity or service delivery, the team should be familiar with that position. If clients are being educated, the people supporting those clients should not be the last to know.

The standard is simple: if we produce it, we pay attention to it.

That does not need to become a long meeting or a corporate ritual. It can be a short weekly review. It can be a Teams post with three questions. It can be a Copilot-generated summary of what went out, what clients asked, and what the team noticed.

But it does need to happen.

Because care is visible. Not in a fluffy motivational sense, but in the final product. You can feel when a team has thought about the work. You can feel when people have challenged it, improved it, and connected it back to the client.

You can also feel when it was pushed out by someone working alone while everyone else walked past it.

If your own people are detached from what you create, do not be surprised when the outside world is detached as well.

The work has to matter internally first.

That is where better culture starts. That is where better feedback starts. And that is where better client outcomes start.