Supply chains fail. Key people leave. Rules change mid-crisis.
I build the systems that hold through all three.

Two kinds of evidence, kept separate.

Part of this record is direct crisis work: an organization under an existential shock, with me building the systems that kept it running. The rest is operational engineering in stable conditions. Both matter to a resilience engagement, but they prove different things, and presenting them as one would undermine everything else on this page.

You can't build a thirteen-week cash model under pressure if you have never built a model, or map supply chain dependencies in a week if you have never mapped a process. The right-hand column is the toolkit. The left-hand column shows it holding under pressure.

Which of these is true in your business this quarter?

Eight situations GCC business leaders are dealing with right now. Choose the one closest to yours to see the pattern underneath it, where the same problem has been solved before, and the module that builds the document to fix it.

Built for how GCC businesses actually work.

Most resilience material available to Gulf business leaders was written for North American or European conditions and lightly adapted. It misses what decides whether a GCC business gets through a disruption: concentrated shipping routes, expatriate workforce mobility, family ownership, and banking relationships that work differently from what those frameworks assume.

Most of this work happened where complexity and pressure meet.

Two things make an operational problem hard: how complicated the organization is, and how much pressure it is under while you fix it. Process consultants usually work in calm, contained settings. Crisis responders usually work in simple, urgent ones. Plotting the engagements in this record shows a concentration in the corner where both are true, which is where many GCC businesses are in 2026. Select any point.

Scores are my own assessment. Complexity reflects scope: the number of sites, departments, entities or stakeholder groups involved. Pressure reflects operating conditions at the time, from stable improvement work to active crisis with no option to pause.

Six industries. One method. Eight documents you keep.

The usual objection to cross-sector experience is that it doesn't transfer, and that a hospital result says nothing about a trading company. What changes between sectors is vocabulary, regulation and stakeholder politics. What stays the same is the question underneath: where is the exposure, where is the constraint, and how does it fail? The program applies the same five-step method to your business and produces eight documents you own. Hover over a sector to trace the path.

An operating theater is a work center with a changeover problem. A sterile processing department is a reprocessing line with a yield problem. A grant program is a high-volume transaction pipeline with an integrity problem. A GCC trading company facing a closed shipping lane is a supply chain with a single point of dependency. The vocabulary changes. The engineering stays the same.

Several of these removed the problem entirely.

Reducing a recurring failure by thirty percent gives you a better average. Removing it means the failure mode is gone, and the capacity spent managing it is released for good. That is the standard the program's deliverables are built to.

What stays behind when the advisor leaves.

The usual complaint about advisors is that nothing holds: the deck arrives, the advisor leaves, and within two quarters the organization drifts back. Every engagement below ended with a system someone else runs, whether a dashboard, a daily management routine, a deployed model or a trained team. The program works the same way. You finish with eight documents your own people maintain.

I have built and delivered training programs like this before.

The program is a training product, and training is a different skill from consulting. Plenty of capable advisors can't pass on what they know. Here are three settings and three very different audiences, with one structure underneath: defined modules, a real project, formal assessment, and a named person who carries the work forward afterward.

Three formats. The same eight documents.

All three formats cover the same eight modules and produce the same eight assessed deliverables. What changes is how much support and accountability you want while you build them.

Each of these is common. Together, they are rare.

A doctorate in industrial engineering. Big Four advisory experience. Years operating inside an institution rather than consulting to one. Native Arabic alongside professional English. None of these is rare on its own. Held by one person, they are the reason for the call.

Every figure on this page, with its source.

Each number used on this page appears below with what it measures and where it comes from. Where the record holds two versions of a figure, the lower, better-supported one is shown. Results from Navolon's GCC work will be added as they are published, starting with the founding cohort in 2027.