Case study · Large-scale production

I am not a
landscaping expert.

I was still the one responsible for irrigation, soil, and several hundred thousand flowers being alive and upright on a publicly announced opening date. Al Ain Flower Festival. This is the case study about doing the thing you have never done before.

Fixed
Public opening date
10+
Vendors & contractors
Multi
Zone site
3
Projects, back to back
01

The honest starting position

A flower festival needs irrigation design, soil and drainage, horticultural timing, landscaping crews, structural installation, and a site that survives thousands of visitors walking through it every day for weeks.

I had done exactly none of that before.

I have built exhibitions, galas, festivals and government programmes. I had never once been responsible for keeping several hundred thousand living things alive on a schedule.

Nobody was going to move the opening date because the producer had not done flowers before.

So the real question was never "do I know landscaping." It was: how fast can I learn enough to make good decisions, and how do I make sure the people who do know are heard?

02

What I actually did instead of pretending

Said it out loud, early

Told the horticulture and irrigation contractors directly that this was not my domain. Specialists tell you far more when they are not busy managing your ego.

Learned the failure modes, not the craft

I did not need to design an irrigation system. I needed to know what kills one, how long it takes, and what the warning looks like a week early.

Put biology on the run sheet

Plants do not care about your build schedule. Growth and delivery windows became fixed constraints in the plan, the same as a stage load-in.

Made the experts the authority

On their call, they decided and I cleared the path. On delivery, budget and the date, I decided. Everyone knew which was which.

Rehearsed the failure

What happens if a shipment lands late, a zone floods, or a section dies in week two. Answers agreed before they were needed, not during.

Owned the boring half

Municipality compliance, permits, crowd flow, entry and exit, visitor experience across multiple zones. That part is squarely my domain and it never slipped.

03

The transferable bit

Every senior operations job is eventually this. A category you have not run before, a date that will not move, and a team of specialists who know more than you about their piece.

The skill being tested is not domain knowledge. It is whether you can be the person who holds the whole thing together while being the least expert person in half the conversations in the room.

That takes a specific kind of confidence: enough to make the call, not so much that you make it over the person who actually knows.

Delivery capability and domain expertise are different skills. Most hiring confuses them.

It is also, unsurprisingly, why I ended up building AI systems for events. Same pattern: unfamiliar territory, real deadline, learn the failure modes fast, and respect the people and tools that know more than you.

04

How it ended

The festival opened on its announced date and ran its full season.

Then the client kept going with me: Al Ain Ramadan Event straight afterwards, and then Sneaker Con Doha, the first edition in Qatar and Alsayegh's first multi-year IP agreement there.

Three consecutive projects, in three different categories, in nine months. In freelance production, that is the review. Nobody rebooks you twice out of politeness.

05

What I will not claim

Said up front, so nobody has to ask
  • I am not a horticulturist, an agronomist or an irrigation engineer, and this page is not quietly suggesting otherwise. Specialists did the specialist work.
  • No visitor numbers, budget or revenue figures. Those belong to the client and the authority. I will not estimate someone else's numbers to make my page look better.
  • It was a team. The festival opened because a lot of people did their jobs well. My contribution was production and operations, not the flowers.
  • Nothing went perfectly. Things went wrong, as they do on every build. They were handled. A case study claiming a flawless project is a case study nobody believes.