Designing for the Domino Effect

# Why a Single ETA Change Breaks Maritime Logistics

MARITIME UX · 4 MIN READ

In 30 seconds

No feature exists in a vacuum.

A 12-hour ETA slip sets off a chain reaction across ports, barges, trucks, and charterers—because shipping lacks a single source of truth.


01 · THE LOGISTICAL BOMB

One prudent course change at sea breaks a week of tightly synchronised port-call logistics.


02 · THE REAL CULPRIT

Not the storm—fragmented emails, phone calls, and WhatsApp messages with conflicting ETAs.


03 · THE DESIGN SOLUTION

A single shared source of truth that broadcasts both the new ETA and the reason behind it.

There is nothing an Englishman enjoys more than talking about the weather. We have, in fact, developed an entire language to describe the infinite nuances of a grey, drizzly sky. It’s a national obsession, a source of endless, harmless small talk.

But what happens when the weather stops being small talk? What happens when a sudden, unforecasted change in the weather has the power to light the fuse on a multi-million-pound logistical bomb?

It starts, as it so often does, with the weather, a storm is brewing in the South China Sea, a menacing grey monster that wasn't flagged on the forecast. On the bridge of a 200,000-tonne vessel, the Master does what any sane and responsible captain would do. He alters course. And with that single, prudent decision for the safety of his crew and vessel, he unknowingly lights the fuse on a logistical bomb a thousand miles away.

That bomb explodes on the desk of a shoreside Vessel Operator. For the last week, she has been conducting a symphony of logistics to ensure a perfect, on-time port call. The berth is booked, the pilot is scheduled, the bunker barge is on standby, and a fleet of trucks is ready to move the cargo. Her entire week's work is a meticulously planned, tightly synchronised machine.

And then the bomb goes off. A single, context-free line in an email informs her that the vessel's ETA has slipped by 12 hours. It's a small change. And it has just set fire to her entire plan.

01 · THE CHAIN REACTION

Suddenly, the dominoes begin to fall, fast.

01 · PORT AGENT

They’ve lost their berthing window to another ship. The next available slot is in two days.

02 · BUNKER SUPPLIER

The bunker barge has been re-tasked and won’t be available for another 36 hours.

03 · TRUCKING FLEET

The trucking company has to be cancelled, likely incurring a costly penalty fee.

04 · CHARTERER

On the phone demanding to know why cargo is late and which charter party clauses were breached.

Now, you might think the problem here is the storm. It isn't. The problem is that the entire global shipping industry is run on a creaking, fragmented, and fundamentally untrustworthy information system. The "official" ETA in the public domain is often a work of fiction, a placeholder padded for safety. Real updates are communicated through a chaotic blizzard of emails, phone calls, and WhatsApp messages, with no single source of truth. The result is that when a genuine change happens, nobody is prepared, and everyone is working with different information.

The job of a good designer, then, is not to build another box for a Master to type an ETA into. The job is to think holistically. It's to understand that this one piece of data is the linchpin for a dozen other critical decisions made by a dozen other people.

Our approach is simple: create a single, shared source of truth that connects everyone in the chain. When the Master updates the ETA in a system we've designed, it doesn't just change a number. It simultaneously communicates the reason for the change ("Delay due to heavy weather for safety") to the Operator, the Port Agent, and the Charterer.

It transforms a crisis into a conversation. It turns reactive chaos into proactive, collaborative problem-solving.

Designing for the domino effect means understanding that no feature exists in a vacuum. It means looking beyond the immediate screen and seeing the entire, messy, interconnected system of people trying to do their jobs. It's the difference between building a small, elegant cog and engineering a machine that actually works.

CALL TO ACTION

What’s the most painful domino effect you’ve seen?

What's the most painful "domino effect" you've seen triggered by a single, simple change in your industry?