The Clocks That Didn’t Ask

Estimated reading time: 6 minutes

The story

There’s a small printed notice that appears on the pillow or the desk most nights on a cruise: tonight, ship’s clocks move forward one hour. It’s easy to miss between the towel animal and the dinner menu for tomorrow. I missed it once, somewhere in open Atlantic between Cádiz and Porto, and came up for breakfast at what I was sure was 8:00. The dining room was already thinning out. The crew had known since midnight. My watch hadn’t.

Nobody had done anything wrong. The ship’s systems — galley schedules, shore-excursion departures, the bridge log — had all changed at once, cleanly, at the appointed hour. What hadn’t changed, not at the same speed, was me. And walking into a half-empty dining room, the quiet assumption in the room was that I was the one running late, not that the day had quietly moved without waiting to see who was ready.

That’s the clocks that didn’t ask — the moment a system declares a new time and assumes everyone is now living in it, when in fact adoption is uneven, invisible, and usually mistaken for individual failure rather than treated as what it actually is: a gap the change left behind.

The Notice Nobody Reads

Every organizational change has its version of the pillow notice. An email. A slide in an all-hands. A line in a policy update nobody opened. It is technically sent, technically true, and technically insufficient — because a notice satisfies the sender’s obligation to inform, not the receiver’s need to actually notice. The ship isn’t being dishonest when it slides that card under the door. It has simply confused distributed with received.

Leaders do the same thing constantly. The policy went out. The new process is “live.” The reorg was “communicated.” All true, and all beside the point, because the real question was never whether it was said. It’s whether it landed for the specific person now expected to act on it.

“A notice satisfies the sender’s obligation to inform, not the receiver’s need to actually notice.”

Michel Paquin

What Moves Instantly, What Doesn’t

Here is what’s strange about the ship, and about most organizations: the hard systems change instantly. The galley clocks, the crew shift log, the bridge — all synchronized the second the order is given, because they’re machines, or because the crew’s job depends on precision. The soft layer — the passengers, wandering in at their own pace, half-informed, half-asleep — updates on a completely different timeline, and nobody designed for that gap. It’s simply what happens when a system change meets human attention.

Most transformations have exactly this same split. The org chart updates instantly. The system access changes overnight. The new approval workflow goes live at midnight, sharp. But the person who’s used the old workflow for six years doesn’t update at the same speed as the database does. The org has moved. The person is still on old time, and the organization rarely builds anything to notice, let alone close, that gap.

Confusion Gets a Name, and It’s Usually Yours

What happens next is the part worth paying attention to. When I walked into that half-empty dining room, nobody said “the ship changed time zones and we should have been clearer.” They said, kindly, “Oh — did you not see the notice?” The confusion got assigned to me. Not maliciously — it’s just the path of least resistance. It is always easier to treat a person’s confusion as a personal lapse than to treat it as evidence the transition wasn’t actually finished.

This is the quiet cost of the clocks that didn’t ask: it doesn’t just create confusion, it also mislabels the confusion, so the organization never learns anything from it. If lateness is always the individual’s fault, nobody ever asks why so many individuals were late at once.

Why Ships Move the Clock an Hour at a Time

There’s a reason ships don’t cross five time zones in a single overnight jump, even when the itinerary would allow it. They break it into a series of smaller shifts, one hour at a time, over several nights, because a five-hour jump is disorienting in a way a one-hour jump isn’t. Bodies adjust. Habits adjust. Nobody’s whole day gets upended at once.

It’s a useful contrast to the instinct many organizations have toward the single dramatic announcement — the “rip the bandaid off” reorg, the all-at-once system cutover, the policy that flips on Monday with no ramp. Sometimes that speed is genuinely necessary. But it’s worth noticing that the alternative — smaller, sequenced shifts that never ask anyone to lose five hours in one night — isn’t indecision. It’s often the more deliberate design.

Whose Job Is It to Notice

The uncomfortable question underneath all of this: whose job is it to know that the ship changed time and the passenger didn’t? On a cruise, nobody’s, really — it’s a minor inconvenience, solved by asking the nearest crew member what time it actually is. In an organization, the stakes are higher, and the answer shouldn’t default to “the person who was confused should have paid closer attention.”

Someone in the transition needs to own the gap between system now live and people now aligned — not as an afterthought, but as a tracked, visible part of the rollout. Otherwise the change looks complete on the dashboard and incomplete in every hallway conversation, and only one of those two things gets reported upward.

When This Doesn’t Apply

Not every gap between system time and personal time is a leadership failure to fix. Some adjustment lag is normal, expected, and self-correcting within a day or two — chasing every straggler with a formal intervention can turn a minor timing mismatch into more process than the moment deserves. And some changes genuinely do need to happen all at once, cleanly, with no gradual ramp — security patches, compliance deadlines, safety protocols — where the instant cutover is the whole point, not an oversight. The concept is most useful where the gap is wide, the stakes are real, and the organization is quietly blaming individuals for a transition it never finished.

What to Do This Week

Pick one recent change you announced as “done” — a new process, a new tool, a new policy — and ask one person who wasn’t in the room when it was decided whether they actually know it changed. Don’t ask if they received the notice. Ask if they’re operating on the new time.