Over 20 years,three countries,one idea.

I started in testing when testing was still something done at the end, by a separate team, to work that had already been declared finished. It was obvious even then that most of what we found wasn't a testing failure. It was a decision made weeks earlier by someone who never heard about the consequence.

That observation has shaped everything since. Across three countries and companies from small teams to large enterprises, the pattern held: the expensive problems were structural, and they were almost always visible earlier than anyone acted on them.

I help software teams find what's genuinely slowing their delivery, fix the two or three things that matter most, and build the capability to keep doing it without me. I work with teams of one to a hundred — small enough that a single engagement can change how the whole organisation ships.

I'm not interested in producing an audit that gets read once and filed. If your team isn't better at this after I leave, the engagement failed, regardless of what was delivered along the way.

I work alongside people rather than presenting at them. That means pairing, reviewing, and running real cycles on real work — not workshops on invented examples that get forgotten by the following sprint.

I'll also tell you when something isn't worth fixing, and when I'm not the right person for the problem. Turning down work I can't genuinely help with is cheaper for both of us than discovering it three months in.