Engineer by training, coach by calling

I founded Agile Conductor to close the gap between what agile promises and what it usually delivers. I've seen too many teams running ceremonies nobody believes in, chasing metrics that measure the wrong thing, and carrying the scar tissue of a twelve-month "transformation" that changed the org chart and nothing else.

My background is engineering, which shapes how I work: choosing a way of working is an engineering decision, not a philosophical one. The right questions are about cadence, complexity, and risk — not about which framework is fashionable this year.

So I work in fixed, honest engagements: a clear problem, a clear price, a clear end. The goal is never to embed myself for a year. It's to fix the one thing, make it stick, and get out of your way. Pragmatic agile. No theatre.