Approach

📌 Staff notice 💭 Inner monologue

Service transition is a two-way seam

The point where a project becomes a live service is where customer experience is usually won or lost. I treat it as a loop rather than a gate. Projects need to land cleanly into support, and what live operations learns needs to reach delivery just as reliably. With Professional Services leadership I formalised how customer requests are routed between support and projects, so customers hear one consistent answer about who will do the work.

Data first, then automation

I get the data somewhere trustworthy before automating anything on top of it. Automating a process nobody can measure only makes the confusion faster. My proactive problem management work started with standard health checks and consistent classifications, and only then moved the repeatable checks into automation.

People stay accountable for AI

I use AI to take repetitive load off engineers and to surface what needs attention, with a person accountable for every decision it informs. In the request triage workflow I built, the AI summarises and suggests, and the leads decide. I would rather give people safe, practical tools that are easier to use than the alternatives than write rules nobody follows.

How I lead

I lead by empowering teams to own their domains, removing blockers and partnering with customers to listen and improve their experience. I pair technical authority with psychological safety: people learn faster and innovate more when they are not afraid to be wrong, and stability through a complex transformation depends on it. That starts with genuine relationships, because operations runs on trust. I stay hands-on in third-line escalations and major incidents where it matters most. In my experience, people cope better with a difficult decision than an unclear one, so I try to make decisions clear early.