Druid Asia. The rescue, the expansion, and the close.
Programme recovery, legal exposure, commercial containment, client confidence, talent reset, regional expansion, and strategic closure interventions.
After FI Group acquired Druid, I moved from the United States to Singapore. The biggest project Druid had at the time was failing: the SAP engineering implementation at Singapore Airlines, subcontracted to IBM. It was over budget and over time. The contract's profitability had been compromised by my predecessor's accounting.
I took the project on. The engineering implementation would never be profitable — but the work was completed, the client kept, and the worst exposure contained.
Then the expansion. I opened SAP consulting partnerships in China and bid for SAP aircraft maintenance contracts with China Northern, China Southern, and a Chinese aero engine manufacturer. I built project teams across Malaysia, Indonesia, Thailand, and Singapore. I cleared the deadwood out of the business. Within two years Druid Asia was running profitable growth.
A new Group CEO was appointed. The Board agreed with his recommendation that every Druid overseas operation should be closed — America, Europe, Asia — and the company pivoted to focus on Indian outsourcing.
Having turned the business around, rescued the Singapore project, and expanded into broader Asia, I was told to close the Asia business I'd built.
Abu Dhabi Aircraft Technologies. The Oracle CMRO build.
Political alignment, executive governance, vendor selection, leadership coalition, scope containment, critical-path delivery, and regulatory-risk interventions.
A hot day in Chiang Mai. Songkran had passed and the rain clouds were gathering. The phone rang.
A senior consultant I didn't know: "You have been recommended to me. We are working for ADAT."
Four days later I was on a flight to Abu Dhabi.
Abu Dhabi Aircraft Technologies — aviation maintenance, repair, and overhaul for multiple global fleets. A highly regulated, critical environment. The current systems were moribund. A new platform was essential. Both Oracle and SAP had nominated their solutions; each had brought an implementation partner.
Oracle's solution had limited history in aviation. Its local implementation partner was strong. SAP's solution was highly regarded. Its implementation partner was weak.
My judgement: the local implementation partner would carry execution. A strong partner could shape an immature product through delivery. A weak partner could not save a proven one.
I recommended Oracle.
I was asked to lead the implementation. I took the roles of CIO and Project Director.
The technical challenge was only part of the work. The programme also required constant political alignment between group leadership, local management, vendors, internal teams, and owners whose interests were not always moving in the same direction.
Then I made the calls. Within weeks, leading experts in aviation MRO systems, business design, and large-scale digital transformation had flown in from four continents to help me lead. They worked alongside top-class internal people. 176 people on the programme at peak.
$40m project. The owners had imposed a 24-month timeline. A timeline no peer programme had ever achieved.
Twenty-four months — and go live was achieved: Oracle Complex MRO, a new digital document management system, a new data centre, and a business-wide organisational transformation.
Was history made that day?