How to Work Remotely Across Oceania Time Zones

Thesis

Remote culture across Tāmaki Makaurau and the US is built in written artifacts and a small, expensive overlap, not in everyone pretending to share one office clock. Protect the Auckland morning. Spend the overlap on ambiguity. Treat delay as the medium, not as a character flaw.

Context

I work the Tāmaki Makaurau clock while engineering commitments still breathe on US Gulf Coast time. Louisiana to Auckland is not a vibe. It is seventeen to nineteen hours, depending on whose daylight saving flipped this month. Time zone math is easy. Trust math is hard.

A standup that is humane in New Orleans is a 4am alarm in Auckland. A standup that is humane in Auckland lands in a Louisiana afternoon that already had a day in it. Rotating that pain is not inclusion. It is a coin flip about whose sleep you are willing to spend. I have sat on both sides of that coin. The meeting almost never needed to exist.

The overlap that actually works is narrow. Auckland 7–10am is roughly a US late afternoon the previous calendar day. That window is the only time both brains are awake without someone performing hero hours. Spend it on the conversation that will spawn three follow-ups. Do not spend it on “yesterday I worked on the ticket.” That sentence can live in a comment.

This is a two-clock problem, not a passport aesthetic. I am Auckland-bound with US collaborators. The work has to survive the offset without anyone becoming the person who is always available.

Mechanism

Async by default is the protocol, not the personality. Write decisions where they can be found: ticket, doc, PR description. Not only spoken in a call half the team slept through. GitLab’s remote playbook is blunt about this because the company ran on it at scale: if it is not written, it did not happen for the people who were not in the room.¹ Expect delay without treating it as neglect. A reply that arrives at the start of the other person’s day is on time. A reply that arrives because someone stayed up to look responsive is a loan against the next morning’s judgment.

I keep a written handoff at the end of my Auckland day: what moved, what is blocked, what I need from US hours, what I will pick up tomorrow. It takes twelve minutes. It saves a meeting that would have cost someone 5am. The handoff is the product. The overlap is for the leftover questions.

Overlap hours are expensive. Spend them like production access. Book the shared window for ambiguity, relationship repair, and conflict. Status belongs in text. If you can paste the update into chat without anyone asking a question, you did not need cameras. Save the live hour for the thing that forks: a schema fight, a hiring call, a postmortem where tone matters.

When I have ninety minutes with a US collaborator, I do not “catch up.” I bring a written agenda and a decision I am willing to own by the end of the call. If we cannot decide in the overlap, we write the options and pick asynchronously. The sun will not wait.

Silence reads as withdrawal unless you publish a rhythm. A 17-hour offset means I am offline for most of their afternoon. If I disappear without a pattern, they invent a story. Short written check-ins, a status that names the next overlap, an honest “I will not be on this thread until 7am NZST” — that is signal, not performance. Remote isolation is a systems failure when nobody names the clock.

Protect the Auckland morning like a deploy freeze. Four uninterrupted hours on the Tāmaki Makaurau clock beat eight fragments timed to US standups. Cal Newport’s case for deep work is structural here: the scarce resource is not presence, it is consecutive attention.² Block the morning on the calendar. Measure output and decision quality, not green dots. Managers who optimize for “caught them online” will harvest night hours from Aotearoa and call it culture.

The calendar has two countries in it. US-centric sprint planning ignores Matariki, ANZAC Day, and the week Auckland actually stops. Aotearoa-centric planning ignores US Thanksgiving and the Friday after a US holiday when half the Slack org is a ghost town. Daylight saving does not flip on the same weekend. Twice a year the overlap you thought you had moves by an hour and somebody’s “quick sync at 8” becomes cruelty. Put both holiday calendars in the same view. Review the overlap when the clocks change. This is operations, not thoughtfulness theater.

Hero hours are a bug you can schedule away. Someone will volunteer to take the 6am call “just this once.” Then the once becomes the default because it worked. Write the default down: no recurring meeting that requires anyone to be awake outside 7am–6pm in their local civil time. Exceptions are incidents and launches, named as such, ended on a date.

Tradeoffs

Always-on chat vs bounded response windows. A documented window in each zone (“Auckland 7am–3pm NZST, Louisiana afternoons for overlap”) prevents the fantasy that someone is failing to care. Boundaries are how the protocol stays humane.

Full remote vs occasional same-room days. Some teams need a quarterly reset in one city. Cost it explicitly: flights, jet lag, whose winter it is. Do not pretend a Zoom standup substitutes for that, and do not pretend you need it every month.

Overlap vs deep work. Every hour you add to the shared window is an hour you subtract from the Auckland morning or the US afternoon where the actual building happens. Cap overlap. Expand writing.

When a live call is correct. Ambiguity, conflict, and care. Not status. If you are scheduling a recurring standup across this offset, you are asking someone to be a worse engineer on purpose.

Close

The deepest work this offset enables is real. So is the isolation if you copy an office calendar onto two oceans. Build rituals that do not depend on everyone sharing one noon.

Pick one norm and enforce it once: decisions in writing, overlap capped at two hours, or no-meeting Auckland mornings. Then keep it. The sun in Tāmaki Makaurau will not move for your sprint.

— JV · Dark Heart Labs.

References

GitLab, The Remote Playbook. Async-first operating rhythms, written decisions, and the refusal to treat timezone delay as disengagement. ↩
Cal Newport, Deep Work (Grand Central, 2016). Structural defense of consecutive focus in knowledge work — the resource an Oceania/US overlap will eat if you spend it on status. ↩