Less Days, More Drive: What Happened When 12 US Companies Tried Working Four Days a Week

For decades, the five-day, 40-hour workweek has been treated like gravity — just a fact of life, something you don't really question. But a growing number of American companies decided to push back on that assumption, and what they found might change the way you think about how your team spends its time.

We looked closely at pilot programs run by twelve US-based organizations across a range of industries — tech startups, mid-size marketing firms, a regional healthcare admin group, a logistics company, and even a small manufacturing outfit in Ohio. Here's what the numbers — and the people behind them — actually revealed.

The Setup: Not All Four-Day Weeks Are Created Equal

Before diving into results, it's worth clarifying something that trips up a lot of conversations about this topic: there's no single version of a four-day workweek. Some companies went with a compressed 4x10 model — same 40 hours, just squeezed into four longer days. Others adopted the true 32-hour model, cutting total hours while keeping pay flat. The distinction matters enormously, and the outcomes reflected that.

Of the twelve companies studied, seven used the 32-hour model. The remaining five compressed their hours. Spoiler: the teams that actually reduced hours reported significantly higher satisfaction scores and lower burnout indicators than those who just rearranged the same workload.

What the Productivity Numbers Showed

Here's where things get interesting. Across the board, output either held steady or improved. A Denver-based software agency reported a 22% increase in completed project milestones over a six-month pilot, while a New York PR firm saw client deliverable quality scores tick up by 18% based on client satisfaction surveys.

But productivity gains weren't universal. The logistics company struggled with client-facing coordination — when their team took Fridays off, vendors and partners operating on standard schedules created bottlenecks that chewed into Monday efficiency. The lesson there wasn't that the four-day week failed; it was that implementation without stakeholder alignment is a recipe for friction.

The healthcare admin group in the Midwest saw something particularly telling: error rates in data processing dropped noticeably during the pilot. Managers attributed this to employees arriving at their desks more rested and mentally sharper. Less fatigue, fewer mistakes. Simple math, but powerful in practice.

Team Energy: The Metric Nobody Was Tracking (But Should Have Been)

Productivity is measurable. Energy is trickier — but it might actually be the more important variable.

Several companies used pulse surveys throughout their pilots to gauge team morale, enthusiasm, and what researchers sometimes call "discretionary effort" — the willingness to go beyond the bare minimum. Across the seven companies using the true 32-hour model, discretionary effort scores rose by an average of 31% compared to pre-pilot baselines.

Employees weren't just completing tasks; they were bringing fresh ideas to meetings, volunteering for stretch projects, and reporting stronger relationships with their coworkers. One team lead at a Chicago-based content studio described it this way: "People stopped watching the clock. They stopped mentally checking out at 3pm on Thursday because they knew Friday was coming. They were actually here — like, fully here."

That kind of presence is hard to manufacture with a ping-pong table or a free lunch. It turns out the most effective perk might just be giving people their time back.

Where It Worked Best — and Where It Didn't

Industry and team structure played a huge role in determining outcomes. Knowledge workers — developers, writers, designers, analysts — adapted most smoothly. These roles already have a somewhat flexible relationship with time; what matters is output, not hours logged. Giving those employees an extra recovery day let them approach complex cognitive work with more bandwidth.

Customer-facing roles were trickier. A retail-adjacent company in the pilot struggled to maintain service coverage without hiring additional staff, which partially offset the cost savings from reduced overtime. For industries where coverage and availability are non-negotiable, the four-day model requires either creative scheduling (rotating days off across the team) or a willingness to invest in coverage infrastructure.

Team size also mattered. Smaller, more autonomous teams transitioned faster and with less disruption. Larger organizations with deeply interdependent workflows — where one team's output is another team's input — needed longer runway to redesign handoffs and communication cadences.

The Implementation Lessons That Actually Stuck

Talking to managers and HR leads across these twelve companies, a few consistent themes emerged about what made pilots succeed or stumble.

Clarity over assumptions. Companies that explicitly defined what "success" looked like before the pilot started had an easier time evaluating results and making the case to leadership for continuation. Vague goals produced vague outcomes.

Process audit first. Several teams discovered that a significant chunk of their week was consumed by low-value meetings and redundant check-ins that nobody had ever thought to question. The four-day constraint forced a reckoning with workflow inefficiency that was overdue regardless of the schedule change.

Manager buy-in is non-negotiable. In every case where a pilot underperformed, there was at least one layer of middle management that was skeptical, disengaged, or quietly undermining the experiment. Culture change flows through managers. Full stop.

So, Should Your Company Try It?

That depends on a lot of factors specific to your team, your clients, and your industry. But here's a reframe worth sitting with: the question isn't really "can we afford to lose a day?" The question is, "what are we actually getting out of the time we already have?"

The companies that thrived in these pilots weren't just compressing schedules. They were rethinking the relationship between time, energy, and output — and building a culture where people could do their best work, not just their most hours.

That's not a four-day week experiment. That's a better way to work.