Four-Day Weeks and Compressed Hours in a Distributed Team

Reduced-hours arrangements are increasingly common and they collide with distributed working in a specific way: both reduce the shared time available, and the effects compound.

The three arrangements

Four-day week, reduced hours. Same pay, fewer hours, output expected to hold through eliminated waste.

Compressed hours. Same total hours in fewer days — four longer days rather than five.

Individual flexible schedules. Each person sets their own pattern within agreed constraints.

These have different implications and are frequently discussed as though they were one thing.

The overlap arithmetic

A co-located five-day team has effectively full overlap. Introduce a four-hour time zone spread and you have perhaps half a day of shared time. Now give everyone a different non-working day and, on any given day, a quarter of the team is absent.

Combine the two and the probability that any three specific people are simultaneously available drops sharply. Meetings become hard to schedule, decisions wait, and the team feels slower even though everyone is working effectively.

This is the failure mode, and it is arithmetic rather than attitude.

What makes it work

A common non-working day. Everyone off Friday is far easier to operate than everyone choosing their own day. It creates a predictable four-day week rather than a rota nobody can hold in their head.

The objection is coverage — someone must handle Friday for customers. The answer is a small rotation with compensating time, not abandoning the common day.

Or a fixed per-team pattern. If a common company day is impossible, set it per team so that a team is at least internally aligned.

Genuinely fewer meetings. A four-day week that keeps five days of meetings compressed into four is not a reduction; it is intensification. The arrangements that succeed cut meeting load first and hours second.

Async by default. Reduced days make synchronous coordination scarcer. Teams that already work asynchronously absorb it; teams dependent on meetings do not.

Compressed hours specifically

Four ten-hour days sounds neutral and is not, in a distributed team.

Longer days extend outside colleagues' working hours at one end or both, which either isolates the person or quietly extends everyone else's day. And the day off still removes a fifth of the availability.

It also raises working-time questions in jurisdictions with daily maximums and mandatory rest periods, which are not waived by employee preference.

Setting expectations properly

State response times in working days, not hours. "Within 24 hours" means something different to someone who does not work Fridays.

Publish everyone's pattern where colleagues can see it, alongside working hours and time zone.

Do not let it become invisible unpaid work. The most common failure of reduced-hours arrangements is that the work does not reduce, so people do it on their day off and stop reporting it. Watch for it; it is the signal that the arrangement is not real.

Trialling it

Set a defined trial period with stated measures. Decide in advance what should hold — delivery, customer response, error rates — and what you are willing to accept degrading.

Publish the outcome honestly, including if it did not work. Trials that quietly lapse teach people that stated commitments are provisional, which costs more than the arrangement was worth.