I have spent my career around data in complex organisations, usually at the point where an ambition meets the reality of the systems and people underneath it. What I noticed, again and again, was that the technical answer was rarely the missing piece. What was missing was agreement, and someone willing to say plainly what the work would involve.
So the way I work is fairly simple. I start with the objective you are accountable for, not the technology in front of you. I spend time with the people who live with the data every day, because they usually know where the problems are. Then I set out the sequence of work, the trade-offs and the parts you should keep in-house, and I tell you if something is not worth doing yet.
I believe consultancy should leave an organisation more capable, not more dependent. That belief shapes how we staff engagements, how we document decisions and how we hand things over. It also means I would rather recommend a smaller piece of work that succeeds than a larger one that stalls.
Enterprise clients tend to work with me directly because they want a senior view they can challenge, in language their board and their engineers both understand. For me, success isn't simply delivering the work. It's seeing it being used and making a difference after we've gone.".