May Mun

A customer’s cloud had been offline for weeks. The fix was a long snapshot consolidation, and May Mun accidentally cancelled the script. Everyone started over.

Her leader didn’t ask who. He asked why. That question has shaped every role she’s taken since.

Data centres were her second office. She built and operated hosted and hybrid cloud, backup and DR across vCloud Director, vSphere, NSX, vROps, CommVault, Veeam, Zerto, Nutanix, Cisco UCS, Dell EMC and NetApp. Then she moved into security, audit and governance, working with Tenable, BeyondTrust and Microsoft Sentinel, building her company’s first ISMS, and driving the organisation towards Microsoft Azure Expert MSP status.

Today, she helps critical infrastructure execs decide what to fix first. She pressure-tests controls and quantifies risk where “down” becomes a public issue.

That journey gave her range. She can get into the weeds with engineers, challenge a technology vendor or an auditor, understand what a control is trying to achieve, and then step back and ask whether it makes sense for the business.

Her principle: assess technology the way it is actually adopted and operated, not the way it was designed on paper. Business context sets the priorities; technology sets the options. The interesting part is the space in between: what the capability really does, what users and operators actually experience, and what the business can realistically absorb.

AI? It’s cloud with a new badge and some new ways to fail. Humans and machines are now making decisions side by side, and she’s watching where the old lessons hold and where they don’t. When an agent breaks something, she asks the question her leader once asked her: why?

Off duty, she plans travel around dinner reservations and still ends up capacity-planning at the table. Unlimited risk appetite; limited storage capacity.