The Four-Day Week, From the Employee's Side

Most writing about the four-day week is aimed at executives deciding whether to run a pilot. This one is aimed at the person who would actually work it — someone weighing a job offer that advertises it, or thinking about asking for one, or already inside a badly-implemented version and wondering why it does not feel like the brochure.

I should say where I sit. I lead a research and development team on a standard schedule; I have not run a four-day pilot. What I have done is manage delivery under time pressure, which gives me an opinion about where the hours in a knowledge-work week actually go, and that turns out to be the crux of the whole thing.

The distinction that decides everything

"Four-day week" refers to at least three arrangements that feel completely different to the person living them.

A genuine reduced week means roughly 32 hours, full pay, and a real reduction in total work. This is the version with the interesting evidence behind it and the version people mean when they get excited.

A compressed week means the same 40 hours in four longer days. You get a three-day weekend and you pay for it with four days that start early and end late. For some people — long commutes, no caregiving duties, a job with natural stopping points — this is a clear win. For a parent doing school pickup, it can be worse than what they had. It is a scheduling change, not a workload change, and it should not be sold as the same thing.

Belgium is the standard example of legislative progress here, and the standard example is usually stated wrongly. Belgian law gives employees the right to request compressing a full working week into four days. It is the second model, not the first, and it is a right to ask rather than a guarantee.

A flexible or rotating model means the team covers five days while individuals work four, with days off staggered. Whether this is good depends entirely on whether the coverage maths was done honestly or whether four people are now absorbing five people's work.

Before you get excited about any employer's four-day policy, establish which of these it is, in writing. The vocabulary is used loosely, sometimes deliberately.

What the evidence supports, stated carefully

The strongest public result is the UK pilot, in which dozens of companies ran a reduced-hours week for six months. The widely-reported headline was that the large majority of participants chose to continue, with improvements in self-reported wellbeing and a drop in resignations. That is a real finding from a real study, and it is the number worth anchoring to.

It is also worth knowing its limits, because you will be arguing this with a sceptical manager. Participating companies volunteered, which means they were predisposed to make it work. Much of the outcome data is self-reported. And "chose to continue" is a decision by the employer, which is meaningful but is not the same as a measured productivity gain.

Then there is the case everyone cites and almost nobody describes correctly. Microsoft Japan ran a short trial in August 2019 and reported a roughly 40% improvement — but the measure was sales per employee over a single month, compared against the same month a year earlier, in a country where August is a holiday period, alongside simultaneous changes capping meeting length and attendance. It is a suggestive anecdote about cutting meeting waste. It is not evidence that a four-day week raises productivity by 40%, and quoting it as such to anyone numerate will cost you the argument.

The honest summary: for output-driven knowledge work, a reduced week appears to be achievable without the disaster sceptics predict, mostly by eliminating work that was never producing anything. For hour-bound work — a ward, a line, a counter — the hours do not compress, and the only route is more staff.

What it actually feels like, and the failure mode

The recurring complaint from people inside four-day arrangements is not that the work is impossible. It is intensification: the same load in less time, with the slack gone. The days that used to contain some recovery — a slow Friday, a meeting where you could think — become uniformly dense. People describe finishing the week more tired than before, holding a third day off they spend recovering.

This happens when the organisation cuts the day without cutting the work. The four-day week only functions if something is genuinely removed, and the removal is unpleasant: meetings that existed so that people felt included, reports nobody reads, projects kept alive for political reasons. Companies that are good at saying no can do this. Companies that are not will hand you a compressed schedule with a nicer name.

So the diagnostic question, when evaluating any employer's version, is not "how does it work". It is: what did you stop doing? A team that has genuinely made this work can answer immediately and specifically. A team that cannot answer has moved the hours around.

Second diagnostic: what happens when a deadline slips. If the honest answer is "people work Friday", the policy is a perk that evaporates under exactly the conditions where you would want it.

Asking for one

Most people asking for a four-day week are asking as individuals inside a five-day organisation, which is a different and harder request than a company-wide policy. A few things make it more likely to land.

Ask about the model you actually want. A lot of individual requests are really requests for reduced hours at reduced pay, which is a much easier approval — it is a part-time arrangement, and organisations have a template for it. If that is acceptable to you financially, say so, because it removes the main objection. If you want full pay for fewer hours, you are asking for a raise in effective hourly terms, and you should be clear-eyed that this is what you are asking for.

Propose it as a bounded trial with a named review date and a stated definition of failure. Managers reject open-ended commitments and accept reversible experiments. Saying "three months, and if X slips we go back" costs your manager very little.

Deal with the coverage problem before it is raised. Who handles the thing that arrives on your day off, and what is the escalation path. This is the objection that kills these requests, and arriving with an answer to it does more than any amount of research about pilot studies.

And be realistic about which roles permit it. Individual contributor work with clear deliverables is the easy case. Roles that are fundamentally about availability — management, on-call, client-facing, anything where your value is partly that you are reachable — are much harder, and pretending otherwise damages your case.

The part worth saying plainly

There is a genre of coverage that treats the four-day week as inevitable, a matter of when rather than if. I would not plan a career around that. Adoption has been real but slow, concentrated in smaller knowledge-work firms, and it moves with the labour market — when hiring is tight, flexible arrangements spread; when it loosens, they quietly recede. Several of the highest-profile pilots of the last few years have not become permanent policy at scale.

The useful stance is narrower. If you can get a genuine reduced week, it is one of the more valuable non-cash things an employer can give you, and probably worth more to you than the equivalent salary. If what is on offer is a compressed schedule, evaluate it as a schedule change and check whether ten-hour days actually suit your life. And if you are already in one that leaves you more tired than the five-day version did, the problem is not you failing to be productive enough. It is that somebody cut the day and forgot to cut the work.