BuzbyTimeRead the requirements guide

Remote and hybrid · 6.2

Working across hours nobody shares

Working across hours nobody shares. What decides it, what it costs, and what usually goes wrong. For a practical comparison point, see Monitask's employee scheduling app.

What actually has to be synchronousThe starting point

Less than most teams assume. Genuinely: a decision needing several people to argue, a difficult conversation, an incident, and the first weeks of somebody new.

Everything else — status, review, most decisions, almost all information sharing — can be written, and is frequently better written because it can be read by whoever needs it later. For another perspective on the surrounding workflow, see Gartner.

The cost, stated honestly

Asynchronous work is slower per exchange. A question that would take thirty seconds in a room takes half a day, and a chain of three such questions takes a week.

It is faster overall only if the written record removes future questions, which requires that things are actually written down rather than discussed in a call nobody recorded. Teams that adopt the latency without the writing get the worst of both.

What written culture requires

  • Decisions recorded with their reasons, findable later.
  • Defaults documented, so that nobody has to ask.
  • Questions asked in a place where the answer is visible to others.
  • An expectation that people read, which is a real cost of somebody's day.

The last is the one nobody budgets. A written culture asks everybody for reading time, and a team that writes without reading produces an archive rather than a shared understanding.

Handover across zones

Where a team spans enough hours that one group starts as another finishes, the handover is the whole arrangement. Done in writing at a fixed time it works; done by expecting an overlap call it gradually consumes somebody's evening.

Rotate whose hours are inconvenient. Where one region permanently takes the awkward call, that is a decision being made by geography rather than by anybody.

The date problem in the record

Time entries across zones raise a question nobody expects: which day does an entry belong to. Somebody working at eleven at night in one place is working at nine in the morning somewhere else, and reports built on the wrong answer produce weeks with six days in them.

Decide once whether the record is kept in local time or in a single reference zone, document it, and check that reports agree with the decision.

Meetings that must happen anyway

Schedule them at a time that is unpleasant for the fewest, record them, and write the outcome. A recorded meeting with written conclusions is attendable asynchronously by everybody it was not convenient for, which is the whole point.

Time zone spread has a limit

Three or four hours of overlap makes most arrangements work. An hour makes them strained. None makes them a relay, which is workable for some kinds of work and impossible for anything requiring iteration.

Know which you have before designing the process, and be honest when hiring: a role described as flexible that requires attendance at a call in the middle of somebody's night is not flexible.

Documentation as a deliverable

In an asynchronous team, writing is the work rather than overhead on it. That means allocating time for it, reviewing it, and treating a decision that was never written as a decision that was not taken.

Teams that adopt asynchronous working without accepting this produce the latency without the archive, and conclude that asynchronous work does not function.

The escalation path

Asynchronous by default needs a defined way to break the default: what counts as urgent, who may declare it, and how it reaches somebody. Without one, every question becomes urgent eventually, because that is the only channel that works.

What to record

Give writing its own category. Teams are frequently surprised by how much of the week it consumes, and the number is the argument for either resourcing it or reducing it.

Starting the transition

Pick one recurring synchronous meeting and replace it with a written update for a month. It is a small, reversible experiment that teaches the team more about their own writing habits than any policy.

A short summary

Very little must be synchronous. Asynchronous work is slower per exchange and faster overall only if things get written. Budget reading time. Rotate the inconvenient hours. Settle the time zone question in the record once. And define how to break the default when something is genuinely urgent.

One line to carry

Asynchronous work is a writing practice with a latency cost. Teams that adopt the latency without the writing get the worst of both and blame the arrangement.

Recording across midnight

A shift or a session crossing midnight is an ordinary case that many systems handle badly, splitting it across two days or losing the second half. Test it during evaluation with a real overnight entry; it takes two minutes and it is a common defect.

Where to start

List what your team currently does synchronously and mark which genuinely requires it. The list is usually shorter than the calendar suggests, and the difference is the opportunity.

Tooling

Less important than the habits. A team that writes decisions down does so adequately in almost any tool; a team that does not will not start because a better one arrived.

Reviewing the arrangement

Every six months, ask what has been decided in a call that should have been written, and what has been written that nobody read. Both failures accumulate quietly and the review is the only thing that surfaces them.

Also in remote and hybrid