The Shared Departure

The story

We were due to leave port at five. By four-forty, most of the ship was already back — you could feel it, that particular hum of a vessel getting ready to move. Crew coiling lines, the gangway crew checking manifests, a low announcement reminding everyone that all-aboard was in twenty minutes.

At five, we hadn’t moved. Two names were still outstanding — a couple who’d taken the full-day excursion, stuck behind a delayed tour bus somewhere on the other side of the island. The captain didn’t sail without them. He couldn’t. Not because policy forbade it, but because there’s no such thing as a ninety-eight percent departure. A ship either leaves with everyone aboard, or it doesn’t leave.

So we waited. Two thousand passengers, fully returned, fully ready, held in place by two people who weren’t.

The Shared Departure is what I’ve come to call this: the moment an organization discovers that readiness isn’t additive. You can have every team, every system, every market but one fully prepared to move — and still be sitting at the dock, because forward motion belongs to the whole hull, not to the parts of it that finished early

The Announcement

There’s a specific kind of stillness on a ship that’s ready but not moving. Nothing is broken. Nothing is behind, except two names on a list. And yet every single person aboard — whether they arrived back at noon or at four-fifty-nine — is now equally delayed. The couple hurrying up the gangway at 5:12 doesn’t experience the wait differently than the retiree who’s been sipping a drink by the pool since one o’clock. The ship doesn’t do partial credit for punctuality.

That’s the part that struck me. On land, if you’re on time, you’re simply on time — the late person’s problem is their own. On a ship, lateness is contagious by design. It has to be. There’s only one hull, and it only goes one place at a time.

Why the Ship Doesn’t Leave in Pieces

Most organizational failures don’t look like this. Most of the time, the finance team’s readiness and the ops team’s readiness really are separable — one can go live Tuesday and the other Thursday, and nobody sinks. The Shared Departure names the narrower, more dangerous case: the moments when the structure genuinely is a single hull, whether anyone planned it that way or not.

A platform migration where every business unit must cut over together. A regulatory change that takes effect for the whole company at once, not team by team. A merger integration where the new org chart either takes effect everywhere on Monday or the confusion multiplies. In each of these, the organization has quietly become a ship — and the honest move is to admit it, rather than pretend the late department’s delay is a side issue.

The parts of an organization that finished early don’t get to leave early. That’s not a flaw in the system — for some systems, it’s the entire point of building them as one system.

Michel Paquin

The Silent Ninety-Five Percent

Here’s what’s easy to miss: the two thousand ready passengers made no noise. Nobody complained on the loudspeaker. There was no scoreboard showing “1,998 aboard, 2 remaining” scrolling through the lounge. The readiness of the overwhelming majority was invisible precisely because it worked — and invisibility is what allowed the two latecomers to become the entire story of the delay.

Inside organizations, this creates a strange, unfair optics problem. The nine teams that hit their deadline get zero credit in the retro, because the meeting is entirely occupied by the one team that didn’t. Readiness has no voice. Lateness has the only microphone.

Where This Shows Up at Work

• A company-wide system cutover waiting on one region’s data migration, while eleven other regions sit fully converted and idle.
• A product launch held for one legal sign-off, while marketing, sales enablement, and support are all staffed and standing by.
• A reorg’s effective date delayed because one division hasn’t finished its org-design paperwork, while the rest of the company has already mentally moved on.

In each case, the temptation is to resent the slow part publicly. The more useful question is quieter: was this ever a single-hull decision to begin with — and if so, did we build in enough margin for the ordinary reality that some part of any large system runs late?

Gangways Have Edges

None of this means infinite patience is the answer. The ship did wait — but not forever, and not silently. There was a published all-aboard time, a series of announcements, and eventually a real deadline after which the couple would have been left to catch up at the next port on their own arrangement. The grace period was generous, but it wasn’t unlimited, and everyone aboard knew where the edge was.

That’s the piece worth borrowing deliberately: build the margin, but name the edge. A cutover date with quiet, unlimited slippage teaches every team that lateness has no cost. A cutover date with zero margin turns one bad afternoon into a companywide crisis. The useful middle is a stated grace window and a real, communicated point after which the ship leaves — or the decision escalates — without the late part.

A deadline with no margin is fragile. A deadline with no edge isn’t a deadline — it’s a suggestion.

Michel Paquin

When This Doesn’t Apply

Not everything is a single hull, and treating it like one is its own mistake. Plenty of organizational work is genuinely divisible — team by team, market by market, phase by phase — and forcing artificial simultaneity onto separable work just adds unnecessary risk and delay for everyone. Before invoking the Shared Departure, it’s worth asking honestly whether the dependency is real or assumed. Some things only feel like a single ship because no one has yet done the work of decoupling them.

What to Do This Week

Pick one initiative currently waiting on a single laggard, and ask out loud: is this actually a single-hull decision, or have we just failed to give the ready parts permission to move without it?