← all posts

There is a meeting happening right now that should not exist.

It was booked three weeks ago, when everyone’s calendars agreed on a slot. Since then, two people moved to different cities, one person switched to a compressed work week, and a third is — for reasons that need not concern us here — operating on a slightly different temporal reference frame.

The meeting still exists. The calendar did not adapt. It never does.

The calendar is not the problem

Most scheduling tools are interfaces to a data structure: a grid of time, divided into slots, populated with events. They are very good at this. The problem is that time, for your team, is not a grid.

It is a set of overlapping, shifting, asynchronous flows. Priya’s Tuesday afternoon is Yuki’s Wednesday morning. Marcus is in a focus block that his calendar says is free. Commander Reyes — we’ll get to her — is experiencing a cumulative temporal offset that no one has accounted for.

A calendar cannot model this. A coordination system can.

Latency is not the exception

We tend to treat time zone friction as an edge case — something to be managed with a world clock widget and a lot of “does this work for you?” emails. But for distributed teams, latency is the normal operating condition. The 9am standup that works for London does not exist for Sydney. The async review window that makes sense in one reference frame looks like a blocker in another.

Continuum’s approach starts from the opposite assumption: everyone is remote, everyone is asynchronous, and the job of the system is to find alignment — not assume it.

What drift compensation actually means

The relativistic features get a lot of attention. We understand why. “Your scheduling tool accounts for time dilation” is a striking sentence.

But drift compensation is, at its core, just a more honest version of what timezone handling should already be doing: tracking the difference between where someone’s clock is and where the team’s shared reference frame is, and correcting for it automatically.

For 99.7% of teams, that drift is measured in hours. For Commander Reyes, it is measured in microseconds that compound over the duration of a mission. The mathematics are different. The systems problem is the same.

The meeting that should not exist

We cannot save the meeting that is happening right now. It is too late for that. But we can make sure the next one is scheduled with full awareness of who will actually be there — and when they will be.

That is what Continuum does. Not magic. Systems thinking, applied to a problem that has been dressed up as a calendar problem for too long.

// no time paradoxes were introduced in the writing of this post