When 20 Minutes Turns into 60

Recently, my family and I went on a Caribbean cruise. We were travelling from one of Europe’s northernmost cities, so we built plenty of breathing room into the journey. A flight or two might be cancelled, and we still wanted to make it to the ship.

Apart from our first flight, everything ran on time. That gave us the chance to explore Miami and fall for the colours and atmosphere of South Beach.

We had booked an 11:00 a.m. boarding slot. That would give us time to look around the ship before she cast off. The cruise line’s ticket said: “Passengers must arrive at the terminal within one hour of their assigned arrival time. Arriving later may result in denied boarding.”

The night before, I checked the journey from our hotel to the terminal on my phone. Twenty minutes. A nice, reassuring little number.

In the morning, the whole family made it to breakfast as planned. Then we soaked up the last of Miami at News Cafe and took a taxi towards the port. We could see it nearby, with only a narrow strip of water between us and the ships. Close enough to wave at. Not close enough to reach.

Ten minutes into the ride, traffic came to a complete standstill.

We were used to traffic in Panama City, but this was something else. The taxi had joined a very large, very stationary parade. Cars stayed in their lanes. Nobody used the shoulder or tried to squeeze into the 3 mm gap between our taxi and the car ahead. The queue simply refused to move, or rather it crawled forward at the speed of a thoughtful tortoise.

Then we learned why: five ships were at the cruise terminal, two of them carrying more than 6,000 passengers.

The minutes ticked by. The map showed red all the way to the terminal. First, our estimated arrival time was 12:10, then 12:20. Our ETA was drifting away like a boat without a mooring line.

In my mind, I was already working through the scenario: no boarding, no hotel booked, new flights and all the other costs. My blood pressure was climbing despite the medication.

We finally reached the terminal at 12:35.

Fortunately, the cruise line’s warning seemed to be there mainly to encourage passengers to arrive at their assigned time and prevent congestion at the terminal. Our long-awaited cruise set sail with us on board.

I had made a classic mistake: I treated a general estimate as reliable planning data without accounting for the conditions we would actually face. This time, the consequence was only a brief spell of stress and perhaps a few extra grey hairs.

Now imagine you are responsible for planning a maintenance shutdown. You sequence the work, define the critical path and issue the schedule. It looks good on paper, and the shutdown begins.

Then it turns out that the duration of the first critical-path task, or one of its steps is based on an assumption rather than verified execution data. The first domino falls, and the rest of the schedule starts wobbling. That perfect plan can become a very expensive paperweight before the shutdown is properly underway.

During the post-mortem, the team looks for ways to improve. Someone suggests using verified actual task durations adjusted to reflect the target conditions rather than starting again with guesses.

Everyone agrees.

But unless actuals are captured, retained and made available for the next planning cycle, the same conversation will happen again.

Sights: No guesswork. Verified data to support better decisions.