There is something deeply broken about equating hours to productivity.
It's been my experience that folk are very good at deceiving themselves about their productivity (myself included :-)
One team I worked with had a serious problem with overtime. They were putting in stupid hours and it was showing in the quality of work going out. So I ran an experiment where we all agreed to work "normal" hours for six weeks.
I was "only" working about 45 hours a week at this point, when other people on the team were regularly working 50-60. I was relatively young, didn't have any family pressure, enjoyed my work and felt very productive doing those hours. I wasn't one of the people with a "problem" as I saw it. We were running the experiment for the other folk on the team.
In the experiment we dropped to a 40 hours week (6 hours coding per day, 2 hours for breaks, meetings & lunch). After a couple of weeks adjustment my productivity went way up. I also felt a lot better in myself - generally sharper and more on the ball.
People seem to have quite a wide bad of "this feels okay" that subsumes the much narrower "I'm performing at my best".
Also people don't jump from a 35 hour week to 60 hours a week. It creeps up a few minutes at a time as pressure increases on the team. People have enough time to adjust to it being "normal" and don't notice the drop in productivity that goes with it.
Currently I work roughly 25-30 hours a week and am just as productive by all metrics that I have available to me as when I worked 40-50.
I would strongly urge people to experiment. Pick some metrics, try working shorter hours for a month, see what happens.
(The only caveat I would add is that with folks doing silly hours - anything over 50 I would say - there is often a couple of weeks where things go to hell as the body adjusts. On the team from the story practically everybody caught a bug and felt crap for the first week or so before productivity rose again).
It's funny how the body adjusts. At my last company (I was a director. 1 of 4) we had a MASSIVE problem with working long ours. At the end I was working 100 hour weeks (I only ever had time to eat sleep and work). I pulled the plug after a few years of these self imposed insane hours. You would assume all would be well then but what happened next was completely unexpected.
I fell ill 3 times in the following 3 months, and I was on holidays! Previously I hadn't been sick for years. After a bit of researching I discovered after a period of intense stress, it's pretty common to get sick once you remove that stress.
I remember back in school, I would always get sick during the vacation after an exam. I'm pretty sure it wasn't confirmation bias, and with what you're saying, it even seems plausible.
That true. My bro, a doctor, actually said that mortality rates dramatically increase during a short time (3yr) after retirement. Rapidly removing stress can be as bad for your health as prolonged exposure to it.
This falling ill thing is really interesting and not something i'd come across before. This perhaps goes someway to explaining why it's quite easy to get ill over the Christmas period. The stress in getting all your work done before the break and then an immediate halt of pressure.
I had the same coming from working similar hours at a game company. I took two weeks off between jobs and had a massive crash, which took me months to recover from
The only area we're currently battling the non-4-day-week is with our Support Team. They're currently working 4-day weeks plus about 3 hours on Friday, Saturday and Sunday.
We're hoping to scale that part of the Team so they can get on the 4-day week as well.
It's been my experience that folk are very good at deceiving themselves about their productivity (myself included :-)
One team I worked with had a serious problem with overtime. They were putting in stupid hours and it was showing in the quality of work going out. So I ran an experiment where we all agreed to work "normal" hours for six weeks.
I was "only" working about 45 hours a week at this point, when other people on the team were regularly working 50-60. I was relatively young, didn't have any family pressure, enjoyed my work and felt very productive doing those hours. I wasn't one of the people with a "problem" as I saw it. We were running the experiment for the other folk on the team.
In the experiment we dropped to a 40 hours week (6 hours coding per day, 2 hours for breaks, meetings & lunch). After a couple of weeks adjustment my productivity went way up. I also felt a lot better in myself - generally sharper and more on the ball.
People seem to have quite a wide bad of "this feels okay" that subsumes the much narrower "I'm performing at my best".
Also people don't jump from a 35 hour week to 60 hours a week. It creeps up a few minutes at a time as pressure increases on the team. People have enough time to adjust to it being "normal" and don't notice the drop in productivity that goes with it.
Currently I work roughly 25-30 hours a week and am just as productive by all metrics that I have available to me as when I worked 40-50.
I would strongly urge people to experiment. Pick some metrics, try working shorter hours for a month, see what happens.
(The only caveat I would add is that with folks doing silly hours - anything over 50 I would say - there is often a couple of weeks where things go to hell as the body adjusts. On the team from the story practically everybody caught a bug and felt crap for the first week or so before productivity rose again).