Cross-zone collaboration should show the other person's local time
Aliases: their local time · dual timezone · meeting in their time · counterpart clock
What it is
Booking a cross-zone meeting and stating one’s own 3 p.m. clearly still leaves the other person doing mental arithmetic. Showing the counterpart’s local time means the collaboration UI offers two clocks at once: what time it is here, what time it is there, and whether that instant falls in their workday or their night. Stating affiliation is the prerequisite. What this adds is computing their local for them to see, not leaving each person to convert.
Why it happens
The decision unit in collaboration is not “some instant on UTC”. It is “will they be around, is it decent”. Decency is local: work, sleep, pickup. Giving only one’s own local pushes both the conversion and “does this count as a disturbance” onto the organizer’s head. Integer offsets are barely doable; half-hour zones, a day boundary, or a counterpart currently travelling raise the error rate, and meetings at their midnight are how that error looks.
Putting their local beside the invite, the message timestamp, the presence line, moves conversion out of the head and onto vision. A second layer is working-hours contrast: two numbers side by side are not enough; it must be visible that this is their 9 a.m. or their 11 p.m. — same instant, different social meaning. Local time moves when someone travels; an interface still pinned to “their company city” is not showing their local now.
Where it stops holding
When the counterpart’s zone is unknown, refused, or a group spans more than about three zones, a local axis cannot be drawn for everyone. Fall back to “your local plus a stated instant” and let each person read their own. One-way broadcast (an announcement, a recording) has no counterpart; label the publisher’s zone or the viewer’s local, and do not invent an interlocutor. Expanding everyone’s local on every historical message turns the thread into a conversion table; the contrast needed in the moment belongs on invites and in the live conversation, not as dual clocks on every old line.
Applying it
- On invites, conflict checks, and agreed times in a thread, show “my local / their local” side by side, and make it visible if it lands in their night.
- If they are travelling or the device zone just changed, use the current device zone, not a headquarters pin that never moves.
- For meetings spanning more than two zones, offer a per-participant local summary, not only the organizer’s clock.
- How to check: send a “tomorrow at ten” invite across an eight-hour gap. The recipient should see their own local without arithmetic. Drop the meeting on their 3 a.m.; the contrast should read as night, not as two daytime-looking numbers.