Fourteen Years of Crossings — A Field Manual for Adaptive Leadership

When people ask me what fourteen years of displacement teaches you, they usually expect a sentimental answer about home. I have one of those answers — it is true — but it is not the most useful one. The more useful answer is operational. Displacement teaches you how to lead a team, a company, or a household under conditions you did not choose, with information you do not fully trust, in time horizons that keep collapsing on you. That is also, increasingly, what most leaders are being asked to do — whether or not they have crossed a border.

I will not repeat the eight stations here; they are mapped, station by station, elsewhere on this site. What I want to set out instead is the doctrine that emerged across them, in the form a colleague could actually use. Five principles. None of them are original. All of them are tested.

One. Run a 90-day operating horizon — always. Every station in the crossing had a different official duration: a six-month visa, a one-year contract, a residency programme, a tourist stamp that got extended. In practice the operating horizon was always the same: ninety days. What can you ship in ninety days that compounds if you stay and survives if you go? Modern leaders complain that the planning horizon has collapsed; what they mean is that they are being asked to plan in displacement conditions. The 90-day cadence is the only honest answer.

Two. Hold portable assets above embedded ones. In every station, I learned the hard way which assets travel and which do not. A relationship with a specific landlord does not travel. A reputation for shipping clean work on tight deadlines travels everywhere. A bespoke local stack does not travel. A documented operating method that any competent collaborator can pick up travels. Leaders building teams in this decade should ask, of every investment of time and money, the simple question: does this asset travel? If not, can it at least be replaced in under thirty days?

Three. Maintain two languages of work. Not literally — though in my case it is also literal — but operationally. The Cairo years taught me to speak humanitarian; the Dubai year taught me to speak commercial; the Washington years taught me to speak policy. None of those languages, alone, are sufficient. Leaders who can only operate in one register get trapped inside it. The deliberate cultivation of a second working idiom — usually one register down the stack from your primary one — is the single highest-leverage investment in optionality I know.

Four. Treat your network as infrastructure, not as serendipity. The crossings were survivable because, at each step, someone who had crossed before me — sometimes by a few weeks, sometimes by a few years — opened a door. That generosity was not random. It was the output of people who had decided, deliberately, to maintain their networks as infrastructure: structured, kept-warm, with explicit norms of reciprocity. Leaders who treat networks as a side effect of being interesting are quietly outcompeted by leaders who treat them as a deliverable.

Five. Write the post-mortem before the next station. The temptation, every time a station ended, was to leave it behind quickly and lean into the next one. The discipline — and I had to learn it — was to spend two weeks writing down, in plain language, what had actually happened: what had worked, what had broken, what I had refused to see at the time. Those documents are the closest thing I have to a real operating manual. Most leaders skip this step under the cover of being too busy for it. They are not too busy. They are protecting themselves from the discomfort of looking at the previous chapter clearly.

I now sit in the eighth station — the return to Damascus, ostensibly the end of the crossing — and I find myself running, daily, the same doctrine I developed for the second station in Cairo when I was twenty-six and improvising. The doctrine has aged well. It will outlive the displacement that produced it.

If there is a single argument here, it is this: resilience is not a personality trait. It is an engineering discipline. It can be taught, documented, transferred, and audited. The most important work in front of any institution this decade is to take that engineering seriously — before the next station, whichever shape it arrives in, asks the question for you.