Our Fully Remote Team Tried 4-Day Work Weeks for 6 Months — The Results Wrecked Everything We Assumed

On September 1st, 2025, our 14-person marketing agency went from five-day weeks to four. Fridays became "Free Fridays" — no meetings, no Slack, no email expectations. Six months later, I have a 47-page internal report, three resignation letters (two came back), and a conviction that the 4-day work week discourse is missing the point entirely.

This isn't a puff piece about how everything was perfect. It wasn't. But the failures taught us more than the wins, and most articles about 4-day work weeks conveniently skip the messy middle. So here's the messy middle.

The Setup

We're a fully remote content marketing agency based across three time zones (US Eastern, Central, and Mountain). Before the experiment, we ran a standard 5-day, 40-hour week with "flexible hours" that, let's be honest, meant people worked whenever their Slack pinged them. Cal Newport calls this "pseudo-productivity" and he's right — we were measuring presence, not output.

The 4-day structure: Monday through Thursday, 9am-6pm in your local time zone, with one hour for lunch. That's 36 hours instead of 40. No salary reduction. The deal was simple — maintain output quality and client satisfaction, and Fridays stay free.

Month 1-2: The Honeymoon (and Its Cracks)

Productivity initially spiked 23%. Classic Hawthorne effect — people work harder when they know they're being observed. Our project completion rate went from 87% to 94%. Client satisfaction scores held steady at 4.6/5.

But something else happened. Meeting time decreased by only 12%, which meant meetings were now consuming a larger percentage of available work hours. On a 5-day week, 8 hours of meetings is 20% of your time. On a 4-day week, it's 25%. Nobody noticed this immediately. It crept up.

By week six, three team members — independently, without coordinating — sent me variations of the same message: "I love Free Fridays but I feel more stressed Monday through Thursday." We had compressed the work without compressing the overhead.

The Meeting Audit That Changed Everything

In late October, we did something radical. We audited every recurring meeting. All 34 of them.

Results: 11 meetings had no clear purpose or could be replaced by async updates. 8 had too many attendees (average meeting size: 6.2 people; average number who actually needed to be there: 3.1). 15 were genuinely necessary.

We killed 11 meetings. Cut attendance on 8. Left 15 alone. Total meeting time dropped from 8.3 hours/week per person to 4.1 hours/week. That one change — not the 4-day week itself — is what actually freed up capacity.

Kenji Yamamoto, our lead strategist, put it perfectly: "We didn't need a shorter week. We needed fewer meetings. The 4-day experiment just made the meeting problem impossible to ignore."

Month 3-4: The Async Revolution

With meetings cut in half, we needed better async communication. We adopted a system inspired by Basecamp's Shape Up methodology:

• Loom videos replaced status meetings. 3-5 minute recorded updates instead of 30-minute syncs. Team members watched at 1.5x speed on their own time. Average time spent on updates dropped from 2.5 hours/week to 47 minutes.
• Written pitches replaced brainstorm meetings. Instead of gathering 6 people in a Zoom room to brainstorm, one person writes a 500-word pitch document. Others comment asynchronously. Better ideas, less groupthink, 83% less time consumed.
• "Office hours" replaced ad-hoc questions. Each team lead held 2 hours of open video chat per week. Need help? Drop in. Don't need help? Don't. This eliminated roughly 60% of "quick question" Slack interruptions.

Tools that made this work: Loom for async video, Linear for project tracking, Notion for documentation. We'd tried Notion before but never committed to it. The 4-day constraint forced discipline.

The shift also required individual productivity habits. Several team members started using focused productivity apps for tracking deep work blocks, which helped them protect their concentrated work time from async notification overflow.

The Resignation Problem

In month 4, three people resigned. Here's what actually happened.

Two resignations were unrelated to the 4-day experiment (one relocated for family reasons, one got a 40% salary increase elsewhere). The third? Complicated. She was a project manager who thrived on real-time coordination. The async shift made her feel disconnected and undervalued. "I'm a people person working in a text-based world," she told me during her exit interview.

We hired her back two months later as a part-time "sync specialist" — someone whose job is specifically to handle the real-time coordination that still needs to happen. She works Tuesday-Thursday, 20 hours/week, and is happier than she's ever been here.

Lesson: async-first doesn't mean async-only. Some work requires real-time interaction, and some people need it psychologically. Build room for both.

Month 5-6: The Numbers

Here's where I get specific, because vague claims about "productivity went up" are worthless without context:

• Revenue per employee: $14,200/month (before) → $15,800/month (after). That's an 11.3% increase.
• Client satisfaction: 4.6/5 → 4.7/5 (marginal but positive).
• Employee satisfaction: 3.8/5 → 4.4/5 (significant jump, measured via anonymous quarterly survey).
• Sick days taken: Average 1.2 days/month → 0.4 days/month. This one surprised everyone. People weren't using sick days as mental health breaks anymore because they had Fridays.
• Voluntary turnover (annualized): 28% → 14%. In an industry where turnover averages 30%, this alone justifies the experiment.

The cost? We lost approximately 8.3% of total available work hours (36 vs 40). We gained 11.3% more revenue per person. The math works because the hours we eliminated were mostly low-value: meetings, context-switching, and performative presence.

What I'd Do Differently

1. Start with the meeting audit, not the schedule change. The 4-day week was a forcing function, but you can cut meetings without changing your schedule. Do that first. If it frees up enough capacity, then try compressing days.
2. Plan for the "sync personality" problem. Not everyone thrives in async environments. Identify who needs real-time interaction early and create roles/spaces for it.
3. Set explicit async norms from day one. Response time expectations (4 hours during work hours, never expected after hours), video length limits (5 minutes max for Loom updates), written format standards. We figured these out through painful trial and error. You don't have to.
4. Measure continuously, not just before/after. We almost abandoned the experiment in month 2 because of the stress complaints. Weekly pulse surveys saved us — we could see problems forming and intervene before they became crises.

Is Four Days Right for Your Remote Team?

Maybe. But probably not for the reasons you think. The 4-day week isn't magic — it's a diagnostic tool. It exposes inefficiencies that a 5-day week masks. Meeting bloat, unclear priorities, performative busyness, poor async practices. All of these hide in 40 hours. Compress to 36, and they become visible.

If your remote team is drowning in meetings, context-switching constantly, and measuring presence over output — a 4-day experiment won't fix those problems. But it will make them impossible to ignore. And sometimes that's exactly what you need.

We're staying with the 4-day week. Not because it's trendy. Because the data says it works for us. Your data might say something different. Run the experiment. Measure honestly. Adjust. That's it.