I Didn't Start in AI

I started by solving operational problems.

Across more than a decade in product and digital transformation, I kept running into the same pattern: teams weren't struggling because they lacked technology. They were struggling because their processes were complicated, fragmented, and hard to actually use. AI became the tool that finally let me fix that properly — not because it was new, but because it let me redesign how people interact with systems instead of just patching around them.

While I was helping organisations transform digitally, I noticed the same gap showing up in people, not just processes: most of us don't have a reliable way to actually understand ourselves — our patterns, our blind spots, what we're actually working toward.

At 37, after years of imperfect journaling — some of it consistent, most of it not, mostly written on solo trips when I finally had the quiet to sit with a question — I found something I didn't expect looking back at every choice I'd made: no regrets, and a much clearer sense of what actually makes me happy.

That process is what BECOME is built from. Not theory — lived truth. Every design decision I make there teaches me something I bring straight back into consulting work: what makes people trust an AI, what makes them abandon it, what "helpful" actually feels like versus what it looks like on a slide.

Outside of technology, you'll usually find me training Muay Thai, running, or travelling.

None of that is separate from the work. Muay Thai in particular has hammered in the same lesson I try to apply to every product I build: progress comes from consistency, not from perfection. You don't get better by getting one session exactly right. You get better by showing up correctly, repeatedly, and paying attention to what breaks down when you're tired.