The hardest leadership lesson I ever learned was this: stillness is not retreat—it is command.

I learned it twice.

The first time was during an airline system cutover in Seychelles, where we had announced our go-live date to the world, and there was no path back.

The second was years later, when I stood before the President and promised—on my daughter’s birthday, September 15—that the country’s new travel authorization system would launch that day, no matter what.

Even the Minister paused afterward and asked: “Are you sure you want to tie yourself to a date like that?” I was. Because choosing a date you cannot break is how you make failure intolerable—and how you summon the same discipline, rhythm, and stillness all over again.

I. Stillness is not Softness: It is Discipline

When I was younger, I believed complexity yielded to speed: push harder, gather more, think faster. It took years to learn the quieter truth: a mind running hot sees nothing clearly. Clarity comes when the inside of you is still, even while the world shakes.

Stillness isn’t softness. It’s discipline.

The hardest problems—the ones threaded through systems, timing, people, and pride—don’t break under force. They open under attention. And attention only comes when the noise inside you goes silent.

II. The Nature of the Fight

An airline system cutover is the moment an airline switches the system it runs on to a new one—while aircraft are flying, passengers are checking in—and nothing can stop.

“The fundamental reason it isn’t easy,” Chris Vukelich once said, “is that a cutover is the business equivalent of removing the brain of a human being while they’re lying on the table and still talking to you.”

I didn’t understand that line until I lived it. Every day, something went wrong—not catastrophic failures, but the quiet ones that only surface during a cutover:

- a handoff with a missing piece

- a configuration that worked in theory but not in the wild

- a data file that arrived late

- a timing slip that knocked a later task off balance.

Our weekly reports became a map of the fight: stretches of green where momentum held, yellow zones where friction had begun to rise, and a few red knots pulsing like warning lights.

And there were two such maps:

- one from the vendor, charting the system’s technical heartbeat

- one from the project I led, showing where people, process, and readiness actually stood.

I sat astride both, watching where they agreed and where their shadows diverged. Between them lay the truth of where the next fight had to be.

A plan perfect at sunrise was rubble by noon, not because it was wrong, but because a new truth had arrived.

And I wasn’t alone in the fight. Etihad sent battle-tested cutover veterans—people who had walked through their own fires and carried the quiet calm that only experience forges. In the long nights, their steadiness kept the entire operation on its rails.

Time itself was an adversary.

In Seychelles, urgency has to be felt to be believed. But in a cutover, what happens in week one echoes into week 32.

I had to push the horizon.

III. Pushing the Horizon

At first, every problem felt like a train already in the station—headlight in my face, horn shaking the rails. But as the weeks sharpened me, and as my counterpart Ashwin guided me through the craft, something shifted.

I learned to move the horizon out, not by ignoring problems, but by detecting them while they were still little more than vibrations on the track. Sometimes I had to raise the temperature—intentionally—so a risk eight months away felt like a Monday-morning problem.

In Seychelles, people move when they feel the ground shift beneath them. So I became the early-warning system: sounding the alarm sooner, clearer, sharper. Not to frighten—to make the invisible visible. It wasn’t theatrics. It was translation: aligning our natural rhythm with the unforgiving cadence of the project.

[Part 2 of this essay will be published on December 10, when Alan will delve deeper into the disciplines that the project demanded—and the outcome.]