Policy and structure

Deciding what your remote model actually is, and writing it down.

Fully remote, hybrid and office-first are genuine choices with different costs. 'Flexible' is not one of them.

Most policies are written to protect the organisation and read by nobody. What belongs in one that gets used.

Distributed teams fail on time zones more often than on any other dimension. The design decisions that prevent it.

The question is rarely about the job title. It is about which specific activities in the job degrade at distance.

The predictable consequences of a mandate, who leaves first, and how to do it without the avoidable damage.

Team size, reporting lines and boundaries behave differently when nobody shares a room.

Most organisations hold space sized for an attendance pattern that no longer exists, and measure it badly.

Reduced or compressed schedules interact badly with distributed work unless the coordination is designed.

In-person gatherings are the highest-value thing a distributed organisation buys, and most are designed to waste them.