The 4-day workweek across time zones
The 4-day workweek experiment has been gaining traction since 2020, with strong results from pilots in the UK, Iceland, Spain, and various US tech companies. For distributed teams across time zones, the 4-day workweek can actually be easier to coordinate than for co-located teams. The math is interesting.
For checking how teams in different zones would overlap on a 4-day schedule, the meeting planner helps.
What the 4-day workweek actually is
A few variations:
4×8 (Most common). Work 4 days × 8 hours = 32 hours/week. Pay stays the same. Day off is usually Friday or Monday.
4×10. Work 4 days × 10 hours = 40 hours/week. Same total hours, compressed schedule. Day off is usually Friday or Monday.
Half-day Friday. 4.5 days, with Fridays ending at noon. Sometimes called "half day Friday" or "casual Friday."
The 4×8 model (32 hours, full pay) is what most "4-day workweek" advocacy refers to. Iceland's experiment used this model. UK's 2022 trial used this model.
Why distributed teams have an advantage
The argument: in a co-located 4-day team, the day off is the same for everyone. Friday means nothing happens. Customers calling Friday get no response. External meetings don't happen.
In a distributed team, you can stagger the day off:
- US team off Fridays
- Europe team off Fridays
- India team off Saturdays (already their weekend)
Wait — that doesn't quite work. Let me redo this.
In a fully distributed team across timezones, you can pick which day each region takes off:
- US team: Friday off (so they have a long weekend with mainland Europe)
- Europe team: Friday off (same — many EU countries already have shorter Fridays)
- India team: Saturday off (already Saturday in their weekend)
Or alternatively:
- US team: Friday off
- Europe team: Monday off (so Friday-Monday cross-zone work continues with a smaller team)
- India team: Friday off
The point: by staggering days off, you maintain coverage across the week even though each individual works 4 days.
What the research shows
UK 2022 trial. 61 companies, 2,900 employees. Most participants reported equal or better productivity, lower stress, lower burnout. About 90% of companies continued the trial after the official period ended.
Iceland 2015-2019 trial. 2,500 workers (1% of working population). Productivity equal or better. Worker wellbeing improved significantly.
Spain 2023 pilot. Government-funded; ongoing. Early results positive.
Various US tech companies (2020-2024). Mostly positive reports, though scope and method vary widely.
The core finding: most knowledge work doesn't require 5 days/week to produce 5 days' worth of output. People work harder and more focused with one fewer day.
What 4-day weeks require
For 4-day to actually work:
1. Eliminating waste. Most companies that succeed find ~20% of the workweek is meetings or busy work that can be cut without affecting output.
2. Stronger written communication. Less time means less synchronous coordination; more must be async.
3. Fewer meetings. Often more than half. Most teams that succeed reduce meeting load by 30-50%.
4. Clear priorities. When you have less time, you need a clear answer to "what matters this week?"
5. Trust-based management. Output, not hours, is the metric. Managers must trust that their team works well in 4 days.
Logistical challenges
Customer-facing roles require coverage. If customer support typically responds Mon-Fri, going to a 4-day week needs a coverage plan: stagger schedules, hire more, accept slower Friday responses.
Critical infrastructure still needs 24/7 monitoring. On-call rotations don't change with 4-day weeks; the regular work week does.
Regulatory and compliance may require certain things to happen on specific days. Real estate closings happen during business hours; some regulatory filings have time-of-week deadlines.
Cross-region collaboration can get tricky if Friday is your "off" day but a critical European meeting is Friday at 4 PM London time.
How to start
If you're considering 4-day for your team:
Step 1: pick a timeframe. Start with a 6-month pilot, with explicit success metrics.
Step 2: define the model. 4×8 (full pay, same hours) is the most common. Decide.
Step 3: pick the day off. Friday is most common; some teams pick Monday (good for long weekends or "no-meeting Mondays").
Step 4: cut meetings. Audit existing meeting load; aim for 30-50% reduction. This is hard but essential.
Step 5: explicit priority setting. Each week, the team identifies "the one thing that matters most." Other work is secondary.
Step 6: measure. Track output, employee satisfaction, customer impact.
Step 7: iterate. After the pilot, decide: continue, modify, or revert.
Time zone coordination on 4-day
If your team has people in multiple zones:
Option A — Same day off for everyone. Simpler. Friday off means the company is "closed" Friday. Customers and external partners learn the schedule.
Option B — Staggered days off. US off Fridays, EU off Mondays. Maintains 5-day external coverage with each individual working 4. Harder to coordinate but less customer impact.
Option C — Region-specific. US has 4-day; EU has 5-day. Reflects different cultural norms but creates some inequity.
Most distributed companies trying 4-day pick Option A. Same day off for everyone, even across zones, for simplicity.
What a 4-day week looks like
Sample schedule for a 4×8 week with Friday off:
Monday: start of week, planning. Aggressive priority-setting. "What are the 3 things this week needs to deliver?"
Tuesday-Thursday: execution. Focused deep work blocks. Minimal meetings. Async-first communication.
Friday: off. Long weekend. No work email expected.
The team trades 1 day per week of "soft" time (low-priority meetings, busy work) for 1 day of recovery and personal time.
What's lost
Honestly: some social cohesion. Casual conversations, lunch catch-ups, post-meeting discussions — some of these get cut when you have less total work time. Teams adapt by being more intentional about explicit social time.
Some types of complex collaborative work also suffer. If a project requires intense multi-day collaboration with frequent course correction, 4 days is harder than 5.
When 4-day doesn't work
Customer-facing roles where instant availability matters — customer support, on-call engineers. These need rotation or different staffing models.
Industries with regulatory time requirements — banking, legal, healthcare. Some hours are mandated.
Manufacturing or physical work — different optimization questions; 4-day is sometimes 4×10 (compressed schedule) rather than 4×8.
Companies with heavy meeting cultures that won't change — if you can't cut meetings, you can't fit the same work into 4 days.
FAQ
Will pay stay the same?
In most 4×8 implementations, yes — that's the point. Same pay, fewer hours. Some 4×10 implementations keep pay the same too. The "less work for the same pay" claim is what makes 4-day attractive to employees.
Can a single team go 4-day if the rest of the company doesn't?
Possible but harder. The team's reduced availability affects cross-team collaboration. Best to pilot at the team level with explicit support from the rest of the organization.
What about meetings on the day off?
Don't have them. The day off is the day off. If a meeting absolutely has to happen on a Friday for cross-region reasons, schedule it for one of the working days.
Will I have to work harder during the 4 days?
Usually yes, somewhat. Most 4-day pilots find people work more intensely during the 4 days. Total output is similar to 5-day weeks because the 5-day version had more idle time.
What about overtime?
If you're working 4 days but doing 5 days of output, 4-day works. If you're working 4 days but the work piles up unaddressed, you'll end up working longer hours on those 4 days, which defeats the purpose.
Will my company adopt this?
Hard to predict. Some companies adopted post-COVID; some resist. Industries that already do remote work and async (tech, knowledge work) are leading.
Bottom line
The 4-day workweek works well for most knowledge work, even better for distributed teams (where staggered days off can maintain 5-day coverage). Implementation requires cutting meetings, clear priorities, and trust-based management. It's not magic — companies that succeed put in real effort to make 32 hours produce as much as 40.
For coordinating distributed schedules including day-off staggering, the meeting planner handles cross-zone schedules.