The four-day work week has been the subject of more corporate pilot programmes, research studies, and think-pieces in the last five years than almost any other workplace policy. The headline findings are consistently positive: productivity holds, wellbeing improves, employees prefer it, companies that try it rarely go back.
The honest version is more complicated. Productivity holding is not the same as productivity improving. Some roles and industries make the transition easily; others do not. And the specific version of the four-day week a company implements — a compressed 40-hour week versus a genuine 32-hour week versus a flexible schedule — produces very different results.
This article covers what the research actually shows, what tends to change when teams move to four days, what time tracking data reveals that surveys do not, and what to consider before committing to a change that is harder to reverse than it looks.
What is a 4-day work week?
A four-day work week is a working arrangement in which employees work four days per week rather than five. The definition splits on one critical dimension: whether the total hours stay the same or reduce.
The compressed week (4×10 or 4×9): Employees work the same total hours — 40 or 36 — across four days instead of five. Friday (or another day) is off, but Monday through Thursday are longer. This is not a reduction in work; it is a rearrangement. It benefits employees who want a consistent day off for personal reasons and can tolerate longer working days.
The reduced hour week (4×8, or 32 hours): Employees work four eight-hour days — 32 hours total — and are paid the same as they were for 40. This is a genuine reduction in contracted hours at no reduction in pay. It is the version that generates the most research interest and the most dramatic productivity claims.
The flexible 100-80-100 model: Employees receive 100% of pay in exchange for 80% of the time, committing to 100% of the output. This is the framework used by the 4 Day Week Global research programme. It is the version that produced the results most frequently cited in media coverage.
When someone says “the 4-day work week works,” the version they are describing matters enormously. A compressed week is relatively low-risk and low-reward. A genuine 32-hour week is high-risk and high-potential-reward. The research, the case studies, and the implementation advice below apply differently to each.
What the research actually shows
The 4 Day Week Global pilot (2022–2023)
The most cited evidence for the four-day work week is the 4 Day Week Global research programme, which ran pilots across the UK, Ireland, US, Australia, and Canada. The UK pilot — 61 companies, roughly 2,900 employees, six months — is the most frequently referenced.
The findings: revenue stayed roughly the same or improved. Employee wellbeing improved significantly across all measured dimensions. Sick days fell by 65%. Staff resignations fell by 57%. At the six-month mark, 92% of participating companies said they intended to continue with the four-day week.
What the research does not show: whether the productivity improvements hold over years rather than months. Whether they hold for all sectors equally. Whether they would hold without the Hawthorne effect — the well-documented tendency for observed performance to improve simply because people are being observed. And whether the companies that self-selected into a voluntary research programme on four-day weeks are representative of businesses generally.
Microsoft Japan’s experiment (2019)
Microsoft Japan ran a one-month trial of a four-day week and reported a 40% productivity increase. This number has been cited extensively. What it measured was meeting efficiency — less time in meetings meant more output per hour — not total output. The 40% figure represents the productivity gain from meetings that should have been emails, not from a fundamental change in how knowledge work happens.
Iceland’s public sector trials (2015–2019)
Iceland’s government ran the largest public sector four-day week trial, involving around 2,500 workers. Productivity was maintained or improved in most workplaces. The trial led to negotiations that resulted in shorter working hours for 86% of Iceland’s workforce by 2021. The caveat: public sector roles — administrative, social care, emergency services — are structurally different from knowledge-work roles, and the generalisation from one to the other is imperfect.
The honest summary
The evidence that a well-implemented four-day week can maintain productivity in knowledge-work roles while improving employee wellbeing is genuine and growing. The evidence that it works universally, for all role types, at all company sizes, without careful implementation, is not. The research supports thoughtful piloting; it does not support assuming the results will transfer automatically.
What changes when you move to four days
What genuinely changes for the better:
Meetings get ruthlessly evaluated. When every working hour becomes more precious, the meeting that was scheduled for “alignment” and spent 45 minutes on things that could have been an email gets cut. Most teams that implement four-day weeks report that meeting time falls significantly — and that the meetings that remain are more focused. This alone is often responsible for a substantial portion of the reported productivity gains.
Deep work time increases. An additional day free from meetings, email, and Slack notifications gives people a mental reset that often results in higher-quality focus during the four working days. The cognitive recovery time of a three-day weekend is meaningfully different from a two-day weekend for knowledge workers doing complex, cognitively demanding work.
Employee wellbeing improves reliably. More time for family, health, personal projects, and rest produces measurable improvements in stress, sleep, and reported happiness. This is the finding that holds most consistently across different studies and different industries.
Recruiting and retention improve. A four-day week is a significant differentiator in a competitive hiring market. Companies that have implemented it consistently report it as their most powerful recruiting tool — because it is something most employers cannot easily match.
What does not automatically change:
The volume of work does not reduce. The work still needs to get done. If a team was working at capacity on five days and nothing changes in terms of workload or scope, moving to four days creates pressure that manifests as longer working days on the remaining four, work spilling into the off day, or declined standards. The four-day week works as a productivity challenge — the implicit contract is “find a way to do what you need to do in four days.” It fails when it is implemented without examining what is on the list.
Client expectations do not automatically adjust. A client who expects same-day email responses on Friday will not be satisfied by a message saying “we are on a four-day week.” This requires explicit client communication, appropriate automation, and in some cases, maintaining coverage on the fifth day through rotation.
Not everyone on the team benefits equally. Roles that require coverage — customer support, operations, anything with a service level agreement — cannot simply not show up on Friday. Four-day weeks in these contexts require rota systems that ensure some team members work Monday–Thursday and others work Tuesday–Friday. The benefit is real but the logistics are more complex.
What time tracking data shows that surveys miss
Surveys are how most four-day week research collects its evidence: employees report how they feel, how productive they feel, how much they are working. The limitation of self-reported data is that perception and reality diverge in predictable ways.
Time tracking data reveals what actually happened, not what people remember or prefer to believe happened.
What time tracking typically shows during four-day week pilots:
The working day does extend. In most teams that track time honestly, the transition from a five-day to a four-day week does not produce four eight-hour days. It produces four eight-and-a-half to nine-hour days. The total hours may not fall as much as the policy implies. Whether employees consider this a reasonable trade for a three-day weekend is a personal question — but it is important to know that it is happening.
Some work moves to the “off” day. In teams with permissive cultures around the fifth day — working is allowed but not expected — time logs frequently show some activity on that day, particularly before deadlines or during high-pressure periods. The true four-day week requires organisational norms and systems that make it genuinely difficult to work on the fifth day, not just a policy that says you do not have to.
Meeting time falls — usually. Time logs categorised by meeting vs task time almost always show a reduction in meeting hours when a four-day week is implemented. This confirms what survey data suggests. It also reveals exactly how much of the “productivity gain” was meetings being cut versus actual work becoming more efficient.
Context switching frequency may not change. One of the theories behind the four-day week’s productivity benefit is that more focused time produces higher output per hour. Time tracking data on context switching — how often people switch between task types within a day — often shows this does not change automatically. The structure of the working day needs to be redesigned alongside the number of working days, or the benefit is diluted.
How to use time tracking during a pilot:
Before the pilot, track time normally for 4–6 weeks. Establish a baseline: total hours worked, hours by project type, meeting time, context switching frequency, and when during the day work is being logged.
During the pilot, continue tracking with the same categories. The comparison between pre- and post-pilot time data tells you more than any survey: are people actually working fewer hours or just fewer days? Is meeting time falling? Is deep work time increasing? Is the fifth day genuinely free?
After the pilot, use the data alongside the wellbeing survey results to make a decision based on both the human experience and the working reality.
Time Bot logs working time from the first /t task command to the /t finish command each day, captures every task transition, categorises time by project and task type, and produces daily and weekly reports automatically. For a four-day week pilot, the reports require no additional setup — the data is being collected regardless, and the pre/post comparison is straightforward.
Who it works for — and who it doesn’t
Tends to work well:
Knowledge work and creative roles — writing, design, software development, strategy, research. These are roles where output quality depends heavily on cognitive state, where deep work time is valuable, and where the product is ideas rather than hours. The four-day week’s primary mechanism — more rest producing better focus — applies directly.
Roles with measurable output. If you can determine whether the work got done regardless of when or for how long, a four-day week is both manageable and assessable. A developer who ships code, a writer who delivers articles, a designer who produces assets — these roles are evaluatable on output.
Companies where client relationships allow it. B2B companies with established client relationships, where clients care more about results than about Friday availability, are better positioned than consumer-facing businesses or companies in industries with urgent service expectations.
Tends to be harder:
Customer-facing roles with coverage requirements. Any role with a service level agreement — customer support, account management, technical support — cannot simply be unavailable on Friday. The four-day week in these roles requires a rota or shift system that adds management complexity.
Industries with five-day week norms. A law firm, a trading desk, a medical practice — industries where client expectations are built around five-day availability face a more significant change management challenge than industries where remote work and async communication have already shifted expectations.
Companies where management does not genuinely support it. The most reliable predictor of a failed four-day week implementation is senior leadership that supported the policy change but did not change how they operate — continuing to send emails and schedule meetings on Fridays, creating implicit pressure that the fifth day is not genuinely free.
How to run a 4-day week pilot
A four-day week is easier to start than to stop. Before committing to a policy change, run a time-limited, well-measured pilot with a clear decision criteria.
Step 1 — Establish your baseline before starting
Four to six weeks of normal working, with time tracking running, gives you the numbers to compare against: total hours per person per week, meeting time as a proportion of working time, output metrics (whatever is appropriate to the role), and a baseline wellbeing survey.
Step 2 — Define the version you are piloting
Which day is the off day? Is it fixed or rotating? Is it a compressed week or a genuine hour reduction? What are the coverage expectations for client-facing roles? What happens if a deadline requires Friday work? Answering these before the pilot removes the ambiguity that derails most implementations.
Step 3 — Address the workload question explicitly
The four-day week does not automatically reduce the work. Before the pilot starts, go through the meeting schedule and cut aggressively. Review processes that create overhead without producing value. Set expectations with clients or internal stakeholders about availability. The pilot needs to answer the question “can we do what needs doing in four days” — which requires examining what needs doing.
Step 4 — Run the pilot for at least three months
One month is not enough to distinguish between the Hawthorne effect and a genuine change in working patterns. Three months gives time for the novelty to wear off, for the team to develop new habits, and for a clearer picture of the sustainable rhythm.
Step 5 — Measure both the data and the experience
At the end of the pilot: compare time tracking data (hours per week, meeting time, output categories) with the pre-pilot baseline. Run the same wellbeing survey. Review output metrics. Make a decision based on both — the number are what happened, the survey tells you how people experienced it.
Step 6 — Decide with clear criteria
Before the pilot, agree on what a successful outcome looks like. What level of output maintenance qualifies as “productivity held”? What wellbeing improvement is sufficient justification? What happens if results are mixed — some team members thriving, others struggling? Having criteria before seeing the results removes the confirmation bias that tends to produce decisions that favour the policy the team already wanted.
The compressed week vs the reduced hour week
The distinction between working 40 hours in four days versus 32 hours in four days is significant enough to treat as a different policy.
Compressed week (4×10):
Lower risk, lower reward. The three-day weekend is real. The working days are longer, which can cause fatigue and makes the policy less suitable for roles that require sustained concentration throughout the day. Employees often report that the longer working days erode some of the benefit of the shorter week. This format works well for roles where the working day is already variable (field work, project-based work) and less well for roles where the workday has a natural rhythm.
Reduced hour week (32 hours, same pay):
Higher risk, higher potential reward. This is what the research programmes tested. The implicit contract — same output for less time — requires both the productivity gains the theory promises and a willingness to examine and reduce low-value work. When it works, it works better than the compressed week. When it fails, it fails more visibly: work piles up, employees feel pressure on the fifth day, and the policy is reversed.
The 32-hour week works best when implemented as a challenge — “let’s see if we can do this” — with genuine management support, genuine workload examination, and genuine cultural permission to not work on the off day.
How to measure whether it’s working
Three data types, measured before and after:
Time data (objective) Total hours worked per person per week. Hours logged on the “off” day. Meeting time as a proportion of total working time. Context switches per working day. These are available from time tracking data without any additional effort if tracking is already running.
Output data (role-specific) Whatever measures the role’s output: code deployed, articles published, deals closed, support tickets resolved, designs shipped. These must be defined before the pilot — ideally the same metrics already used for performance assessment. If there are no output metrics, the pilot is measuring the wrong thing.
Experience data (subjective) Wellbeing survey: stress, sleep quality, sense of control over time, energy at the end of the working day, confidence in the team’s ability to manage workload. Also: would you return to five days for a salary increase, and if so, how much? The answer to the last question reveals how much employees actually value the change.
The combination of objective time data, output data, and wellbeing survey data is more reliable than any single measure. Productivity held and wellbeing improved is a strong case for continuation. Productivity held but hours extended significantly is a case for reconsidering the implementation. Productivity fell regardless of wellbeing is a case for reversal.
FAQ
What is a 4-day work week? A four-day work week is a working arrangement where employees work four days per week instead of five. It comes in two main forms: a compressed week (same total hours — typically 40 — across four longer days) and a reduced hour week (typically 32 hours at the same pay as a previous 40-hour week). The two produce different experiences and different results. Most of the research showing strong productivity and wellbeing outcomes relates to the reduced-hour version, not the compressed week.
Does the 4-day work week actually work? The honest answer is: often, for knowledge-work roles, with careful implementation. The 4 Day Week Global research programme — 61 companies, 2,900 employees — found that revenue was maintained or improved, sick days fell by 65%, and staff resignations fell by 57%. These findings are genuine. They are also from companies that self-selected into a research programme on four-day weeks, may include a Hawthorne effect, and do not necessarily generalise to all industries or all implementation approaches. The four-day week is worth piloting in the right context; it is not guaranteed to work universally.
What is a 32-hour work week? A 32-hour work week is a four-day working arrangement where employees work four eight-hour days — 32 hours total — at the same pay as a previous 40-hour, five-day week. It is the most researched and most controversial version of the four-day week. The core argument is that productive output in knowledge work does not scale linearly with hours, and that the final eight hours of a 40-hour week produce less output than the first eight hours — meaning cutting them has less cost than expected. Time tracking data during pilots often shows that actual hours worked in a “32-hour week” are closer to 35–37, as working days extend slightly.
How do you transition to a 4-day work week? Start with a time-limited pilot (three to six months) rather than a permanent policy change. Establish a baseline with time tracking and output metrics before the pilot begins. Define the specific version you are implementing, address coverage requirements for client-facing roles, and explicitly cut low-value meetings and processes before starting. Run the pilot with genuine management support — including senior leaders not working on the fifth day. Measure time data, output data, and wellbeing survey results throughout. Make a continuation decision based on pre-defined criteria, not on whether people liked it.
What does time tracking reveal about 4-day weeks? Time tracking data during four-day week pilots typically reveals: working days extend by 30–60 minutes on average (so actual hour reduction is less than the policy implies), some work appears on the “off” day in most teams, meeting time falls substantially (often 20–30% of previous meeting volume), and context switching frequency does not automatically improve without deliberate redesign of the working day. Surveys tend to show more positive results than time data alone, because the experience of a three-day weekend is genuinely valuable even when the hours did not fall as much as expected.
What is a compressed work week? A compressed work week is a schedule where employees work the same total hours — typically 40 — across fewer than five days. The most common format is four 10-hour days (4×10). Unlike a genuine four-day work week, a compressed week does not reduce total working hours. It provides a consistent additional day off in exchange for longer working days. The compressed week is lower risk to implement and produces fewer of the dramatic results reported in four-day week research — because the mechanism of the research (more rest, better focus, cut the low-value hours) does not apply when total hours are maintained.
