114 ms·
Research does not say that people produce more when working 40 hours per week
- spamizbad 9y agoOn a phone so I can't really crunch the raw data, but looking at that chart example, Is the difference between 48 hours and 60 statistically significant?
- divenorth 9y agoI think we should be looking at efficiency. If we can find a way to maximize the tradeoff between productivity and hours worked it would greatly benefit employers and employees.
- autokad 9y agoi think the author did a pretty good job at looking at the tradeoffs. in a lot of ways, some businesses are already trying to take advantage of both options by using a mix of contractors/consultants and full time employees.
- divenorth 9y agoI guess my opinion is that we should all be working less and earning a living wage. I feel that's the trend that must happen with all the automation taking place. And welcome UBI.
- dec0dedab0de 9y agothat would be great, but many employers would just use that as a reason to pay employees less, or not give them benefits.
- divenorth 9y agoYeah that's the problem. Potential solution is universal basic income.
- the_cat_kittles 9y agoyes, and i would like to see people thinking of efficiency in terms where hours not worked are considered a good. putting it in overly simplistic terms, if someone has a better time not working than the sum of (them working + people consuming their product) then they shouldn't work.
- divenorth 9y agoMy goal in life is to automate myself so I can spend more time at the beach.
- itsdrewmiller 9y agoThe author addresses that and suggests that 40 hours is generally the right number there - productivity on a units per hour basis is maximized. For salaried employees though employers rationally care more about units per week, which continues to increase as hours per week go to 50 and beyond. Of course this is all research of factory work, so its application to software development is questionable.
- divenorth 9y agoObviously the more you work the you produce. From his graph the best productivity is less than 40 hours but he thinks 40 is a good trade off between production and productivity. I disagree. In my ideal world we would be working less and still earning a good wage. I hope to see that in my lifetime but probably unlikely.
- reificator 9y ago> Obviously the more you work the you produce. That's not so obvious in software development, where mistakes from yesterday or 5 years ago can mire you in unproductive work for hours or days. But then I look at lines of code not as value produced but as a resource spent.
- debbiedowner 9y agohttp://www.youtube.com/watch?v=w4Pu_JuPILw&t=2m45s http://www.youtube.com/watch?v=w4Pu_JuPILw&t=2m45s
- jimnotgym 9y agoA bit surprised not to see a reference to Henry Ford. I thought he was the father of the 40 hour work week? He did include in his thinking the idea that more leisure time would allow workers more time to enjoy his cars, but IIRC the basis of the change was not social, but productivity, and based on his own studies.
- pessimizer 9y agoThe 40-hour workweek was conceived of and fought for by many socialists and labor activists over many years. What can be said for Ford is that they instituted it without being forced to (by strike or law), but it was nearly 50 years after it had been instituted for federal employees (and 2 years after it was a part of FDR's platform.) https://en.wikipedia.org/wiki/Eight-hour_day#United_States https://en.wikipedia.org/wiki/Eight-hour_day#United_States
- jimnotgym 9y agoI wonder which had the biggest effect on its widespread adoption, Ford on the unions. I'm sure I read that once Ford did it, it became almost fasionable in the factory owning classes!
- rajeshmr 9y agoI think the real problem is presentialism – people would likely contribute more if they are provided with the flexibility of working according to their body rhythms. Each human peaks at different hours of the day. And being in the knowledge economy, it makes more sense to access these spikes of output by providing flexibility. 40 or 50 or 60 hours, i believe that if we could just eliminate the presentialism from our work life, build more trust with each other about being honest with our work – i think the whole research into how many hours we need to work will not even pop up. Everyone would be happy contributing their share of work in return for a paycheck.
- veidr 9y agoTL;DR: you can get more done if you work 60 hours instead of 40 hours in a week, but the work done in that extra 20 hours might be a small fraction of what gets done in 20 hours during a 40 hour week. This is self-evidently true for many jobs. E.g., if you pick apples for 40 hours, then even if you only pick one apple per hour after that, you will still pick more apples working 50 hours than 40. We software developers, though, have an additional consideration: creating software bugs which can (easily) push the productivity of a given period of time into the negative, sometimes deeply. In my apple-picker example above, this would be like the tired picker driving the loaded apple truck off a cliff, destroying all the apples picked in the first 59 hours of the 60 hour work week (along with the expensive truck). That example is contrived and unconvincing for the apple picker case, though; nobody makes their tired apple pickers drive the apple trucks back via treacherous mountain roads after a hard day of work. That's not the case for software development, however; looking at my own 20+ years of professional software development through the lens of an extremely rigorous scientific n=1 anecdatal analysis (which undoubtedly thrills the OP hehe), in my own career probably 75% of the negative productivity caused by bugs I've created was the direct result of code I wrote while trying to work more hours than I should. I suspect this holds true for other programmers as well.
- justbaker 9y agoSemi-true; it depends how the extra 20 hours are spent for myself. I've had weeks where I program 60 hours or more and it's all spent well, and then the next week I might be a little more burnt out.. take it a little easier and then sprint again.
- JustSomeNobody 9y agoWhich goes towards 60 hour weeks are not sustainable...
- monk_e_boy 9y ago60 hours weeks aren't sustainable, but just look at teams during crunch weeks. They sure get a lot of work done. Sometimes you've just got to put the hours and effort in to get the work done on time. Now I quit very quickly after doing stupid hours a week. But I'd like to think the work produced was fine. Not that much different to a normal week. The work was all planned in detail, there weren't any big surprises, just lots of code to type in, lots of tests to write and run. I was just more tired.
- jbmorgado 9y agoThis title is very odd, I suggest an edit: Research is unable to prove that working more than 40 hours a week increases productivity.
- tobych 9y agoYes, coming from the UK, where my hours in academia were 37.5/week, I was surprised to learn (from my incorrect interpretation of the title) that those 2.5 hours/week I work here in the US were pointless.
- walshemj 9y agoI had one boss who had worked in the valley and the uk he said he got no more work out of the USA teams who worked longer hours and much less leave than he did in the UK where we where on civil service terms
- jxub 9y agoAs an interesting remark, I still find myself quite productive working 50 hours a week thanks to context switches from working in 2 different languages at my jobs (node and python), and in different areas (data engineering and backend)
- endorphone 9y agoWe need to delineate manual, low-effort work from mental exercise. I can perform manual work virtually unendingly, but have a very finite ability to do mental exercises before mental exhaustion or simple boredom/distraction undermines the work. Individuals will differ, but data for manual work has no application to research, software development, etc. Having said that, there is shockingly little research or proof for any position, and if there was it can never be generalized to all people.
- pishpash 9y agoAny creative work does not follow a timeline. Butt in the seat means nothing. In fact, the opposite -- the more relaxed and freeing the structure of work, the better the output.
- combatentropy 9y agoYes, I've thought the same thing. Wasn't 40 hours mainly about factories and coal mines --- though 40 hours in a mine would also be exhausting. But I think you meant something like a barista. To my bosses and other non-programmers, I try to describe programming as doing math problems all day. I wonder what the history of hours is for clerks, architects, and other jobs more like ours. I feel like I would be less tired if I just worked trouble tickets all day. Actually, writing a program too would be easier if that's all I did. Instead, I switch among writing a few different programs, working tickets, and the normal bureaucracy of emails, meetings, required training, etc.
- JBlue42 9y agoBeing a barista can be exhausting at fast-paced place. Not as hard or deadly as coal mining, of course. I work with architects. They work as much as they want to but are paid salary. The minority walk out of the office after their 8 hours is up but many work late into the night and on weekends. They say it's their "industry standard" but, from my observations, it's a) lack of boundaries and b) poor project/time management. Not to mention the amount of time studying to take their many exams to become licensed.
- adekok 9y agoWhich says to me that the game development culture of "work 80 hours per week for months on end" is largely about incompetent management, and/or deliberate abuse. It's not about getting things done.
- itsdrewmiller 9y agoI think you may have misunderstood the article - if anything this is an argument for death marches.
- deleted 9y ago[deleted]
- Gibbon1 9y agoI wonder if the author being a student pushing for a European PhD[1] warps his thinking about this. With a PhD all the reward is at the end. You either make or break. None of the work you do has any tangible results outside of the end goal. Most work isn't like that. The rewards are continuous and ongoing. Meaning every task has captured value. If a loan officer closes 19 loans this month instead of 20, productivity is down 5%. BFD. Vs PhD student, complete 19 out of 20 required classes, no PhD. You totally wasted a couple of years of your life. [1] Europeans historically are way more creditialist than Americans. Learning something isn't very helpful unless there is a credential to go along with it.
- luispedrocoelho 9y agoI have a PhD already (from an US institution), but there are elements that are pretty specific to academic research: it's fairly competitive (and wins are not that constant) and it's very individualized. It's also one where we have almost complete control of our time. It's more like being a freelancer, albeit with a fixed salary in an often bureaucratic environment. I agree with you 100% that most work is not like that at all. (Btw, most PhDs in Europe do not have required classes or, if they do, they tend to be pretty easy; it's the research component that's hard)
- 9y ago
- AndrewKemendo 9y agoI love how things like the 40 hour work week with two days off get enshrined as some kind of natural phenomenon that has always been with us. 40 hours is an arbitrary number that came from trade unionists demanding fair hours and Robert Owen's slogan: “Eight hours labour, eight hours recreation, eight hours rest.” I mean those two things: 8 hour work day and 8 hours of sleep have been considered to be the biological/natural requirements, when the research isn't there for it at all. The reality is, some people can work for 100 hours while others can only work for 20 hours per week without without losing productivity. This is why I'm sick of this stupid trope that nobody should be working 80 hour weeks. Guess what, I want to, that's how my body works, why are you trying to stop me from doing that? When I was in the military I would work 12 hour days every day and my co-workers would complain because I was "making them look bad" that they only worked 8-10. What? Go home if you want. The kind of person you are should push you into those types of roles - not the other way around. A 20 hour a week capable person isn't going to last very long in a 100 hour a week job, and they shouldn't be going out for it. I think the major contention though is that you can't realistically succeed and live comfortably anymore as just a 40 hour a week person, because all of those jobs are gone. So inevitably 20 hour a week people, get put into 60 hour a week jobs and then say the whole system is screwed up (maybe it is, I dunno).
- tertius 9y agoWhere can I find this research showing the health of these 100 hour persons?
- rbjorklin 9y agoNot reasearch but still relevant: http://www.bbc.co.uk/news/business-39981997 http://www.bbc.co.uk/news/business-39981997
- deleted 9y ago[deleted]
- AndrewKemendo 9y agohttps://www.wsj.com/articles/SB10001424052748703712504576242701752957910 https://www.wsj.com/articles/SB10001424052748703712504576242...
- dheera 9y agoI wonder how they got this curve. A lot of things can be sustained for 1 week cannot be sustained in the long term. I'd say in the long term: * 140-168 hours/week --> almost certain death. * 100-140 hours/week --> at risk of cardiovascular disease and many other serious medical conditions. Possible early death. * 80-100 hours/week --> still super-bad for your body. Forget raising children, dating, getting married, or even making friends. You won't have time for any of those. Expect clinical depression. * 60-80 hours/week --> you might be able to have meals with friends but forget having a life, hobbies, or anything outside of work. Expect depression and overall culture of unhappiness. * 50-60 hours/week --> sustainable but not really fun. You can't join family or friends for dinner. Expect talented employees to leave because they'll find something that they enjoy more than being in your company. * 40-50 hours --> reasonable level for long-term sustainability and retention
- kilroy123 9y agoWhat about these? * 30-40 hours * 20-30 hours
- dheera 9y agoI think it depends on the nature of the job and whether or not I "own" my work. If I "own" my work in some capacity, e.g. a freelancer, a co-founder, getting public recognition for my work, getting to publish papers in my name, getting to talk about my work in public, get the chance to open-source my work, then I'm happy working more. If I work for somebody else, or some big boss always takes the recognition for my work, as is often the case in some large companies, then I'd probably be much happier on the <40 side so I have time to learn and build things that are truly my own, outside of work. I think 20-40 might be a sweet spot for certain fields where creativity drives money. In those cases, rest and recreation time are paramount to work productivity.
- kentt 9y agoWe only question hours/week > 40. It's edgy and cool. Past that, you are looked upon as a sluggard or kook.
- 9y ago
- ninjakeyboard 9y ago40 hours is good for me for "you must do work" but lots of times when I'm working on projects I find interesting I'm just inspired to work on the project.
- awinter-py 9y agoArticle is focused on the academic world so doesn't talk about interruptions, meetings, and quiet time. If you work in an open-plan office the 10 hours you do at night, at home, and on the wkend can be the most productive. I've had months where I put out more real fires on a kayak, on vacation, than at my desk; people bother you when you're at a desk but they can't get to you on the water.
- titanomachy 9y agoAcademia isn't exempt from those things. A professor (PI) is as much a manager as anything.
- luispedrocoelho 9y agoAll these things happen in academia. Nowadays, many people regularly work from home for the quiet (I do 1 day a week from home).
- mempko 9y agoProductivity is the greatest source of waste.
- dahart 9y ago> the point of productivity inflection is just about 40 hours per week To me, that does seem to support the claim “research shows that 40 hours per week is the best”. I don't know who's claiming that overall output goes down the minute you hit 40, that's obviously exaggerated, so why take it so seriously? There's strong evidence that productivity starts to decline somewhere around 40ish, and it obviously varies by individual and situation. I think the more common, and more correct claim is that 40-ish is optimal, rather than anything above 40 is a negative return. That bit of data he referenced is for munitions workers doing a low-skill monotonous job - easy to measure productivity. Who would expect to produce solid high quality thought output for 40 or 50 hours a week? I'd be surprised if most academics & programers managed more than 15 hours of conceptual work in a week, the rest we fill with coffee & lunch, browsing the web, talking to people, and loads of other stuff that doesn't require much thinking. The author's completely right about many of his points; this just isn't clearly defined or unambiguously supported by data. There are obviously some people out there rationalizing and mis-presenting the evidence in favor of a 40 hour work week. As with all studies, there are people who summarize incorrectly and decide that weak evidence justifies a hard line decision. But why get twisted over the worst arguments? Let's discuss the strongest arguments instead. Do we need data to support the idea that 8 hours is enough? Productivity is only a tiny part of the equation, so this debate is academic. Why are we obsessing over unmeasurable productivity and ignoring labor & poverty issues? Do you need data to prove that when you work 12 hours a day, you physically can't have much life outside of work? The idea of an 8 hour work day is meant to work for everyone. It's guaranteed to be conservative, because it has to be good enough for teenagers as well as people near retirement, for single people as well as parents, for everyone.
- deleted 9y ago[deleted]
- Spooky23 9y agoThat encourages bad behavior and ultimately decreases productivity.
- WisNorCan 9y ago"If you are managing as a group, go for the average" This is a point I strongly disagree with. Just the way some people need fewer hours of sleep than others OR some people can run further than others. I have found that people have vastly different ability to focus and personal drive. Orienting around averages is a terrible way to develop a team and people. It also demotivates people that want to work harder and they end up leaving. Instead of setting an average, create an environment where people can push harder if they want to AND get incremental rewards.
- luispedrocoelho 9y agoOP here. I agree and my phrasing may not have been exact. I meant that if you need to pick a number for a whole group of people, then you look at the average. This can be in the context of industrial production where you have thousands of workers and are forced to have fixed shifts (because you cannot run the assembly line without all the stations filled). Or, in more modern example, a public sector bureaucracy where you cannot be very flexible as these things are negotiated with a union as whole.
- rb808 9y agoDoes this include side projects? ie if you work 10 hours/week on a side project you shouldn't work more than 30 in your job. Maybe employers should be able to ban side projects for this reason.
- michaelmrose 9y agoMaybe if you don't want any good employees
- walshemj 9y agoGiven the source of employment law is the masters and servants act I think you might find that employers can veto outside work certainly getting permission for out side work is often required by contract.
- heisenbit 9y agoAbility to perform is in part a function of age which the article leaves out completely. 40h/week is doable for most but there are plenty of posts by more experienced developers here who have said they strictly limit hours or report that when they were younger they were able to perform longer. There is also the question of sustainability. Not only health wise but also the social system around one gets impacted imho. somewhere beyond 45-50h. More work directed output may well be possible but at the cost of weakening the support system and with that increased risk in times of crisis. I'm willing to discuss this more in depth with the author once he's got a few grey hairs.
- slaymaker1907 9y agoI think the key thing for me is that maybe I produce more one week, but working 60+ hours is going to make me useless the following week.
- deleted 9y ago[deleted]
- johnmyers2 9y agoWe work a 9/80 flex schedule. 44 hours one week, ,then 36 hours the next with Friday off. So every other weekend we have a 3 day weekend, or 4 if there is a holiday on Monday. Works great, moral increases, productivity increases. Its a win, win.
- logingone 9y agoAt my last job I probably did 20 hours of work a week due to the awful environment. I started burning out from frustration. I'm not convinced the number of hours is as important as the suitability of the environment.
- sklivvz1971 9y agoHogwash: 1. Go read the linked article: http://ftp.iza.org/dp8129.pdf http://ftp.iza.org/dp8129.pdf 2. It's about munition line workers in 1920 UK during the war. 3. The blog post claims generality based on this.
- lstroud 9y agoThe question is how long you can maintain a pace (hours worked) before that pace begins to impact performance. Usain Bolt can't run his 100m pace for the duration of a 400m race.
- freeduck 9y agoWhat a strange article, his first issue: "I am happy to be contradicted with data, but too often I see this issue being discussed with links to web articles citing other web articles, finally citing studies which suffer from the issues listed below. Maximum output at work is traded off" while he him self does not cite a single scientific article
- luispedrocoelho 9y agoI do cite one study, but burden of proof of producing citations is on people claiming that "science shows". I never claim that. In fact, I found few scientific articles on the subject and the few that I did find were not relevant (for some of the reasons in the text).
- launchtomorrow 9y agoNo one seems to have mentioned the value of the work done. Like market value or impact. The quantity of work is kind of a distraction, and focusing on it implicitly says that presentalism is ok. Which is not true.
- GoldDust 9y ago40 hours per week is detrimental to the health as well, especially if you don't take breaks where you exercise vigorously. I've seen research that showed a 4% reduction in lifespan for people that worked 45 hours versus 40. I'll look for it and be back with more details.
- WalterBright 9y agoDuring WW2, the government wanted to increase production, so did some studies. They found that a 60 hr week boosted production for a couple weeks, but then it fell below what was produced by a 40 hr week. The solution to a sustained increase in output was to do 60 hr weeks in bursts, not continuously.
- majewsky 9y ago"In bursts" as in "40 hours with the occasional 60-hour week" or "60-hour weeks with weeks off in between"?
- WalterBright 9y agothe former
- watwut 9y agoThe study I have seen claimed that 40-50 hours long term have same output and then it goes down. The studies on game development teams found that crunch raise productivity of short (don't recall if 3 or 6 weeks) and productivity goes down only after. This article does not seem to adress concrete studies nor their results - it just generally theorise about what might be wrong about them without knowing what is on them.
- luispedrocoelho 9y agoOP here. Do you have a citation? The post is mostly to address this constant claims that 40 hours is proven by science and no convincing citations are provided. I am also writing in the context of self-managing knowledge workers who can manage their own time. I explicitly write that the flexibility we have may mitigate many of the downsides observed in mandated long hours. For example, I do work >40 hours, but I rarely have to wake up with an alarm clock. I can follow the occasional 16 hour day with a 10 hour sleep cycle and stroll into work at lunch time the next day feeling pretty relaxed.
- kbutler 9y agoThis essay and most of the comments saying, "of course more work time yields more work completed" ignore the fact that there is no magic reset to full productivity Monday morning. If you work every hour of week 1, your output of week 2 will be drastically reduced. There is therefore some optimal balance between work time and recovery time. It may be 40 hours, or 20, or 80. It probably varies between tasks and individuals and situations. Just don't fall into the trap of thinking that spending more time working is necessarily going to be more effective. Sometimes the best thing you can do to get the job done is to stop working on it for a while.
- majewsky 9y ago> Sometimes the best thing you can do to get the job done is to stop working on it for a while. This. I like to have several side projects at once so I can switch to another one when I'm stuck on the current one. On the downside, this procedure made me question if I can actually work as a programmer professionally, where I don't have the liberty to just leave any task assigned to me lying around for a week (or a month). It worked out nicely, though, since I found that I can get my train of thought unstuck by discussing the problem with a colleague.
- ryanbrunner 9y agoOne point I'll agree with is that a lot of times, people use the argument that working 40 hours a week is actually the most efficient to mask their real argument, which is socially unacceptable in today's business climate (particulary tech): People ought to have more to their lives than their jobs, and working 50, 60, or more hours a week makes that difficult. Personally, even if people had inexhaustible energy, I still would think it would be wrong to spend more than a third of your day at work. It so happens that it makes sense from an efficiency standpoint to, but I want people working under me to be able to have hobbies, families, and something other than their career.
- mcv 9y agoWhen I read the title, I thought: if there's no evidence that people produce more when working 40 hours, why would we work 40 hours? Let's work less! I didn't expect anyone to argue for working more than 40 hours. But then again, I don't live in the US.