More than two decades of engineering leadership, engaging teams and enabling modern, sustainable ways of working.
MY EXPERIENCE · INDIA → USA → AUSTRALIA · MYOB · IAG · ORACLE
Experience built at
The problem
Releases slip, and nobody can say exactly why.
Your pipeline is green, but nobody trusts it.
Quality is one person's job — and they're leaving.
You're shipping fast enough to hurt yourselves.
None of this is a testing problem. It's an engineering one.
What I do
The method
Five stages. Every engagement, every time.
Understanding what you actually build, and how the work really flows.
Two weeks of listening. I sit with your engineers, watch a release go out, and read the last three months of incidents. Not a survey — I want to see the work as it happens, not as the process document describes it.
What you get
A written map of your delivery flow, with the friction points marked.
Where the real constraints are — in the process, the tooling, the structure, or the habits.
Every team assumes their problem is tooling. It usually isn't. I test that assumption against evidence: cycle time, where defects originate, how many handovers a change survives, and where work sits waiting for a person.
What you get
A written findings report and a ranked list of what's costing you most.
Deciding what to fix first, and being honest about what to leave alone.
Most improvement plans fail because they try everything at once. We pick the two or three changes with the highest return and sequence the rest behind them. Some things on the list will never be worth fixing, and I will say so.
What you get
A sequenced roadmap with effort, impact and an owner against each item.
Making the change with your team, not to them.
This is the longest stage and the one that actually moves the numbers. I work alongside your engineers — pairing, reviewing, running the first few cycles with them — until the new way is simply the way things are done.
What you get
Working practice in place, run by your people rather than by me.
Making sure it holds after I leave.
The measure of the engagement is what is still true six months later. We agree what to track, who owns it, and what slipping looks like early enough to act on. Then I hand it over properly.
What you get
An agreed set of signals, owned internally, and a full handover session.
The method
Five stages. Every engagement, every time.
01
Understanding what you actually build, and how the work really flows.
Two weeks of listening. I sit with your engineers, watch a release go out, and read the last three months of incidents. Not a survey — I want to see the work as it happens, not as the process document describes it.
What you get
A written map of your delivery flow, with the friction points marked.
Who I help
Who I don't
The journey
Where the craft was learned.
Scale, and what it does to quality.
Leadership, and building teams that don't need you.
Coverage
Small, steady improvements beat big transformations. My job is to leave your team more capable than I found it — not more dependent on me.
