About

I help technology leaders make better decisions about architecture, engineering, and AI adoption by bringing clarity to the questions that matter most: what are you trying to achieve, what constraints are you working within, and how will you operate this once it’s built?

After twenty-five years working across financial services, defence, retail, and data platforms, I’ve learned what makes technology decisions succeed.

The hard part is understanding what you’re really trying to solve, facilitating honest conversations around constraints, and building architectures that your teams can actually maintain. Whether you’re evaluating Kubernetes versus serverless (to pick two examples) or any other architectural decision, technology choices shouldn’t exist in isolation from the business context and the people maintaining them.

This site exists because I think better when I write. The posts here span both my current work as a Field CTO and my earlier hands-on technical and product roles. You’ll find analysis of patterns I’m seeing across engagements, explorations of architectural trade-offs, and occasional deep dives into specific technologies when they’re relevant.

If you’re working through decisions about AI adoption, cloud migration, or platform modernisation, my role is to help you think through the implications of different approaches, drawing on practical experience across multiple sectors and technology stacks.

For more detail on my background, see my Interactive CV . You can also find me on LinkedIn or GitHub , or get in touch directly.