The four-day week has had a wave of high-profile experiments over the last three or four years. Some have stuck. Most haven't. The pattern of failure is fairly consistent and worth being explicit about, because the failures are predictable and avoidable.
I've watched a few agencies try the model, fail, and quietly revert. I've also been on calls with leaders considering it where it was clear, ten minutes in, that they were heading toward one of the standard failure modes. Worth naming the five most common, in approximate order of frequency.
1. Treating the four-day week as a perk
The single most common mistake. Leadership announces the four-day week as part of a broader benefits package — better holiday allowance, mental health days, four-day week — and rolls it out as a wellbeing initiative.
This fails because it doesn't change anything operationally. The team works the same way it did before, with one fewer day to do it in. Output drops. Capacity tightens. Stress goes up rather than down because the same workload is now compressed into less time. Within six months, leadership reverts.
The model only works if it's positioned as an operational redesign, not a benefit. The operating model has to genuinely change. Async-first defaults. Meeting discipline. Different capacity planning. Different decision delegation. The four-day week is the constraint that forces these changes, not the change itself.
Agencies that announce "we're going to four days" without simultaneously announcing "and here are the operational changes that make it work" are setting themselves up to fail. The team can tell the difference between a model and a perk. So can clients.
2. Underpricing the operational redesign
A subset of the first failure mode but worth its own callout. Even when leadership recognises the operating-model dimension, the magnitude of the work is consistently underestimated.
The operational redesign isn't a quarterly project. It's a sustained, multi-quarter investment. Documentation systems that didn't previously exist. Communication norms that have to be deliberately reset. Meeting culture that has to be actively defended. Capacity planning that has to be re-tooled. Decision-making patterns that have to be pushed down the org.
I've watched agencies announce the four-day week with a two-week prep period and a Slack message about new norms. Predictably, the model collapsed within a quarter. The team hadn't internalised the new norms. The client communication hadn't been updated. The senior layer was still being asked to make every decision. The capacity numbers didn't add up.
Realistic prep for a four-day week is at least three months of operational redesign before the model launches, plus six to nine months of active reinforcement after. That's not a small project. It's leadership-level commitment for the better part of a year.
3. Weak leadership discipline
The four-day week works only if the leadership team genuinely doesn't work on the fifth day. The signal travels. If the leaders are checking Slack on Friday, sending emails on Friday, having client calls on Friday, the team will too — because the team takes its cues from the leadership, regardless of what the formal policy says.
We see this fail in two specific patterns.
The first: leadership intends to take Friday off but in practice keeps working because they feel they have to. The team observes this and quietly works Fridays too. The four-day week becomes a four-day-on-paper, five-day-in-practice operating model. The benefits don't materialise because the model isn't actually being run.
The second: leadership formally takes Friday off but keeps available "in emergencies", and the definition of emergency drifts over time. Within a quarter, the leaders are working most Fridays in the name of supporting clients. The team follows. Same outcome.
The discipline has to be authentic at the leadership level. If the leaders can't actually disengage on the fifth day, the model can't run. This is one of the harder pieces of the implementation, because it requires the leaders to genuinely change their working pattern, not just to authorise the team to change theirs.
4. Sloppy client communication
The clients didn't sign up for the four-day week. They have their own urgency, their own budgets, their own deadlines. The agency's operational change is the agency's problem until it's communicated and managed cleanly.
Sloppy communication looks like:
A single email at the launch announcing the change, with no follow-up.
Inconsistent enforcement of the new availability — answering some Friday emails, not others, based on which client asked or which senior person felt awkward saying no.
No clear escalation path for genuine emergencies, leaving clients to guess whether to bother the agency on a Friday.
No update to the formal contract or scope of work to reflect the new operating model.
Each of these creates friction. Stacked together, they create the impression that the agency's operational change is undisciplined, which clients then take as evidence the agency is undisciplined generally. Trust degrades. Retention suffers.
The client communication piece needs to be treated as a behaviour change campaign — explicit, repeated, and consistent in enforcement. Single-message rollouts don't change behaviour. Sustained attention does.
5. Using the four-day week as a cost-cutting move
The most cynical version of the failure pattern: leadership announces a four-day week and simultaneously communicates that compensation will not change. The implicit message is that the team should be grateful for the day back, in lieu of the pay rise that would otherwise have been negotiated.
This fails for two reasons.
The first: the senior people the model attracts are not naive. They calculate the gross hourly rate and notice that the equivalent salary on a five-day basis is now lower than the market norm. They draw conclusions about whether the agency is using the four-day week as cover for lower compensation, and behave accordingly — they accept the role with intent to job-search, or they don't accept the role at all.
The second: the financial argument behind a four-day week — that productivity rises enough to compensate for the lost time — only works if the team is genuinely willing to work harder per hour to compensate. If the team perceives the change as a pay cut in disguise, the productivity lift doesn't happen. The model collapses into a four-day-cost-cut, with no offsetting benefit.
The model needs to be financially neutral or positive to the team. The right framing is: "we're keeping compensation at market rate, and giving the team a day back, because we believe the operating model is better." Anything else is gaming, and the team can see it.
Pulling it together
The five failure modes share a structural feature: each is about insufficient seriousness about the implementation. Treating the four-day week as a perk rather than a model. Skipping the operational redesign. Failing to enforce the leadership discipline. Sloppy client communication. Using it as cost reduction.
The agencies that succeed at the four-day week tend to be agencies that took the implementation seriously. They invested in the operational redesign. They communicated clearly to clients. They held the leadership discipline. They paid people fairly.
It's not that the model is fragile. It's that the implementation is harder than it looks, and most failures are implementation failures rather than model failures.
If you're considering the move and you can credibly invest the time, money, and leadership attention to do it properly, the model works. If you can't, the failure pattern is fairly predictable. Better to keep operating in the existing model than to ship a half-baked four-day week and have to revert.
I'm always happy to talk through this with agency leaders considering it. The conversation that's useful is the one before you've announced the change, not after.