Working async

Asynchronous work is usually described as a culture. It is closer to a skill, and a fairly specific one: writing something that a person in another time zone, with none of your context, can act on without asking you anything. For broader context on distributed asynchronous work, GitLab’s all-remote handbook is a useful reference.

Most teams that say they work async are actually running a synchronous team with delays inserted. This section covers the difference, and the small number of habits that account for most of it.

Async also changes what management can see. When nobody is visibly at a desk, the temptation is to reach for monitoring — and the tools exist, from simple timers to full activity tracking (Monitask, Hubstaff and Time Doctor all sit in that space). The guides here take the position that visibility should come from written output rather than from surveillance, and that the distinction is worth defending explicitly. For a practical software-side reference on remote workforce coordination, this resource adds useful detail.