My Story

I started close to the machine, and never entirely left.

What follows isn't a CV. It's the sequence of rooms I've worked in and what each one taught me — usually the hard way, and usually about people rather than technology.

My first years were spent writing and supporting systems that other people depended on at three in the morning. That period set a habit I still keep: before believing a report, I try to find the thing underneath it.

Over thirty years the scope changed — more countries, larger portfolios, higher stakes — but the recurring failure mode did not. Programs rarely fail because the technology was wrong. They fail because ownership was ambiguous, complexity was underestimated, or the organisation was never asked whether it could absorb the change.

I still describe myself as a student. The subjects move quickly and the honest position is that a good part of what I know will need revising. Writing here is how I do that revising in public.

Selected stages

A journey, not a job history.

  1. Stage 01

    Engineering

    Close to the machine — writing, breaking and supporting systems. Where I learned that most outages are explained by something ordinary.

  2. Stage 02

    Technology leadership

    First responsibility for other people's work: estimates, standards, and the discovery that clarity is a leadership deliverable.

  3. Stage 03

    Global delivery

    Programs spanning geographies and vendors. Delivery became as much about handovers and language as about engineering.

  4. Stage 04

    Digital transformation

    Modernisation at scale — migrations, platforms, operating models, and the organisational absorption that decides the outcome.

  5. Stage 05

    Executive technology leadership

    Portfolio-level choices: what to fund, what to stop, and how to keep a multi-year agenda intact through change.

  6. Stage 06

    CDO perspective

    Sitting where technology, operations and the business case meet — and translating between them without losing precision.