Your Real Culture Shows Up When Everything Goes Down
Culture is easy to talk about when the business is having a good week. Friday drinks, a team lunch, and a few carefully chosen values on the wall can all suggest that people enjoy working together. The more revealing moment is when a client’s systems go down and everyone is looking for answers. That is when you discover whether people feel safe enough to tell you what is actually happening. Not the slightly tidier version they hope to present once they have fixed it, but the uncomfortable truth while the problem is still unfolding.
Nick Clift
10/8/20262 min read
Culture is easy to talk about when the business is having a good week. Friday drinks, a team lunch, and a few carefully chosen values on the wall can all suggest that people enjoy working together. The more revealing moment is when a client’s systems go down and everyone is looking for answers.
That is when you discover whether people feel safe enough to tell you what is actually happening. Not the slightly tidier version they hope to present once they have fixed it, but the uncomfortable truth while the problem is still unfolding.
I remember an extreme incident where an entire client site dropped offline. The site engineer did not panic, make excuses, or try to hide it. He raised his hand immediately: “We’ve got a major problem here. This server is down… actually, they’re all down.”
Not the update anyone wanted. But it was the update we needed, and it meant we could get on with responding rather than spend time trying to establish what had happened.
Because the team operated with transparency, nobody started pointing fingers. Senior engineers jumped in, our vendors rallied alongside us, and we ran a daily standing huddle with the client and technical leads until the issue was resolved. The attention stayed on the problem and the customer’s business.
We turned an operational disaster into one of the strongest client relationship wins we ever had. Not because the outage somehow stopped mattering, but because of how we worked together through it.
The client could see that we were engaged, communicating, and bringing the right people into the conversation. They did not have to chase a succession of disconnected updates or wonder whether anyone was taking responsibility. The daily huddle gave everyone a shared place to understand the situation and discuss what needed to happen next.
Looking back, the engineer’s willingness to speak up was central to that response. If he had felt the need to protect himself first, we could have lost valuable time while he tried to solve everything alone.
That is why psychological safety matters in an MSP. The phrase can sound like something reserved for an HR workshop, but the practical question is straightforward: can someone in your service team say, “I need help,” before the situation gets worse?
Safety does not mean that mistakes go unexamined or responsibility disappears. It means people can report a problem honestly without treating the admission itself as a career hazard. There is time to understand what went wrong, but the first priority is helping the customer.
This is how I connect culture to operational maturity in my role as Governor of Growth at Morphability. A service team that asks for help early can bring more experience to the problem sooner. A team that feels compelled to work in isolation makes collaboration harder precisely when it is needed most.
Leaders influence that through ordinary conversations, not just major incidents. How do we respond when someone admits uncertainty, flags a mistake, or challenges an assumption? People notice whether we become curious or immediately start looking for someone to blame.
Friday drinks are lovely, of course. But they cannot compensate for a Monday morning where nobody feels safe enough to tell you the truth.
Your real culture is what happens between “we have a major problem” and “let’s work through it together.” When did you last make it clear to your team that asking for help early is part of doing the job well?