Four-day work weeks looked good on paper. What actually happened is messier.

The four-day work week made sense as an idea. Fewer days in the office, same output, happier people, lower energy bills. It had the clean logic of a productivity hack, which meant it spread through organizations the way productivity hacks do: with enthusiasm and minimal skepticism.

What's emerged from places that actually ran multi-year experiments is something weirder than the pitch suggested. The results exist, but they don't slot neatly into the "this is obviously good" or "this doesn't work" boxes everyone expected them to fit into.

The thing that keeps showing up across different trials is that compressed schedules do produce real outcomes. Productivity doesn't tank. In some cases it actually improves, which sounds counterintuitive until you think about what a four-day week actually removes from the equation: the low-friction waste of a fifth day. That's not about working harder on four days. It's about what happens when you eliminate Friday afternoon meetings, the slow restart on Monday mornings, the meetings about why you're in meetings. Teams that run tighter calendars tend to move faster. This part is real.

But here's where it gets complicated. Better productivity metrics don't automatically translate into "people are happier" or "we're solving burnout." Some organizations reported genuine improvement in employee retention and morale. Others found that four-day weeks just compressed the same amount of stress into fewer hours. The difference seemed to depend entirely on whether the organization actually changed how it worked, or just deleted a day from the calendar and called it a day. Turns out you can't outsmart organizational culture with scheduling.

There's also something worth noting about who actually benefits. Four-day weeks work differently depending on the kind of work. Roles with deep focus and fewer interruptions tend to see clear gains. Customer-facing teams, support roles, anything with real-time collaboration across time zones gets messier. Some organizations ended up running staggered schedules, which defeats the point. Others discovered they needed coverage five days a week anyway, which means rotating who gets the day off, which feels a lot less revolutionary than the idea promised.

What's genuinely interesting is how the experiments exposed what organizations actually prioritize. Some companies embraced the shift completely, reorganized their meeting culture, and built rituals around shorter weeks. They treated it as a fundamental change in how they operate. Others implemented it as a benefit while keeping all the underlying infrastructure the same, which meant people just worked remotely on their day off to keep up. The system didn't change. Just the appearance of it.

The data suggests four-day weeks work best for organizations that already have strong remote and async practices in place. If you're already comfortable with Teams conversations replacing meetings, with documentation that doesn't require synchronous discussion, with leaders who trust output over presence, then four days is just a logical extension of what you're already doing. If you're not there yet, a four-day week becomes a problem to solve, not a benefit to enjoy.

So the honest read is this: four-day work weeks aren't magic. They're a forcing function that exposes whether your organization actually wants to work differently or just wants to claim that it does. When they work, they work because organizations used them as an excuse to fundamentally rethink how they operate. When they don't, it's usually because nobody addressed the underlying structural problems. A shorter calendar just makes existing dysfunction more visible.