The question I'm most often asked is, "How did you get into this?" And the honest answer is that I fell into it, the way many of us did and do. I spent years in the thick of it, in IT, OT, and the messy space where they overlap. I've been the one piecing together what happened in a retrospective, the architect trying to build something that wouldn't break. That experience is the foundation of everything I do now.

Over time, I started to notice something. The technical problems were rarely the hardest part. The real friction, the real bottlenecks, came from us. From how we react under pressure, how we communicate (or fail to) when things go wrong, and how fear can shut down the very curiosity we need to solve problems.

That's where my approach today comes from. It’s not just about the technical bits. It’s about the humans in the system. I work with people and teams to build real, usable resilience. For me, that means creating spaces where it's safe to be curious, to experiment, and yes, to fail. My thinking is quietly shaped by two very different sources: the Montessori idea that we learn best when we have ownership and are genuinely interested, and the work of Virginia Satir, who understood that how people behave in a family system is exactly how they behave in any other system under pressure, including a business during a security incident.

So, whether I'm designing a hands-on exercise, talking through a problem one-on-one, or helping a team untangle a tricky incident, that's the lens I use. I bring my technical experience so at least you don't have to repeat my mistakes. And I bring a focus on the human dynamics, so you can navigate the pressure without losing your energy or your grip.

This isn't about me delivering a product. It's about working together to figure out what you actually need and finding a way forward that sticks. If that sounds useful, I'd be glad to talk.