"Demand is relentlessly rising. Our capacity is not keeping pace. The traditional solution to higher demand has been to invest more time. Unfortunately, time is finite, and most of us have no hours left to invest. Energy, however, can be systematically expanded --- and it can also be regularly renewed. To operate at our best, we need four energy sources: physical (quantity), emotional (quality), mental (focus), and the energy of the human spirit (purpose). This talk will focus on the role of energy in fueling sustainable high performance, and in motivating others."
>and the Dutch people are better known for their love of cycling
We don't 'love' cycling it's just highly ingrained in our culture and it's way cheaper than owning a car, especially with our awesome public transport.
>But what about tackling the issue at its roots? What if everyone had a shorter working week? We would be healthier and happier, and society would be less unequal and more sustainable.
Is it? How is this article different from pure speculation?
Well, it's not speculation to compare Britain to Denmark, which have comparable living standards, levels of technology, &c but different attitudes to the working week.
No-one in Denmark/Germany is a slacker, btw. They're just really productive when they're actually at work.
It seems to me that the spirit of long working hours stems from the idea that a worker is an interchangeable 'machine' with a capacity to provide effort and the idea that more time spent (literally) at the coal face will yield a better return on capital.
This holds true in an industrial context where there is a large pool of workers, the work is low skilled and unions are weak. A workers ability to provide time is the only concern that the employer has. Where I live, in the North of England, this factory mentality still casts a long shadow over working conditions and practice.
I think a 40 hour week is way too long to actually have a balanced life and I've consistently burnt-out where the pressure to work 50/60 hours a week is strong.
I'm not surprised that DavCam is wanting to keep the 48-hour opt-out - if you are an investor / owner of capital, do you care about the long term well being of the people making effort to give a return on your capital over a short term (5 years) when people are interchangeable? You simply want to increase the return on your investment.
The article makes the fundamental error of assuming that if you worked ten hours less, someone else would get to work ten hours more. But other than that, it's a pretty good article grounded in actual fact.
Yes, it would only work in sectors where the labor is more or less fungible, but these types of articles always seem to overgeneralize the effectiveness of reduced work hours.
I agree that shorter hours are likely to be beneficial, but why are people trying to achieve this by passing a law?
I think that this can be achieved with a softer approach. Imagine that when you sign up for a job, you select how many days per week do you want to work, from 3 to 6, with proportionate wage scale. That you can select what hours do you want to work. That it's easy to change this arrangement while you're already working.
Now, why is this fantasy not a reality? Not because of laws; laws allow this. But:
1) These creative arrangements require non-standard agreements, and a lot of additional bureaucracy, because in a lot of countries, all the bureaucracy machinery allows it, but is really not optimized for use-cases like that.
This can be solved through careful policy work, removing necessary paperwork, streamlining processes, etc.
2) Economies of scale. Having a full-time 40h/week employee that gets X money as salary is cheaper than having 2 half-time 20h/week employees that get X/2 money because of management overhead, cost of their office spaces and other stuff like that.
This would be solved if 20h/week employees would understand this and get X/2-Y money. Also, a lot of these scale issues are being solved by modern world anyway, because we're learning to telecommute, work together in more effective ways, automate management tasks, etc.
3) Culture.
And I think this is the most important one. It's not in the laws, it's in the people's heads. We need to convince people that one person wants to dedicate work 60 hours per week, spend free time that's left on professional education and succeed in his career, and another is quite OK to work for 20 hours per week, get less promotions, learn less new stuff and earn less money, and spend all his free time with his kids. We need to stop labeling the first of these persons as "successful" and second one as a "failure": it's OK to be both of them. And they need to be able to work in the same office, on the same project, fully understanding difference in each other's views and being mutually acceptful.
I don't know how to do that, but it seems that this cultural change is already slowly happening. Still, advancing it would bring the real change much faster and more effectively than writing new laws.
Laws are pretty important, actually. IIRC, in Slovenia, if you don't work 40 hour weeks, you'll have issues with retirement (e.g. you'll have to retire later, or your pension would be smaller (regardless of your salary)). I'm assuming there are similar issues with health/social insurance.
Your comment (point 2 especially) reflects the current widespread notion (among employers at least, it seems) that one hour of work is one hour of work, always. I think the main point of the article is exactly to counter that.
> "Productivity – output per working hour – improves with shorter hours."
And why should the employer get all the benefit from this? I think a lot of people would love to work fewer hours, be more productive those hours, if they could retain the same salary.
I would love to, at least, but can't afford reduced pay.
I'm "paid for" 40 hours a week. However since I'm awesome, it takes me only 20-30 hours a week to accomplish more than the output of the younger software developers. Work from home, come in late, come in early, work late, leave early. Doesn't matter, it balances out.
The more I work from home, the greater productivity gains I have over everyone else that remains at the office. It's satisfying.
And I get paid more than them by at least 40%. Go figure.
So sauronlord's reply contributes nothing as an answer to my question about golergka's statement which was: "Thankfully, we don't analytically decide who takes the benefits — labor market is working pretty well at figuring this out."
I'm genuinely curious to know how we would know whether the labor market is working well at figuring this out or not.
Because I know how it compares to planned economy, which was doing it completely awfully in comparison. And in general, by every measure labour markets which have enough volume to regulate themselves fair far better than labour markets that are small or subjected to monopoly from either side.
> We need to stop labeling the first of these persons as "successful" and second one as a "failure"
It's not about judging employees from a moral standpoint, but getting the most skill and involvement going into your project/company. So, one of the questions would be: does 20h/wk + 20h/wk = 40h/wk skills+involvement, ie. is it linear? Wouldn't 20h/wk jobs be limited to inherently part-time, low importance tasks--which means you got to have plenty of funds to staff for them in the 1st place?
> Wouldn't 20h/wk jobs be limited to inherently part-time, low importance tasks--which means you got to have plenty of funds to staff for them in the 1st place?
Interesting question. Not necessarily; as a lead developer, I just had an experience of a talented freelancer joining my project for 20 hours per week and helping with issues that we delegated to him so we can fit in the deadline. On one hand, _usually_, 9 women don't make 1 baby in 1 month; on the other hand, in this particular case the freelancer new the technology really well, and we delegated him with special issues that required less knowledge of our whole project and more knowledge of the tech itself.
So — yes, 20h/week limitation creates some problems, when you're working in the 40h/week team, but it's not the end of the world.
Freelancers often work part-time because they are more expensive, so they are not hired full-time, but they generally have many clients in the same week when they can. Moreover, they most often have some expertise in their field, which means they still devote quite a bit of time keeping up to date--they don't just spend their time with the kids. What they can do, though, is taking several months off, either between contracts or when it is ok with their long-time clients.
Anyway, that's a kind of special situation, essentially unrelated to the employee working 20h/wk to take care of their family.
> So, one of the questions would be: does 20h/wk + 20h/wk = 40h/wk skills+involvement, ie. is it linear? Wouldn't 20h/wk jobs be limited to inherently part-time, low importance tasks--which means you got to have plenty of funds to staff for them in the 1st place?
It would seem to me that 2 people working 20h/wk offers some significant advantages over one person working 40h/wk.
Firstly, it allows for fail-over; when one person is unable to work (due to holiday or illness, for example) the other might be able to handle 40h/wk for a short period to cover. If one person leaves the company suddenly, it allows for continuity of knowledge while a third person is hired and trained.
Secondly, it allows for variable output; two people can "burst" up to 80h/wk in response to workload, whereas one person would find that very stressful.
Thirdly, multiple people bring multiple points of view, increasing the chances of serendipitous ideas and solutions, and increasing the potential benefit of using people's special skills or experience. Basically, the company is renting two brains for the price of one.
There are some downsides too: The management overhead is higher (equipment, legal, payroll, etc...) and things that were simple when done by a single person are now more complex since there needs to be coordination between multiple people.
To use an incredibly bad analogy: It's like moving from a monolithic "big iron" server to a pair or farm of smaller ones. There are many advantages, but it means it's now a distributed system with all the problems that can bring.
The problems aren't insoluble and don't limit 20h/wk employees to low-importance tasks: Many open source and volunteer projects function perfectly well with many, small, variable inputs from their contributors, many of which will be high-importance.
> To use an incredibly bad analogy: It's like moving from a monolithic "big iron" server to a pair or farm of smaller ones. There are many advantages, but it means it's now a distributed system with all the problems that can bring.
The thing is that, as you noted yourself, the analogy doesn't hold, for people are not AWS servers waiting for charge or failovers. If they chose to work 20h/wk, it's presumably to spend their time for other pursuits, eg. family, and they often won't be able to or won't agree to work more when their employer need it, perhaps unless it is planned well in advance (eg. Black Friday period).
> Basically, the company is renting two brains for the price of one.
Or, as I questioned, you might got two partly focused and perhaps less skilled people thinking about your problem, instead of someone more skilled totally focusing on it. As was brought in another comment, if you got two freelancers, then yeah, you could pick two brains, but if you have two family guys, not so much.
I think the analogy holds for the case of employees not having the capacity to give extra hours due to other commitments. However, I totally agree that people aren't AWS servers, and the reason I felt the analogy was bad was that such a mechanistic view doesn't leave room for the multitude of positive, human ways of working around such problems. For example: if an employer asks a 20h/wk employee to work extra hours, then there can be a negotiation around whether the extra hours can be done at home, flexibly in the evenings, or for a higher hourly rate. In other words, people can compromise and negotiate a settlement which is beneficial for all.
I also don't think it's necessarily true that two part-time people would be less skilled or less focussed on work. It's the very point of the original article that working fewer hours can increase the quality and focus of the work done during that shorter period.
I've worked with many talented and exceptional "family guys" (and family women) who were skilled and totally focussed during working hours. I haven't noticed a correlation between people's priorities outside working hours and ability to do good work.
> It's the very point of the original article that working fewer hours can increase the quality and focus of the work done during that shorter period.
To me, it depends on how you cut the hours, and to what extent. I'm all for working shorter days, eg. 6-8h, 4-5 days a week; however, the more you get close to half-time or below, the more difficult it becomes to stay fully focused and as motivated as a (more) full-time employee. This is admittedly less of a concern if the person uses their free-time on related projects (eg. writing open-source stuff).
The only way to change culture is through law. Look at seatbelt use: decades of public awareness campaigns did nothing, but once it became a legal requirement people switched.
In France working 35h/week is actually enforced by law. I personally think it's good for productivity (France is still considered a very productive country, more than Germany for instance) but this law remains regularly critiziced. Many want it removed or updated.
It's very hard to measure human productivity unfortunately. It's much easier to measure the cost of an employee working less hours for the same salary.
There's a very weird and irrational belief that more hours on the job means more productivity. Projects are often goal-based now.
But management hasn't entirely caught up with the idea that jobs are no longer about clock punching - and longer clock times can mean less real worker value.
This is partly about power dynamics in the workplace. In many corporations control of time and personal freedom are perks that are only available as you move up the hierarchy. Dysfunctional cultures are much more interested in explicit displays of limited freedom for the worker bees than in true increases in productivity.
Not entirely true (I'm French BTW). In a lot of companies if you're engineer or similar you're "cadre", and not subject to the 35h/week limitation: you have flexible work day hours. There's still a maximum limit, I think you must have at least 10h of rest a day but don't quote me on that one.
To compensate for the more than 35h/week work days you do have more vacation days call RTT for "Reduction du Temps de Travail" (Work Time Reduction). It's about 8 days per years, on top of regular vacations.
Also laws are the way to prevent a race to the bottom. If it's legal to work longer hours people will, and everyone else will do so to compete with them.
Oh, is that why almost everyone earns minimum wage?
> Every full-time job is 40 hours, which is the maximum allowed without having to pay overtime.
Categorically false. I'd wager 90%+ of the (American) readers here are exempt FTEs, meaning they are paid a salary which is based on calendar days/weeks/months/year, not hours worked.
Very few jobs offer 35- or 30-hour weeks (which would still be called full-time). There are part-time jobs that have much shorter hours, or often no contractual hours, but they're a different thing.
That's exactly why. Because minimum wage puts a floor on the 'bottom' that's being raced to. Otherwise, people would be earning considerably less than the current minimum wage, because the 'bottom' would be even lower.
The question was sarcastic (poor form, I know). More than 90% of workers earn above minimum wage, despite this supposedly inevitable race to the bottom.
Education just changes the rules of the game when it comes to working time. In the US, once you have your college degree, you morph from an hourly employee where overtime is paid, to an 'exempt employee' where extra hours are unpaid.
Over the years, the federal government has added more jobs to the exempt employee list. This means we get things like fast food store managers making $26K/yr putting in 60 hour weeks. There has been a push to change the minimum salary to $50K/yr for exempt employees, but employers have successfully delayed the implementation of this till late 2016.
Ideally, the US needs to rewrite the Fair Labour Standards Act to be more in line with the EU working time directive which limits the working time to an average of 48 hours over a period of several weeks. This allows overtime to be used in bursts, but not chronically.
I'm confused. That proves his point. Every state at a secondary enforcement seat belt law before 1998. Every state aside from Maine and South Dakota (both of which had relatively high seat belt usage before the law) saw an increase in seat belt usage post-law.
I think you might be confused by the 1998 number. That year came after the after law percentage. Meaning that enforcement immediately after the law also worked.
No, the law only brought the 17% of change. The law change is binary and sudden, but the change in culture brought all the rest, gradually, year after year, before law and after.
You are making assumptions based on zero evidence. The change is binary, enforcement is over time. You are assuming the change from 48% to 65% (which is also a 17% increase) can be explained sans law, but there's zero evidence that's the case.
In the interest of not citing 12+ year old studies relying on 17+ year old data, 2013 usage was 87% and since 1995 there have only been two years of decreasing average usage[0], '05-'06 (82-81%) and '10-'11 (85-84%).
To truly see any trend, we would need to look at not just before the law, but many years before the law.
This is one of those sneaky tricks advocates for government intervention use (or fall victim to). To prove the efficacy of OSHA, for example, proponents will show a chart of workplace fatalities or accidents where there are a few or only one data points before the law and then show some spectacular trend that follows after the law was passed. In reality when you go back many more years it is clear the law had little to do with the trend as workplace safety had been increasing for years prior to the law.
Not at all. For gay marriage or pot legalization, large shifts in public opinion have preceded changes to laws.
If it's legal to work longer hours people will, and everyone else will do so to compete with them.
The Moloch post is excellent, but it doesn't really apply here. Productivity isn't a zero sum game; unless you're in a dysfunctional stack ranking environment like Microsoft used to have, being more productive doesn't hurt your coworkers.
And for tech workers in particular, it's impossible to prevent you from working "off the clock" in your spare time. Yet people generally don't, probably because as others have noted just adding hours doesn't actually make you more productive.
I think the point of the Moloch reference wasn't that individuals would work longer hours, it's that companies that have people who work longer hours will be more successful.
Changing the law is not the only thing that would need to be done.
You would also need an executive order to change the way that federal contracts are handled. Currently, huge numbers of salaried professionals employed by contractor companies have to punch the clock as though they were wage-earners in order for the company to get paid for their work.
If you don't log X hours during a given week, your salary for that week may be docked by N/X. If you log more than X, you are not necessarily paid any more for overtime. The contractor-employer could set X to be 40, or 45, or 50--whatever it wants.
If an executive order said that no individual could work more than 30 hours total in any calendar week on any combination of federal contracts, unless that person is paid an additional 10% of their normal weekly salary for each hour in excess of 30 (aka triple-time OT), while the company still gets paid the same rate, then lo, nearly everyone in the military-industrial complex would suddenly have a 30-hour work week.
As it is now, the contracting arrangements dance around the fuzzy edges of labor law, to the detriment of the workers and to the benefit of their employers, and possibly also to the benefit of several additional layers of middlemen. Changing the law is meaningless if you can't enforce it.
> I agree that shorter hours are likely to be beneficial, but why are people trying to achieve this by passing a law?
We tried asking nicely; employers were abusive arseholes. This is why we can't have nice things.
Without law we see huge rich multinationals forcing people to stay at work but "clocking off" (and thus not getting paid) when things are quiet; or asking for very long hours without sensible overtime.
> I agree that shorter hours are likely to be beneficial, but why are people trying to achieve this by passing a law?
> I think that this can be achieved with a softer approach
That's a bit of a "trickle down economics" argument. Depending on corporations and owners to offer an option is never going to be as effective as passing a requirement.
As long as you only care about "effectiveness" of the conversion to smaller working hours — yes. But my point is that we should care about creating an environment where people are actually free to choose how much are they supposed to work.
In other words, you argue of how effective we can be in achieving our goal, while I suggest redefining the goal itself.
We should reduce full time employment to 30 hours.
You'd probably end up with nearly equal productivity for office staff, and you'd generate more jobs for shift based work, as you would need 30% more workers to cover a 5-day period.
This was one of the drivers of the 40-hour workweek -- previously, 12 hour days + saturday work were considered the norm.
This can be effective in jobs where there is a labor shortage but not a labor surplus.
Meaning, if you are applying for a job that 100 other people are also applying for, you don't get to make these kinds of demands. Whoever is hiring you will simply pass you over.
However if you happen to be working a position requiring skill with a labor shortage (they are having a hard time finding someone qualified to fill the position) then you definitely could be in a position to negotiate for these things.
I think this is why people would be inclined to making it law, there are a lot of jobs where the workers wouldn't have the leverage to affect this kind of change.
Totally agree. I don't see how people can be productive working >60h/week and doing mental job. I find 30h/week to be perfect as I can't keep concentrated more than 3-5 hours straight, so that makes two streaks (2-3h) and a coffee break working day Monday till Friday. If I'm forced to work longer hours, I find my mind wandering around, rewritting the same code over and over or reading HN. Of course, there might be some short-term mission critical periods when I can honestly put ~10h/day, but it's an exception that must be justified, not a rule.
I think one of the problems is that some people in powerful positions in companies want to do long hours themselves, so expect those under them to do the same. They see someone putting in long hours as hard-working and diligent, even though in reality they are probably being very inefficient and producing shoddy work.
If you have to have your bum in the seat for 40+ hours/week to get paid, why would you bother? The "bullshit" gives you something to do when you're too tired to be actually productive.
If your inbox is full of bullshit, try taking proactive steps to clear it out. If it's a waste of corporate time, you have a basic professional responsibility to do so.
If you fail, it is likely because it wasn't as bullshit as you thought. The cogs may be sexy and obviously doing work, but the grease turns out to be vital too. But my "if" isn't for mere rhetoric... you may well succeed, because bullshit does build up too. The only way to find out is to try. I've had it go both ways.
I'd like to believe this article, and in fact strive myself to reduce my working hours one day and have more time for all that other good stuff the article mentions. Shorter weeks could bring a lot of benefits with them to those who can enjoy them. Some problems I have with the article however:
1. Working less may well not result in getting more (or the same amount) done. The article mentions a correlation between shorter working hours and higher productivity. As always, correlation does not equal causation. Most likely those countries with shorter work weeks are developed countries which have higher output per capita than less developed ones not because working 40 hours a weeks is more productive than working 80, but that utilising a higher level of technology gives superior output.
2. The idea that because the Dutch apparently spend all their free time riding around on bikes means the brits would if given more free time is a joke. We'd spend it doing the things we enjoy (damaging our livers?), not suddenly become some imagined healthier happier version of ourselves.
All in all a pretty poor article I think as a result of the above isssues.
> The article mentions a correlation between shorter working hours and higher productivity. As always, correlation does not equal causation. Most likely those countries with shorter work weeks are developed countries which have higher output per capita than less developed ones not because working 40 hours a weeks is more productive than working 80, but that utilising a higher level of technology gives superior output.
The article is comparing the UK (long working hours, terrible productivity) with Germany (short working hours, very much better productivity).
It's unlikely that there's much difference in the technology available. And they both surely know about all the modern methods of organising a workplace.
I mostly agree with point 2, but
> We'd spend it doing the things we enjoy (damaging our livers?)
Maybe the reason so many british people drink too much is because they're working too much, and they're (mis)using alcohol to wind down.
Purely anecdotal I know, but since giving up my job in the city and going freelance I have indeed spent far less time drinking and far more time exercising.
A quick one after work was far too common. I buckled far too easily to peer pressure and conformity. After all it's the done thing to do right? A crap day at work is solved by a pint (or three) after? And a good day at work... well that could be considerably more ;)
The reduction in hours has allowed me to do activities which overall make me happier and less inclined to drink.
I now do a lot of running and bodyweight fitness. Drinking decreases my performance in those two activities and so I tend not to drink as I get far greater happiness from dropping a second in my minutes per mile than I do from having three pints during the week.
That compares data across the OECD, so fair enough this isn't comparing Papua New Guinea to the UK or similar. However, it mentions in the article the difference between Germany and Greece as examples of higher average hours and lower average productivity. I'd still tend to believe this isn't because the Greeks could get more done by working less but that Germans are tackling different work or using more technology in their work than the Greeks.
> Maybe the reason so many british people drink too much is because they're working too much, and they're (mis)using alcohol to wind down.
Maybe. It seems like we agree on this anyway. I was being slightly tongue in cheek here, not trying to suggest all the freed up hours would be spent in the pub :). I'll leave it at that.
i agree that working less should not always result in getting more done.
one of the potential benefits mentioned by the article is the climate change perspective. from that perspective, the whole point of working less is a mechanism to reduce the rate that stuff gets done.
the downsides of this would be:
1. less stuff gets done
2. on average people have less income
3. on average people have less income, and this hurts poor people far more than wealthy people
4. perhaps the economy doesn't grow, and we don't know how to run society that way
the upsides might be:
5. there's a reduction in negative side effects (both generation of pollution and rate of depletion of non-renewables and unsustainable depletion of renewables (fish stocks, timber, soil, ...))
6. we've got more time to do stuff that isn't work. hurray!
7. we've got more time to think carefully about what we're doing before we hit some hard limit
8. a lot of stuff that gets done is unhelpful, and now there's less of it
9. it's fairly obvious that we cannot keep growing the physical economy indefinitely, it might be a wise idea to try to learn how to run society in a different way before we're forced into collapse.
e.g. see the book "Prosperity without Growth: Economics for a Finite Planet" by Tim Jackson.
Until we have control over land prices via land value tax we will always work a full week.
Land prices are set by credit which will expand to fill all labour less food / heating costs.
Only when land is cheaper can we opt out of working 40 hours and this will see a general reduction in the average working week. Until then we are all banker bitches.
I changed my working arrangement to 80% recently, so now I work four 8-hour day weeks. I wholeheartedly recommend it if you can make it work.
I have wednesday off, so the week is divided into two-day stretches.
Not sure if I'm any more productive (maybe), but I'm a lot happier. I suspect some coworkers are going to follow my lead, now that the precedent has been set.
I never said it was for everyone, but I suspect people magnify the expected issues a lot.
Everyone knows I won't be here on wednesdays, so we try to arrange things so I'm not a bottleneck during that time. If some really important deadline shows up, I'll just work the one wednesday and take thursday off instead, it's not a big deal. I haven't needed to yet though.
Besides, assuming you're not on a really tiny team, if many parts of your project hinge on one person with no available backup, you have bigger problems related to project management.
This is nonsense, although it may depend on the kind of job you have. For most of us, we don't need to be there five days a week. You can plan around that.
Of course if you have five people in a team and everybody has a different day off, you can never get together, and that may be a problem. This is the same if you and your colleagues work many days/hours out of the office or at home.
Pretty much anything can be made to work if it's planned for and executed properly.
Our dev process required a lot of meetings and interaction. So in order to ensure clear blocks of working time, we used to set aside days as "no meeting days" Some people would take the opportunity to work from home on those days since it was guaranteed they wouldn't be pulled into a meeting. Once you know Sally, Jared and Kaitlyn won't be in on Tuesdays, you plan around it.
This happens where I work- one of my coworkers is here Monday - Thursday (10 hour days) but takes Friday off. He's the only one with knowledge of a lot of our legacy systems, so a lot of potential work doesn't happen on Fridays. I'd argue that more of us should learn what he knows to avoid "hit by a bus syndrome" but we don't have enough spare man hours to devote to that.
> The question is not whether or not you're as productive, but rather, are you more than 80% as productive as you were before.
Absolutely, that was what I was trying to convey (productivity per hour rather than total productivity) but it was poorly worded. A lot of discussion around shortening the work week focuses on the latter. While there may be cases where that's true, I think focusing the discussion on that is wrong because it assumes that there has to be an economic argument for making the change. For me, people having more free time is a positive in itself that society should probably optimise more for.
I am certainly not less productive per hour worked. I might be more productive, I don't know, but that should not be the only reason we contemplate such a change.
Most likely, but taking into consideration taxes the decrease could be smaller.
Some countries have progressive income tax. So it depends on salary, but it could be that by working 20% less you receive only 15% less.
We have a progressive income tax here. The 20% comes from the part of my salary that gets the higher tax bracket. So in fact the decrease in amount I get paid is quite a bit less than 20%.
I also suggested this change at the yearly salary interview during which I negotiated a 10% raise. So really the amount I get paid each month didn't change all that much.
You're assuming a fixed workload-based salary. If we're talking about a salary that has a big variable component (commissions, fees, bonuses), the cut may have been smaller.
I'd be happy to take a 20% pay cut for a 4-day work week at some point in my life. I have a semi-retired relative who does just that.
As it is now, I'm vocal at reviews that I'll take more days off per year in lieu of direct salary increase -- an idea which seems to throw people off and hasn't been seriously entertained. At some point, I'll make enough annually, that I'll simply start taking days off without pay, which is something payroll seems to really hate for some reason when it concerns salaried folks.
Corporate pay/work expectations are really odd sometimes.
> ...I'll simply start taking days off without pay, which is something payroll seems to really hate for some reason when it concerns salaried folks.
At the risk of sounding too glib, the short answer to why they hate it is it creates work for them. In the US, all of the major payroll processing services are geared towards either hourly or salaried templates. Most companies' payroll procedures are built around the core assumption that if you are salaried, then it is X salary divided across N weeks/months/your-pay-period. If you take days off without pay, changing the salary, someone in payroll has to manually key in the delta off your normal pay period processing numbers. That sometimes has downstream ramifications upon unemployment insurance reporting and remittance, for larger companies there are other regulatory-originated reporting that this can impact, and put in common issues like tax liens and family court-mandated levies, just for starters, and it gets hairy. Generally payroll processing is still built around a set of assumptions that are at odds with emerging knowledge workforce trends; the trends can be accommodated, but it's a hassle.
If you have a good enough relationship with your manager, then you are far better off negotiating a sub-rosa agreement to (in your example) work Wednesday this week and take off a couple days next week (or leave a couple hours earlier each day), and net out to zero change in time worked over a short (sub-month) period and leaving payroll none the wiser to any change in time worked, than making the payroll department perform an exception-based processing of your payroll.
US payroll processing trivia to illustrate how rigid payroll processing systems are today for the small business, and for flexible work arrangements: if you are a really small, micro-sized business, like say an Etsy seller with a couple full-time employees, set up as your own LLC or whatever, you will run payroll, except unlike larger businesses you will frequently want to know how much to pay yourself (after paying off all employees and vendors) including all employER-side tax liabilities, and not just the employEE-side disbursement. All of the top-ten payroll processors have no capability to compute that for you; you have to iterate to an approximation. In other words, if you know you can afford to pay yourself only $10K total this month, payroll processors force you to key in a employEE net pay number then they spit out the gross including the employER side, and only then do you see if you are over/under the $10K amount. There is no feature that lets a small business owner say, this pay period, I can only afford at most $X cash out the door total including all tax liabilities for so-and-so employee, iterate and solve for me what the best result is to achieve that.
US payroll processing can get really complex, really fast even for small businesses, so I can imagine what a nightmare it must be for the designers and developers of those systems. However, I believe there is still plenty of room for someone to create a disruptive service that caters to and appeals to small businesses.
If you are a salaried employee, the only thing payroll should need to know is whether or not you worked at all during the week. If the answer is yes, you get paid your full salary. If it is no, you get paid your full salary if you have a vacation week left. If it is no, and you have no vacation weeks left, you don't get paid. Simple.
If taking a day off during a working week causes them additional effort, it is only because they are grossly abusing the definition of salaried employee the entire remainder of the year.
If they want to handle employees as though they were hourly, they could just stop lying about their people being salaried exempt employees.
If you are salaried, and your manager is fine with you taking Fridays off, payroll does not need to know. If a deadline approaches, and you need to work Saturday and Sunday, too, payroll does not need to know. Salaried workers are supposed to be paid for getting their work done, and not just for punching the clock.
It seems as though many employers are abusing the legal definitions in order to bend labor laws.
> It seems as though many employers are abusing the legal definitions in order to bend labor laws.
This is absolutely what is going on in many US companies, no question. That's a separate can of worms for the political and legislative arenas, and not one that individual salaried employees can safely change on their own within their company. Discussions about this also tend to drag in meta-discussions about compensation, project management, management accounting, work environments, etc., adding more worms to the can, and even more cans of worms to the original can. It's messy.
What you outlined is definitely what should happen. The jobs situation is bad enough for many fields outside of our own, and even many areas within our own field, that flagrant flouting of salaried exempt labor laws is allowed by regulators, and encouraged by shareholders. Longer-term, this only hurts the companies, because they're receiving imperfect signaling of actual required effort, distorting all future projections; competitive advantage accrues to those companies that accurately and precisely calibrate their projections to known required effort. Change will come slowly and haphazardly, if only from the ongoing population growth slowdown, hopefully.
That's because they know they should just tell you that they don't need to pay you less–you're a salaried employee. Salaried employees get paid a fixed salary to get a job done. The part that employers enjoy in the arrangement is you being able to work more hours to get something done and your compensation remains a fixed cost. What they don't like to talk about is the other side of the coin: It doesn't matter how much time it doesn't take either. So accordingly you should, in theory, be able to work less days if you get your job done in those days.
But the reality is that many managers and employers only support the part that benefits them. Even many of the ones that are supportive of someone taking a Friday off every other week feel that they're doing you a favor or giving you a "perk". At the end of the day your manager has to support it (and if necessary continue believing they're doing you a favor) because they can find a way to shit-can you if you start pushing boundaries they're not comfortable with (in the US).
I have done this before, but arranged my days off to be alternating Mondays and Fridays so that every two weeks I'd get a four day weekend. My bosses were very generous with my schedule. :-)
Honestly this seems like the ideal scenario. Full pay, likely no argument from superiors about the amount of work you'd accomplish, and the ability to take long weekend trips without wasting a day or two of PTO.
I only see a few possible downsides:
- Someone expecting you to be in the office and you're not, particularly if they're not familiar with your schedule.
- For developers the same issues with 60+ work weeks often come up in hours 7-10 of a single working day. Off-campus lunch for a full hour (or more) would probably be important, which pushes your full day to 11+ hours.
- Using 10 hours of PTO when you take a day off, but I guess that's what you get for getting the 4-day weekends :)
This is the schedule my father has, working as a mechanic in a power plant. It's pretty solid.
The only (kind of ironic) downside is that holiday weeks are kind of sucky. The holiday day only pays 8 hours, so he ends up having to still work four eight hour days those weeks.
Working 3 10-hour days during a week and 6 5-hour days during a week seems equally doable, but I think I would get more complex, brainy problems solved with the latter, and more simpleminded grunt work done with the former.
It's not working less, some of us need 100% of our pay to get by and can't afford a 20% cut for less work (the stress of having less money > the stress caused by working more)
Anecdotal evidence, I used to to that as a CSR at PayPal years ago. After a "normal" day of height hours of calls or emails you had two more hours of emails.
My brain was fried and I was glad when the policy was canceled.
I loved the extra day though (which was Monday or Wednesday) and as a software engineer I would love to pull it off, to rest or work on my own thing, but I would gladly take a pay cut than work 10 hours a day constantly.
I think I conflated your current role as a software engineer with your previous job as a CSR. Besides poor reading comprehension on my part I think assuming a position like CSR is hourly and (typically?) only salaried employees answer emails after they go home contributed to that. Sorry.
I do this every once in a while, and my most productive hours tend to be... the two hours left in my day after everybody else has gone home. The office is silent and there are no distractions or emails. I can just get "in the zone". Maybe I should start doing this more often...
Can't speak for GP, but what I did was move my schedule up to 9:30-6:00 or so, let my arrival date float between 9:30 and 10:00 so I could come in pretty much when I felt like it.
After awhile my workload dropped practically to zero, and I started leaving at 5. Kept it up even when there was a workload, and found that completion times didn't suffer.
Don't propose anything. Just start shifting your schedule around and see if people complain. Do it slowly and people won't notice, or if they do, won't care.
In the corporate world, you don't ask for permission, only forgiveness. The word they use for it is 'initiative'.
I should also note that management is likely to see this not as a wayward employee bucking the rules, but as someone doing what he needs to under the circumstances to make himself happy. So long as it's not egregious and work quality stays ultra-sharp, everybody involved is going to just work around your preferences. They know you'll be much less likely to leave if you're happy with your situation, the damage you cause by leaving is far worse than the damage caused by bucking the standards.
Around the time I was doing this, I got a new manager. I was wholly unwilling to reorient my schedule around his expectations, but I would stay until he left for the first few weeks. One day I followed him out, even though it was at least an hour before I "should" have been leaving. I'd also taken an hour-plus long lunch that day. I told him I usually leave at 5, but I was staying late in case he had any questions for me. He was like, "even though you took a long lunch??" and I just nodded, and followed him out. He didn't mention it again, until I started talking about taking another job.
There is a space in between political expectations, business needs, and personal wishes at any job that is ripe for exploration and exploitation. One can iterate towards their ideal work environment and conditions at any job where their performance is stellar. Just keep the business needs and political expectations in mind and you can practically get away with murder.
You propose spend 20% less time working for 20% less pay. He'll probably not accept it too, and if he accepts you'll probably not progress inside that company anymore. But he very probably won't get annoyed either.
I did the same for several years at my last job (although with Friday off so I had long weekends). It was great and I'd encourage anyone to try it if they can.
I definitely felt like it made me more productive per hour worked. A shorter week added a little bit of time pressure that helped me stay focused, and I'd often finish something in four days that might otherwise have stretched to five.
Total output was probably a little lower, but I took an equivalent pay cut when I reduced my hours.
I was only able to make that arrangement after I'd been at the job for a while. When I changed jobs, I went back to five days a week, and I'm definitely missing the long weekends.
Did your salary also drop to 80%? Did other benefits which legally require a 'full time' schedule go away?
The worst possible scenario would be workers switching to shorter work weeks, accepting pay cuts and loss of benefits, and proceeding to be more productive for their employer. I mean, unscrupulous employers would love it, but for society it would be terrible.
Yes, sort of. I approached this during the yearly salary interview. I negotiated a 10% raise, and a change in work schedule to 80%. So I'm getting paid 0.8*base_pay, but I didn't just take sudden a 20% cut between months.
> Did other benefits which legally require a 'full time' schedule go away?
I checked with my union (union membership is mandatory here but they really only negotiate minimum vacation days and minimum salary for a given profession/class, neither of which affects me since I have negotiated above and beyond what they have - it's a very different system than US people are probably familiar with) and according to them, there should be no change to any benefits or legal rights. Things like the fixed christmas bonus will be paid to 80%.
> The worst possible scenario would be workers switching to shorter work weeks, accepting pay cuts and loss of benefits, and proceeding to be more productive for their employer. I mean, unscrupulous employers would love it, but for society it would be terrible.
I'd rather not work more hours than I really want because my employer might benefit from me doing what I want to. If this concerns you, you can just keep your productivity per hour to the same level as it was before. I have no idea if I'm actually more productive, and I don't really care. What matters to me is I now have an extra day every week to do something that I actually want to be doing, rather than working for someone else.
Put another way, if you feel like your skills are undervalued, talk to your employer about a raise. This holds regardless of whether your work proportion is 100% or 80%.
I figured it'd be nice to only ever have two-day work stretches. I didn't put much thought into it, just decided to try it and I've been happy with it so far. I feel a lot more energetic on thursdays and fridays now.
The climate change argument is a terrible one. Lower consumption? In the same article it argues that the work would be spread over more people. So, using the article's logic, same amount of productivity, more people providing it. For 50 hours of work, you deploy 2 people, thus causing 2 units of fixed costs to be incurred for the same productivity. Same variable costs, twice the fixed cost.
Mythical man month actually says the opposite, because even if longer hours have diminishing returns, the organizational overhead from adding people to the team is worse. Maybe the descrepency here is short view (a couple years to build a startup) vs long view (mature organization over an entire business cycle)
"From a business point of view, long hours by programmers are a key to profitability. Suppose that a programmer needs to spend 25 hours per week keeping current with new technology, getting coordinated with other programmers, contributing to documentation and thought leadership pieces, and comprehending the structures of the systems being extended. Under this assumption, a programmer who works 55 hours per week will produce twice as much code as one who works 40 hours per week. In The Mythical Man-Month, the only great book ever written on software engineering, Fred Brooks concludes that no software product should be designed by more than two people. He argues that a program designed by more than two people might be more complete but it will never be easy to understand because it will not be as consistent as something designed by fewer people. This means that if you want to follow the best practices of the industry in terms of design and architecture, the only way to improve speed to market is to have the same people working longer hours. Finally there is the common sense notion that the smaller the team the less management overhead. A product is going to get out the door much faster if it is built by 4 people working 70-hour weeks (180 productive programmer-hours per week, after subtracting for 25 hours of coordination and structure comprehension time) than if by 12 people working 40-hour weeks (the same net of 180 hours per week). The 12-person team will inevitably require additional managers and all-day meetings to stay coordinated.
It's the unit size that matters. Mythical man month said the ideal basic organization for delivering work output is modeled after a surgical team. If you model after traditional military units, the infantry squad is the equivalent to that team.
Under the mythical man month org structure, the atomic unit of work capacity is that surgical team. You can't do more surgery by putting two more surgeons in the OR. But you can add new teams and get more output. I think the analogy works in the military context as well -- a general doesn't ask for <X> more individual soldiers, he asks for more battalions/regiments/divisions.
Let's remember the context though: That books was about 1960's IBM culture, of legendary stiffness and bureucracy even among contemporary office workplaces, in a project working on a revolutionary mainframe operating system core with innumerable "firsts", in assembly language, at a time where recruits couldn't be expected to have much under their belts.
That working fewer hours ==> increased productivity is also a mathematical tautology. Productivity being a function of output and hours, with output generally being somewhat sticky as hours change.
I think your definition of productivity is off a bit. You need to account for "effective" productivity. My hours might be 40+ but how many of those are truly focused and productive?
Hence, working less time with (theoretically) better focus and reduced stress/strain would be more productive.
It's not my definition, but an econo-bs definition that involves aggregating $ value output, hours worked. So any study that discusses productivity will always find, at least over any short period, that hours are inverse to productivity as they cannot move in perfect lockstep. However, as an individual, your experience may (and probably should) vary quite a bit from what you might predict in the aggregate!
My circle of friends are what you call professionals. They spend an awful lot of time at work, most of it on looking like they're working.
There's a fair number of jobs where the work itself is not hard or time consuming, but where a culture has grown where everyone needs to justify their position. This skew incentives; if you're a junior, you end up doing a bunch of little things that can pass as a laundry list of things someone had to do. If you're senior, you can gun for getting credit for grandiose sounding things like "strategy". Junior people end up in meetings all day, which if you're senior, you end up calling everyone into. Everyone sits around until late to demonstrate worth.
A lot of these jobs could be done remotely, on any schedule with a sensible number of hours, by just about anyone who can read and write. But because of the culture, they end up being done by the only people who have 100 hours a week, namely singles in their 20s who are just out of university, in some very expensive location. These people then have families to feed and get stuck propagating the same sick culture.
I don't see the law as providing a solution. Nobody enforces the 48 hour contract in Britain. When did you last hear about a City sweatshop being liberated by the police?
The way to change the culture is actually, believe it or not, startups. Yes working hours can be horrible in startups. But in an environment where a lot of firms are startups, there will be more variation in the working culture. Certain firms are already showing the way forward with flexible hours, remote work, and other family friendly practices, without compromising on quality.
>They spend an awful lot of time at work, most of it on looking like they're working.
Guilty. If I could switch to a 4 day work week, I'd get the same amount done, but spend a bit less time on Hacker News and other distractions. Hell, let me work a 2 day week and I'd cut out all distractions to finish what was needed.
I will get the same amount of work done for the same amount of salary, given that my employer has obviously already agreed that it is a fair amount to be compensated for the level and quality of my output.
I signed up for a gym that apparently went on an initiative to improve its employee culture. The gym is really nice, not as good as Equinox in Palo Alto, but close enough. So one of the initiatives was to close the gym during holiday seasons so that staff could enjoy vacations schedules just like everyone else. Lo and behold, they closed the gym between December 20 and January 5th. Just when I was planning to catch up on things. They can count on my cancellation. What I'm saying - do you want to live in a world that is functioning 80% of time?
We should respect other people's time off if we want others to respect our time off. Is it really so hard to find some other way to exercise for a month?
Why not close supermarkets out of respect for labor unions as well, for 2 weeks. I think the solution lies somewhere else - such as automating humans out of retail and services to the extent possible. For instance, speaking of gym, I would keep the facility open staffed just with with security and reception. Shut down non-core functions: new member office, group sessions, cafe etc.
If you need your business to be open for the same amount of time, reducing maximum hours to 3/4 means increasing worker count to 4/3.
Judging by the abysmal labor participation rate and unemployment stats in the US, this is easily done. Per-worker overhead costs would force an increase in the labor budget for most companies, though.
As many businesses have been ruthlessly slashing that budget category for a while, that is likely to prompt a lot of bitching and moaning from company management--even from businesses that depend on consumers being able to afford their products.
It's just a scheduling problem. If a business elects to be open longer than 6 hours per weekday, it will need to have some workers work at different times than others. But I do recall visiting the government license office once on my lunch break, only to discover that most of the workers there were also out to lunch, and took more time out of the middle of the day than I wanted to.
So, anecdotally, whether or not the world functions when you need it to function depends more on how much the business cares about serving its customers than the number of hours its workers are on-site every day.
One irony here is that of the two gyms I belong to, the cheap one has longer hours on holidays and Fridays.
I originally added the cheap one because it's just 4 minutes from my house, ruining my ability to flake out on the basis that "I don't have time to do X before they close".
I cut my hours down to around 35 a year ago. The reduced stress made me more productive than when I was working 40 hours. If I thought I could get away with chopping it down to 15 hours I would. I don't have a high enough workload to get into flow state most days. Chopping the week down would both make me more productive and allow me to enjoy work even more. But actual tasks don't come in very frequently.
I've worked the standard 40-? hr/week programming jobs for years and about a year ago I took on a project where I was the only developer and before I took the job I made the decision to work about 20 hours a week. Turns out that 20 wasn't quite enough so I ended up doing 25-30.
Looking back I think 25-30 hours is about as efficient as I could have been as I gave the best hours of my day. But when it came to the last month before the release I found I did have to give some more time to get it done on time. Short bursts of working long hours seem to be effective for me, but I also noticed that I needed to take some time off after the project.
It's been a great year and I've really enjoyed the other things I was able to do with my time. If you are able it's worth considering even if you take a little less pay.
I worked at 50% capacity for some years. It was just great until I chose to want more money for the time being and returned to 70% capacity. That was just great, too, until I realized that I was as productive as a full-time guy without the full-time pay so I eventually went back full-time but trying to keep my output roughly on the same level as I had been getting good reviews all the time.
However, last year I got tired of the full hours and a bit depressed because of lots of factors that prevented me from getting things done, and after one realisation I took a month off. Coming back to work I figured I shall be going with working full hours for three months and then taking a month off again. So that comes to three months of spare time and nine months of work annually.
The realisation was about working patterns. For a programmer like me, the best productivity comes in bursts so I'd happily do three ~12-hour days and keep two days off as opposed to working the official 7.5 hours (in my country) every day. This has always been so, even as a kid. I could work on something really intensively for a few days and then I needed to do something completely different. The newest realization was that it works on longer timescale too. I can work three months and do my absolute best, and then relax and have time for my own things.
This sort of a contract――relax pattern is quite reminiscent to life and nature itself. I feel much at home between the pushes and pulls. I'll see how the first year will turn out to be.
Over the years I've also realised that staying productive is mostly just about conserving these important productivity patterns.
A lot of what happens at work eats away from these patterns but if you can keep them mostly intact then you'll get productivity by default. That is, assuming that you love programming. Hint: if you're known to occasionally spend hours on hacking something at work at an intensity where nobody can pull you away from it, it's a good sign that you love programming.
This sounds amazing and I'm happy you've found a solution that works for you. Unfortunately in my experience this scenario is basically impossible for 98% of people in the US - I assume when you say 'my country' that you are not from the US?
I work in Europe but I'm actually employed by a very much US company. Practically my whole team is in the USA and other than receiving salary locally I have surprisingly little to do with the European subsidiary. I also work from home a lot because working at the office would be effectively telecommuting, too. Decisions such as my unpaid time off come from the US.
My employer is not a particularly conservative company and it helps that my boss is great and if he has to cross-check something with his boss, his boss is great too. And it probably helps to have a somewhat senior position (next milestone: ten years) and having made my mark years ago.
But most importantly: getting your shit done. If you can get your shit done you're in a much better position in getting everyone to agree on more flexibility into your job because companies need to get shit done.
Wise employers recognize that it's of everyone's benefit, including theirs, to keep productive employees in a loose leash with more freedom of choice rather than impose binary requirements on how and when to do the work. If my employer wasn't wise like this some other company would be enjoying the fruits of my productivity as I would've left them years ago.
Even if you work at the very best companies and love your work, work is still always work and it will at some point become too much, meaningless, source of frustration, or any combination of those.
Yes! This is exactly what I've been thinking for a while as well; I've been sort of badly approximating it by saving up money and taking a while off between jobs.
Next time you're negotiating a salary and they aren't willing to match what you want, don't walk away yet but offer to take the salary with reduced hours in proportion to how much you're missing. Taking an exaggerated example: if you want 150K and they're only willing to pay 100K, suggest to take 100K with 2/3 of the hours. You have nothing to lose but potentially lots to gain.
How do you manage these? I'm most productive that way too. But the trouble is I'll keep going longer than I should, and then I just get tired and unproductive and not sensible enough to rest.
Are there signs you look for to leave it on a high note, or do you use hard time limits?
My old colleage Mike Rowe wisely said "Always leave it compiling". That way you could go home thinking, that was probably the right fix. Then the next day you could go in and see that it wasn't, and pick up where you left off.
I kind of keep a (mostly mental) tally of the week's hours and when I've done a full week +/- N hours, I've done enough. But because of N it's a bit hazy sometimes.
If I can finish something in a day what could've easily taken three days, I'll probably end the week a bit earlier. And if I get fixated on doing some "simple thing" that ends up taking a lot longer, then I allow myself to work extra to get that squashed. It's important keep your conscience fair so that you know you can mentally match the hours with results produced.
Programming isn't strictly about wallclock hours but wallclock hours are a good starting point for measuring a fair effort because your pay is likely to be based on the wallclock too. (Such as 22 days * 8 hours or so.) But some hours are indeed "thick" and some hours are "lean" and you need to balance those somehow. Otherwise you'll be working way too much or way too little in relation to what you are paid. If you only look at the chronographic units you will realize that you can't do so. If I'm walking in the woods and figure out how to architect some component, is that work or not? And how is it work if I sit at my desk for half a day and get nothing done? That's what you have to live with as a programmer and striking the balance is delicate business, but luckily it's enough that you only need to find the balance in the average.
Then again, it's all about shit. As long as you get shit done the hours don't matter. And as long as you don't work too many hours to feel shitty yourself, the scheme is sustainable. That's the ultimate balance.
This is exactly my goal as well. I'm currently working a full time job, moonlighting contract jobs on evenings/weekends, with the goal to save enough money to cover my expenses for 6 months. After that I plan to go into full time consulting and specifically target shorter term contracts and take off blocks of time in between. I've always seemed to work best in spurts and software development (new projects anyway) are a good industry for this type of environment.
> Productivity – output per working hour – improves with shorter hours.
Yes, but total output = number of hours x productivity. So even while productivity diminishes, your total output can increase if you increase number of hours.
Most conversations about working fewer hours are really conversations about how much the personal resources of workers can be drawn upon without providing extra pay before there are negative productivity consequences. This article ties in directly with some ideas I've been exploring recently [0] involving personal resources of workers and time/productivity management of workers [1][2]. The concepts of worker personal resource management and worker time management are largely foreign to the places I've worked, much to their detriment. Instead, the strategy could be described as "colloquial management", a mishmash of half-remembered concepts from business school or worse, the playground.
If a worker can quantify roughly how much time and energy each task at work will take up, a clearer picture of how to be the most productive in the least amount of time will reveal itself. Employers perpetually hide in the ambiguity of the employees' time and effort, hoping to make a profit out of asking for too much and motivate their workforce by periodically throwing a tiny bone to the most masochistic over-achiever. A tabulated rubric describing to the employer exactly how much time is spent on each task and how much mental and physical energy the task takes relative to the worker's actual capacity for these energies would show exactly how wasteful it is to over-work people.
Longer hours deplete worker mental energy and physical energy resources whether or not there is more work being done. Once these resources are depleted, worker efficiency drops precipitously. Additionally, periodically depleting these resources leads to worker burnout. I also suspect that workers resent longer hours whether or not they are necessary, leading to weakened ability to refill their mental energy reservoir due to poorer mental health in general.
I'm annoyed that it said the "Most Voted" before I even had the chance to look at the options. That immediately tainted my ability for an unbiased response.
252 comments
[ 3.4 ms ] story [ 284 ms ] thread"Demand is relentlessly rising. Our capacity is not keeping pace. The traditional solution to higher demand has been to invest more time. Unfortunately, time is finite, and most of us have no hours left to invest. Energy, however, can be systematically expanded --- and it can also be regularly renewed. To operate at our best, we need four energy sources: physical (quantity), emotional (quality), mental (focus), and the energy of the human spirit (purpose). This talk will focus on the role of energy in fueling sustainable high performance, and in motivating others."
...which relates to the work he does at the Energy Project - http://theenergyproject.com/
We don't 'love' cycling it's just highly ingrained in our culture and it's way cheaper than owning a car, especially with our awesome public transport.
>But what about tackling the issue at its roots? What if everyone had a shorter working week? We would be healthier and happier, and society would be less unequal and more sustainable.
Is it? How is this article different from pure speculation?
No-one in Denmark/Germany is a slacker, btw. They're just really productive when they're actually at work.
This holds true in an industrial context where there is a large pool of workers, the work is low skilled and unions are weak. A workers ability to provide time is the only concern that the employer has. Where I live, in the North of England, this factory mentality still casts a long shadow over working conditions and practice.
I think a 40 hour week is way too long to actually have a balanced life and I've consistently burnt-out where the pressure to work 50/60 hours a week is strong.
I'm not surprised that DavCam is wanting to keep the 48-hour opt-out - if you are an investor / owner of capital, do you care about the long term well being of the people making effort to give a return on your capital over a short term (5 years) when people are interchangeable? You simply want to increase the return on your investment.
Somebody needs to check the parallel-universe France that has a longer workweek and check its unemployment rate.
I think that this can be achieved with a softer approach. Imagine that when you sign up for a job, you select how many days per week do you want to work, from 3 to 6, with proportionate wage scale. That you can select what hours do you want to work. That it's easy to change this arrangement while you're already working.
Now, why is this fantasy not a reality? Not because of laws; laws allow this. But:
1) These creative arrangements require non-standard agreements, and a lot of additional bureaucracy, because in a lot of countries, all the bureaucracy machinery allows it, but is really not optimized for use-cases like that.
This can be solved through careful policy work, removing necessary paperwork, streamlining processes, etc.
2) Economies of scale. Having a full-time 40h/week employee that gets X money as salary is cheaper than having 2 half-time 20h/week employees that get X/2 money because of management overhead, cost of their office spaces and other stuff like that.
This would be solved if 20h/week employees would understand this and get X/2-Y money. Also, a lot of these scale issues are being solved by modern world anyway, because we're learning to telecommute, work together in more effective ways, automate management tasks, etc.
3) Culture.
And I think this is the most important one. It's not in the laws, it's in the people's heads. We need to convince people that one person wants to dedicate work 60 hours per week, spend free time that's left on professional education and succeed in his career, and another is quite OK to work for 20 hours per week, get less promotions, learn less new stuff and earn less money, and spend all his free time with his kids. We need to stop labeling the first of these persons as "successful" and second one as a "failure": it's OK to be both of them. And they need to be able to work in the same office, on the same project, fully understanding difference in each other's views and being mutually acceptful.
I don't know how to do that, but it seems that this cultural change is already slowly happening. Still, advancing it would bring the real change much faster and more effectively than writing new laws.
> "Productivity – output per working hour – improves with shorter hours."
And why should the employer get all the benefit from this? I think a lot of people would love to work fewer hours, be more productive those hours, if they could retain the same salary.
I would love to, at least, but can't afford reduced pay.
Thankfully, we don't analytically decide who takes the benefits — labor market is working pretty well at figuring this out.
The more I work from home, the greater productivity gains I have over everyone else that remains at the office. It's satisfying.
And I get paid more than them by at least 40%. Go figure.
I'm genuinely curious to know how we would know whether the labor market is working well at figuring this out or not.
It's not about judging employees from a moral standpoint, but getting the most skill and involvement going into your project/company. So, one of the questions would be: does 20h/wk + 20h/wk = 40h/wk skills+involvement, ie. is it linear? Wouldn't 20h/wk jobs be limited to inherently part-time, low importance tasks--which means you got to have plenty of funds to staff for them in the 1st place?
Interesting question. Not necessarily; as a lead developer, I just had an experience of a talented freelancer joining my project for 20 hours per week and helping with issues that we delegated to him so we can fit in the deadline. On one hand, _usually_, 9 women don't make 1 baby in 1 month; on the other hand, in this particular case the freelancer new the technology really well, and we delegated him with special issues that required less knowledge of our whole project and more knowledge of the tech itself.
So — yes, 20h/week limitation creates some problems, when you're working in the 40h/week team, but it's not the end of the world.
Anyway, that's a kind of special situation, essentially unrelated to the employee working 20h/wk to take care of their family.
It would seem to me that 2 people working 20h/wk offers some significant advantages over one person working 40h/wk.
Firstly, it allows for fail-over; when one person is unable to work (due to holiday or illness, for example) the other might be able to handle 40h/wk for a short period to cover. If one person leaves the company suddenly, it allows for continuity of knowledge while a third person is hired and trained.
Secondly, it allows for variable output; two people can "burst" up to 80h/wk in response to workload, whereas one person would find that very stressful.
Thirdly, multiple people bring multiple points of view, increasing the chances of serendipitous ideas and solutions, and increasing the potential benefit of using people's special skills or experience. Basically, the company is renting two brains for the price of one.
There are some downsides too: The management overhead is higher (equipment, legal, payroll, etc...) and things that were simple when done by a single person are now more complex since there needs to be coordination between multiple people.
To use an incredibly bad analogy: It's like moving from a monolithic "big iron" server to a pair or farm of smaller ones. There are many advantages, but it means it's now a distributed system with all the problems that can bring.
The problems aren't insoluble and don't limit 20h/wk employees to low-importance tasks: Many open source and volunteer projects function perfectly well with many, small, variable inputs from their contributors, many of which will be high-importance.
The thing is that, as you noted yourself, the analogy doesn't hold, for people are not AWS servers waiting for charge or failovers. If they chose to work 20h/wk, it's presumably to spend their time for other pursuits, eg. family, and they often won't be able to or won't agree to work more when their employer need it, perhaps unless it is planned well in advance (eg. Black Friday period).
> Basically, the company is renting two brains for the price of one.
Or, as I questioned, you might got two partly focused and perhaps less skilled people thinking about your problem, instead of someone more skilled totally focusing on it. As was brought in another comment, if you got two freelancers, then yeah, you could pick two brains, but if you have two family guys, not so much.
I also don't think it's necessarily true that two part-time people would be less skilled or less focussed on work. It's the very point of the original article that working fewer hours can increase the quality and focus of the work done during that shorter period.
I've worked with many talented and exceptional "family guys" (and family women) who were skilled and totally focussed during working hours. I haven't noticed a correlation between people's priorities outside working hours and ability to do good work.
To me, it depends on how you cut the hours, and to what extent. I'm all for working shorter days, eg. 6-8h, 4-5 days a week; however, the more you get close to half-time or below, the more difficult it becomes to stay fully focused and as motivated as a (more) full-time employee. This is admittedly less of a concern if the person uses their free-time on related projects (eg. writing open-source stuff).
Also laws are the way to prevent a race to the bottom. If it's legal to work longer hours people will, and everyone else will do so to compete with them. Compare OHSA, see http://slatestarcodex.com/2014/07/30/meditations-on-moloch/ .
It's very hard to measure human productivity unfortunately. It's much easier to measure the cost of an employee working less hours for the same salary.
But management hasn't entirely caught up with the idea that jobs are no longer about clock punching - and longer clock times can mean less real worker value.
This is partly about power dynamics in the workplace. In many corporations control of time and personal freedom are perks that are only available as you move up the hierarchy. Dysfunctional cultures are much more interested in explicit displays of limited freedom for the worker bees than in true increases in productivity.
Oh, is that why almost everyone earns minimum wage?
I think it's fair to assume companies will do anything for increased productivity. That has nothing to do with wages.
Categorically false. I'd wager 90%+ of the (American) readers here are exempt FTEs, meaning they are paid a salary which is based on calendar days/weeks/months/year, not hours worked.
Not true. What about education?
Over the years, the federal government has added more jobs to the exempt employee list. This means we get things like fast food store managers making $26K/yr putting in 60 hour weeks. There has been a push to change the minimum salary to $50K/yr for exempt employees, but employers have successfully delayed the implementation of this till late 2016.
Ideally, the US needs to rewrite the Fair Labour Standards Act to be more in line with the EU working time directive which limits the working time to an average of 48 hours over a period of several weeks. This allows overtime to be used in bursts, but not chronically.
That's not true.
http://web.stanford.edu/~leinav/pubs/RESTAT2003.pdf
Page 835. Total average of seatbelt usage, before law: 31%, after law: 48%, in 1998: 65%.
I think you might be confused by the 1998 number. That year came after the after law percentage. Meaning that enforcement immediately after the law also worked.
Your assumptions are without standing.
[0] http://www-nrd.nhtsa.dot.gov/Pubs/811875.pdf
This is one of those sneaky tricks advocates for government intervention use (or fall victim to). To prove the efficacy of OSHA, for example, proponents will show a chart of workplace fatalities or accidents where there are a few or only one data points before the law and then show some spectacular trend that follows after the law was passed. In reality when you go back many more years it is clear the law had little to do with the trend as workplace safety had been increasing for years prior to the law.
Not at all. For gay marriage or pot legalization, large shifts in public opinion have preceded changes to laws.
If it's legal to work longer hours people will, and everyone else will do so to compete with them.
The Moloch post is excellent, but it doesn't really apply here. Productivity isn't a zero sum game; unless you're in a dysfunctional stack ranking environment like Microsoft used to have, being more productive doesn't hurt your coworkers.
And for tech workers in particular, it's impossible to prevent you from working "off the clock" in your spare time. Yet people generally don't, probably because as others have noted just adding hours doesn't actually make you more productive.
You would also need an executive order to change the way that federal contracts are handled. Currently, huge numbers of salaried professionals employed by contractor companies have to punch the clock as though they were wage-earners in order for the company to get paid for their work.
If you don't log X hours during a given week, your salary for that week may be docked by N/X. If you log more than X, you are not necessarily paid any more for overtime. The contractor-employer could set X to be 40, or 45, or 50--whatever it wants.
If an executive order said that no individual could work more than 30 hours total in any calendar week on any combination of federal contracts, unless that person is paid an additional 10% of their normal weekly salary for each hour in excess of 30 (aka triple-time OT), while the company still gets paid the same rate, then lo, nearly everyone in the military-industrial complex would suddenly have a 30-hour work week.
As it is now, the contracting arrangements dance around the fuzzy edges of labor law, to the detriment of the workers and to the benefit of their employers, and possibly also to the benefit of several additional layers of middlemen. Changing the law is meaningless if you can't enforce it.
We tried asking nicely; employers were abusive arseholes. This is why we can't have nice things.
Without law we see huge rich multinationals forcing people to stay at work but "clocking off" (and thus not getting paid) when things are quiet; or asking for very long hours without sensible overtime.
That's a bit of a "trickle down economics" argument. Depending on corporations and owners to offer an option is never going to be as effective as passing a requirement.
As long as you only care about "effectiveness" of the conversion to smaller working hours — yes. But my point is that we should care about creating an environment where people are actually free to choose how much are they supposed to work.
In other words, you argue of how effective we can be in achieving our goal, while I suggest redefining the goal itself.
You'd probably end up with nearly equal productivity for office staff, and you'd generate more jobs for shift based work, as you would need 30% more workers to cover a 5-day period.
This was one of the drivers of the 40-hour workweek -- previously, 12 hour days + saturday work were considered the norm.
Meaning, if you are applying for a job that 100 other people are also applying for, you don't get to make these kinds of demands. Whoever is hiring you will simply pass you over.
However if you happen to be working a position requiring skill with a labor shortage (they are having a hard time finding someone qualified to fill the position) then you definitely could be in a position to negotiate for these things.
I think this is why people would be inclined to making it law, there are a lot of jobs where the workers wouldn't have the leverage to affect this kind of change.
I think one of the problems is that some people in powerful positions in companies want to do long hours themselves, so expect those under them to do the same. They see someone putting in long hours as hard-working and diligent, even though in reality they are probably being very inefficient and producing shoddy work.
"what" you ask? take a serious look at your inbox.
If you fail, it is likely because it wasn't as bullshit as you thought. The cogs may be sexy and obviously doing work, but the grease turns out to be vital too. But my "if" isn't for mere rhetoric... you may well succeed, because bullshit does build up too. The only way to find out is to try. I've had it go both ways.
1. Working less may well not result in getting more (or the same amount) done. The article mentions a correlation between shorter working hours and higher productivity. As always, correlation does not equal causation. Most likely those countries with shorter work weeks are developed countries which have higher output per capita than less developed ones not because working 40 hours a weeks is more productive than working 80, but that utilising a higher level of technology gives superior output.
2. The idea that because the Dutch apparently spend all their free time riding around on bikes means the brits would if given more free time is a joke. We'd spend it doing the things we enjoy (damaging our livers?), not suddenly become some imagined healthier happier version of ourselves.
All in all a pretty poor article I think as a result of the above isssues.
The article is comparing the UK (long working hours, terrible productivity) with Germany (short working hours, very much better productivity).
It's unlikely that there's much difference in the technology available. And they both surely know about all the modern methods of organising a workplace.
I mostly agree with point 2, but
> We'd spend it doing the things we enjoy (damaging our livers?)
Maybe the reason so many british people drink too much is because they're working too much, and they're (mis)using alcohol to wind down.
A quick one after work was far too common. I buckled far too easily to peer pressure and conformity. After all it's the done thing to do right? A crap day at work is solved by a pint (or three) after? And a good day at work... well that could be considerably more ;)
I now do a lot of running and bodyweight fitness. Drinking decreases my performance in those two activities and so I tend not to drink as I get far greater happiness from dropping a second in my minutes per mile than I do from having three pints during the week.
That compares data across the OECD, so fair enough this isn't comparing Papua New Guinea to the UK or similar. However, it mentions in the article the difference between Germany and Greece as examples of higher average hours and lower average productivity. I'd still tend to believe this isn't because the Greeks could get more done by working less but that Germans are tackling different work or using more technology in their work than the Greeks.
> Maybe the reason so many british people drink too much is because they're working too much, and they're (mis)using alcohol to wind down.
Maybe. It seems like we agree on this anyway. I was being slightly tongue in cheek here, not trying to suggest all the freed up hours would be spent in the pub :). I'll leave it at that.
one of the potential benefits mentioned by the article is the climate change perspective. from that perspective, the whole point of working less is a mechanism to reduce the rate that stuff gets done.
the downsides of this would be:
1. less stuff gets done 2. on average people have less income 3. on average people have less income, and this hurts poor people far more than wealthy people 4. perhaps the economy doesn't grow, and we don't know how to run society that way
the upsides might be:
5. there's a reduction in negative side effects (both generation of pollution and rate of depletion of non-renewables and unsustainable depletion of renewables (fish stocks, timber, soil, ...)) 6. we've got more time to do stuff that isn't work. hurray! 7. we've got more time to think carefully about what we're doing before we hit some hard limit 8. a lot of stuff that gets done is unhelpful, and now there's less of it 9. it's fairly obvious that we cannot keep growing the physical economy indefinitely, it might be a wise idea to try to learn how to run society in a different way before we're forced into collapse.
e.g. see the book "Prosperity without Growth: Economics for a Finite Planet" by Tim Jackson.
Land prices are set by credit which will expand to fill all labour less food / heating costs.
Only when land is cheaper can we opt out of working 40 hours and this will see a general reduction in the average working week. Until then we are all banker bitches.
I have wednesday off, so the week is divided into two-day stretches.
Not sure if I'm any more productive (maybe), but I'm a lot happier. I suspect some coworkers are going to follow my lead, now that the precedent has been set.
Everyone knows I won't be here on wednesdays, so we try to arrange things so I'm not a bottleneck during that time. If some really important deadline shows up, I'll just work the one wednesday and take thursday off instead, it's not a big deal. I haven't needed to yet though.
Besides, assuming you're not on a really tiny team, if many parts of your project hinge on one person with no available backup, you have bigger problems related to project management.
Of course if you have five people in a team and everybody has a different day off, you can never get together, and that may be a problem. This is the same if you and your colleagues work many days/hours out of the office or at home.
Our dev process required a lot of meetings and interaction. So in order to ensure clear blocks of working time, we used to set aside days as "no meeting days" Some people would take the opportunity to work from home on those days since it was guaranteed they wouldn't be pulled into a meeting. Once you know Sally, Jared and Kaitlyn won't be in on Tuesdays, you plan around it.
It's really not a big deal.
Seriously though, no man should be irreplaceable because of his knowledge, this is some serious risk you are taking.
The question is not whether or not you're as productive, but rather, are you more than 80% as productive as you were before.
Absolutely, that was what I was trying to convey (productivity per hour rather than total productivity) but it was poorly worded. A lot of discussion around shortening the work week focuses on the latter. While there may be cases where that's true, I think focusing the discussion on that is wrong because it assumes that there has to be an economic argument for making the change. For me, people having more free time is a positive in itself that society should probably optimise more for.
I am certainly not less productive per hour worked. I might be more productive, I don't know, but that should not be the only reason we contemplate such a change.
I can't imagine going to my boss and proposing I spend 20% less time working for the same amount of pay, and getting approval for that.
We have a progressive income tax here. The 20% comes from the part of my salary that gets the higher tax bracket. So in fact the decrease in amount I get paid is quite a bit less than 20%.
I also suggested this change at the yearly salary interview during which I negotiated a 10% raise. So really the amount I get paid each month didn't change all that much.
I'd be happy to take a 20% pay cut for a 4-day work week at some point in my life. I have a semi-retired relative who does just that.
As it is now, I'm vocal at reviews that I'll take more days off per year in lieu of direct salary increase -- an idea which seems to throw people off and hasn't been seriously entertained. At some point, I'll make enough annually, that I'll simply start taking days off without pay, which is something payroll seems to really hate for some reason when it concerns salaried folks.
Corporate pay/work expectations are really odd sometimes.
At the risk of sounding too glib, the short answer to why they hate it is it creates work for them. In the US, all of the major payroll processing services are geared towards either hourly or salaried templates. Most companies' payroll procedures are built around the core assumption that if you are salaried, then it is X salary divided across N weeks/months/your-pay-period. If you take days off without pay, changing the salary, someone in payroll has to manually key in the delta off your normal pay period processing numbers. That sometimes has downstream ramifications upon unemployment insurance reporting and remittance, for larger companies there are other regulatory-originated reporting that this can impact, and put in common issues like tax liens and family court-mandated levies, just for starters, and it gets hairy. Generally payroll processing is still built around a set of assumptions that are at odds with emerging knowledge workforce trends; the trends can be accommodated, but it's a hassle.
If you have a good enough relationship with your manager, then you are far better off negotiating a sub-rosa agreement to (in your example) work Wednesday this week and take off a couple days next week (or leave a couple hours earlier each day), and net out to zero change in time worked over a short (sub-month) period and leaving payroll none the wiser to any change in time worked, than making the payroll department perform an exception-based processing of your payroll.
US payroll processing trivia to illustrate how rigid payroll processing systems are today for the small business, and for flexible work arrangements: if you are a really small, micro-sized business, like say an Etsy seller with a couple full-time employees, set up as your own LLC or whatever, you will run payroll, except unlike larger businesses you will frequently want to know how much to pay yourself (after paying off all employees and vendors) including all employER-side tax liabilities, and not just the employEE-side disbursement. All of the top-ten payroll processors have no capability to compute that for you; you have to iterate to an approximation. In other words, if you know you can afford to pay yourself only $10K total this month, payroll processors force you to key in a employEE net pay number then they spit out the gross including the employER side, and only then do you see if you are over/under the $10K amount. There is no feature that lets a small business owner say, this pay period, I can only afford at most $X cash out the door total including all tax liabilities for so-and-so employee, iterate and solve for me what the best result is to achieve that.
US payroll processing can get really complex, really fast even for small businesses, so I can imagine what a nightmare it must be for the designers and developers of those systems. However, I believe there is still plenty of room for someone to create a disruptive service that caters to and appeals to small businesses.
If taking a day off during a working week causes them additional effort, it is only because they are grossly abusing the definition of salaried employee the entire remainder of the year.
If they want to handle employees as though they were hourly, they could just stop lying about their people being salaried exempt employees.
If you are salaried, and your manager is fine with you taking Fridays off, payroll does not need to know. If a deadline approaches, and you need to work Saturday and Sunday, too, payroll does not need to know. Salaried workers are supposed to be paid for getting their work done, and not just for punching the clock.
It seems as though many employers are abusing the legal definitions in order to bend labor laws.
This is absolutely what is going on in many US companies, no question. That's a separate can of worms for the political and legislative arenas, and not one that individual salaried employees can safely change on their own within their company. Discussions about this also tend to drag in meta-discussions about compensation, project management, management accounting, work environments, etc., adding more worms to the can, and even more cans of worms to the original can. It's messy.
What you outlined is definitely what should happen. The jobs situation is bad enough for many fields outside of our own, and even many areas within our own field, that flagrant flouting of salaried exempt labor laws is allowed by regulators, and encouraged by shareholders. Longer-term, this only hurts the companies, because they're receiving imperfect signaling of actual required effort, distorting all future projections; competitive advantage accrues to those companies that accurately and precisely calibrate their projections to known required effort. Change will come slowly and haphazardly, if only from the ongoing population growth slowdown, hopefully.
But the reality is that many managers and employers only support the part that benefits them. Even many of the ones that are supportive of someone taking a Friday off every other week feel that they're doing you a favor or giving you a "perk". At the end of the day your manager has to support it (and if necessary continue believing they're doing you a favor) because they can find a way to shit-can you if you start pushing boundaries they're not comfortable with (in the US).
Eight hours isn't really enough time to get anything done, particularly during business hours.
I only see a few possible downsides:
- Someone expecting you to be in the office and you're not, particularly if they're not familiar with your schedule.
- For developers the same issues with 60+ work weeks often come up in hours 7-10 of a single working day. Off-campus lunch for a full hour (or more) would probably be important, which pushes your full day to 11+ hours.
- Using 10 hours of PTO when you take a day off, but I guess that's what you get for getting the 4-day weekends :)
The only (kind of ironic) downside is that holiday weeks are kind of sucky. The holiday day only pays 8 hours, so he ends up having to still work four eight hour days those weeks.
My brain was fried and I was glad when the policy was canceled.
I loved the extra day though (which was Monday or Wednesday) and as a software engineer I would love to pull it off, to rest or work on my own thing, but I would gladly take a pay cut than work 10 hours a day constantly.
What does CSR stand for?
After awhile my workload dropped practically to zero, and I started leaving at 5. Kept it up even when there was a workload, and found that completion times didn't suffer.
Don't propose anything. Just start shifting your schedule around and see if people complain. Do it slowly and people won't notice, or if they do, won't care.
In the corporate world, you don't ask for permission, only forgiveness. The word they use for it is 'initiative'.
Around the time I was doing this, I got a new manager. I was wholly unwilling to reorient my schedule around his expectations, but I would stay until he left for the first few weeks. One day I followed him out, even though it was at least an hour before I "should" have been leaving. I'd also taken an hour-plus long lunch that day. I told him I usually leave at 5, but I was staying late in case he had any questions for me. He was like, "even though you took a long lunch??" and I just nodded, and followed him out. He didn't mention it again, until I started talking about taking another job.
There is a space in between political expectations, business needs, and personal wishes at any job that is ripe for exploration and exploitation. One can iterate towards their ideal work environment and conditions at any job where their performance is stellar. Just keep the business needs and political expectations in mind and you can practically get away with murder.
Get a 25% raise, and then 6 months to 1 year later drop down to an 80% workload and take the corresponding 20% cut in pay.
I definitely felt like it made me more productive per hour worked. A shorter week added a little bit of time pressure that helped me stay focused, and I'd often finish something in four days that might otherwise have stretched to five.
Total output was probably a little lower, but I took an equivalent pay cut when I reduced my hours.
I was only able to make that arrangement after I'd been at the job for a while. When I changed jobs, I went back to five days a week, and I'm definitely missing the long weekends.
The worst possible scenario would be workers switching to shorter work weeks, accepting pay cuts and loss of benefits, and proceeding to be more productive for their employer. I mean, unscrupulous employers would love it, but for society it would be terrible.
Yes, sort of. I approached this during the yearly salary interview. I negotiated a 10% raise, and a change in work schedule to 80%. So I'm getting paid 0.8*base_pay, but I didn't just take sudden a 20% cut between months.
> Did other benefits which legally require a 'full time' schedule go away?
I checked with my union (union membership is mandatory here but they really only negotiate minimum vacation days and minimum salary for a given profession/class, neither of which affects me since I have negotiated above and beyond what they have - it's a very different system than US people are probably familiar with) and according to them, there should be no change to any benefits or legal rights. Things like the fixed christmas bonus will be paid to 80%.
> The worst possible scenario would be workers switching to shorter work weeks, accepting pay cuts and loss of benefits, and proceeding to be more productive for their employer. I mean, unscrupulous employers would love it, but for society it would be terrible.
I'd rather not work more hours than I really want because my employer might benefit from me doing what I want to. If this concerns you, you can just keep your productivity per hour to the same level as it was before. I have no idea if I'm actually more productive, and I don't really care. What matters to me is I now have an extra day every week to do something that I actually want to be doing, rather than working for someone else.
Put another way, if you feel like your skills are undervalued, talk to your employer about a raise. This holds regardless of whether your work proportion is 100% or 80%.
Personally, for almost all of my professional life I didn't work Monday's (32 hour work week). That worked out really well for me.
This is just wacky.
"150 years of research proves that long hours at work kill profits, productivity and employees"
http://www.salon.com/2012/03/14/bring_back_the_40_hour_work_...
edit -----
Secondary source: https://news.ycombinator.com/item?id=3547965
Quoting the secondary source:
"From a business point of view, long hours by programmers are a key to profitability. Suppose that a programmer needs to spend 25 hours per week keeping current with new technology, getting coordinated with other programmers, contributing to documentation and thought leadership pieces, and comprehending the structures of the systems being extended. Under this assumption, a programmer who works 55 hours per week will produce twice as much code as one who works 40 hours per week. In The Mythical Man-Month, the only great book ever written on software engineering, Fred Brooks concludes that no software product should be designed by more than two people. He argues that a program designed by more than two people might be more complete but it will never be easy to understand because it will not be as consistent as something designed by fewer people. This means that if you want to follow the best practices of the industry in terms of design and architecture, the only way to improve speed to market is to have the same people working longer hours. Finally there is the common sense notion that the smaller the team the less management overhead. A product is going to get out the door much faster if it is built by 4 people working 70-hour weeks (180 productive programmer-hours per week, after subtracting for 25 hours of coordination and structure comprehension time) than if by 12 people working 40-hour weeks (the same net of 180 hours per week). The 12-person team will inevitably require additional managers and all-day meetings to stay coordinated.
It's the unit size that matters. Mythical man month said the ideal basic organization for delivering work output is modeled after a surgical team. If you model after traditional military units, the infantry squad is the equivalent to that team.
Under the mythical man month org structure, the atomic unit of work capacity is that surgical team. You can't do more surgery by putting two more surgeons in the OR. But you can add new teams and get more output. I think the analogy works in the military context as well -- a general doesn't ask for <X> more individual soldiers, he asks for more battalions/regiments/divisions.
Hence, working less time with (theoretically) better focus and reduced stress/strain would be more productive.
There's a fair number of jobs where the work itself is not hard or time consuming, but where a culture has grown where everyone needs to justify their position. This skew incentives; if you're a junior, you end up doing a bunch of little things that can pass as a laundry list of things someone had to do. If you're senior, you can gun for getting credit for grandiose sounding things like "strategy". Junior people end up in meetings all day, which if you're senior, you end up calling everyone into. Everyone sits around until late to demonstrate worth.
A lot of these jobs could be done remotely, on any schedule with a sensible number of hours, by just about anyone who can read and write. But because of the culture, they end up being done by the only people who have 100 hours a week, namely singles in their 20s who are just out of university, in some very expensive location. These people then have families to feed and get stuck propagating the same sick culture.
I don't see the law as providing a solution. Nobody enforces the 48 hour contract in Britain. When did you last hear about a City sweatshop being liberated by the police?
The way to change the culture is actually, believe it or not, startups. Yes working hours can be horrible in startups. But in an environment where a lot of firms are startups, there will be more variation in the working culture. Certain firms are already showing the way forward with flexible hours, remote work, and other family friendly practices, without compromising on quality.
I'm enjoying having a job where not only do I only have to work 8 hours a day, I'm not even allowed to work more if I wanted to.
Guilty. If I could switch to a 4 day work week, I'd get the same amount done, but spend a bit less time on Hacker News and other distractions. Hell, let me work a 2 day week and I'd cut out all distractions to finish what was needed.
My gym AND my favorite bar were closed all holiday.
Why would you be at either of those places? You should be enjoying yourself like everyone else during this time.
Judging by the abysmal labor participation rate and unemployment stats in the US, this is easily done. Per-worker overhead costs would force an increase in the labor budget for most companies, though.
As many businesses have been ruthlessly slashing that budget category for a while, that is likely to prompt a lot of bitching and moaning from company management--even from businesses that depend on consumers being able to afford their products.
It's just a scheduling problem. If a business elects to be open longer than 6 hours per weekday, it will need to have some workers work at different times than others. But I do recall visiting the government license office once on my lunch break, only to discover that most of the workers there were also out to lunch, and took more time out of the middle of the day than I wanted to.
So, anecdotally, whether or not the world functions when you need it to function depends more on how much the business cares about serving its customers than the number of hours its workers are on-site every day.
I originally added the cheap one because it's just 4 minutes from my house, ruining my ability to flake out on the basis that "I don't have time to do X before they close".
Looking back I think 25-30 hours is about as efficient as I could have been as I gave the best hours of my day. But when it came to the last month before the release I found I did have to give some more time to get it done on time. Short bursts of working long hours seem to be effective for me, but I also noticed that I needed to take some time off after the project.
It's been a great year and I've really enjoyed the other things I was able to do with my time. If you are able it's worth considering even if you take a little less pay.
However, last year I got tired of the full hours and a bit depressed because of lots of factors that prevented me from getting things done, and after one realisation I took a month off. Coming back to work I figured I shall be going with working full hours for three months and then taking a month off again. So that comes to three months of spare time and nine months of work annually.
The realisation was about working patterns. For a programmer like me, the best productivity comes in bursts so I'd happily do three ~12-hour days and keep two days off as opposed to working the official 7.5 hours (in my country) every day. This has always been so, even as a kid. I could work on something really intensively for a few days and then I needed to do something completely different. The newest realization was that it works on longer timescale too. I can work three months and do my absolute best, and then relax and have time for my own things.
This sort of a contract――relax pattern is quite reminiscent to life and nature itself. I feel much at home between the pushes and pulls. I'll see how the first year will turn out to be.
Over the years I've also realised that staying productive is mostly just about conserving these important productivity patterns.
A lot of what happens at work eats away from these patterns but if you can keep them mostly intact then you'll get productivity by default. That is, assuming that you love programming. Hint: if you're known to occasionally spend hours on hacking something at work at an intensity where nobody can pull you away from it, it's a good sign that you love programming.
My employer is not a particularly conservative company and it helps that my boss is great and if he has to cross-check something with his boss, his boss is great too. And it probably helps to have a somewhat senior position (next milestone: ten years) and having made my mark years ago.
But most importantly: getting your shit done. If you can get your shit done you're in a much better position in getting everyone to agree on more flexibility into your job because companies need to get shit done.
Wise employers recognize that it's of everyone's benefit, including theirs, to keep productive employees in a loose leash with more freedom of choice rather than impose binary requirements on how and when to do the work. If my employer wasn't wise like this some other company would be enjoying the fruits of my productivity as I would've left them years ago.
Even if you work at the very best companies and love your work, work is still always work and it will at some point become too much, meaningless, source of frustration, or any combination of those.
Are there signs you look for to leave it on a high note, or do you use hard time limits?
That way he had an easy start next day.
Perhaps it's also a good method to work as a programmer? Don't fight to close that ticket before the end of the day?
If I can finish something in a day what could've easily taken three days, I'll probably end the week a bit earlier. And if I get fixated on doing some "simple thing" that ends up taking a lot longer, then I allow myself to work extra to get that squashed. It's important keep your conscience fair so that you know you can mentally match the hours with results produced.
Programming isn't strictly about wallclock hours but wallclock hours are a good starting point for measuring a fair effort because your pay is likely to be based on the wallclock too. (Such as 22 days * 8 hours or so.) But some hours are indeed "thick" and some hours are "lean" and you need to balance those somehow. Otherwise you'll be working way too much or way too little in relation to what you are paid. If you only look at the chronographic units you will realize that you can't do so. If I'm walking in the woods and figure out how to architect some component, is that work or not? And how is it work if I sit at my desk for half a day and get nothing done? That's what you have to live with as a programmer and striking the balance is delicate business, but luckily it's enough that you only need to find the balance in the average.
Then again, it's all about shit. As long as you get shit done the hours don't matter. And as long as you don't work too many hours to feel shitty yourself, the scheme is sustainable. That's the ultimate balance.
Yes, but total output = number of hours x productivity. So even while productivity diminishes, your total output can increase if you increase number of hours.
If a worker can quantify roughly how much time and energy each task at work will take up, a clearer picture of how to be the most productive in the least amount of time will reveal itself. Employers perpetually hide in the ambiguity of the employees' time and effort, hoping to make a profit out of asking for too much and motivate their workforce by periodically throwing a tiny bone to the most masochistic over-achiever. A tabulated rubric describing to the employer exactly how much time is spent on each task and how much mental and physical energy the task takes relative to the worker's actual capacity for these energies would show exactly how wasteful it is to over-work people.
Longer hours deplete worker mental energy and physical energy resources whether or not there is more work being done. Once these resources are depleted, worker efficiency drops precipitously. Additionally, periodically depleting these resources leads to worker burnout. I also suspect that workers resent longer hours whether or not they are necessary, leading to weakened ability to refill their mental energy reservoir due to poorer mental health in general.
[0]:http://cryoshon.co/2016/01/04/how-to-survive-late-capitalism...
[1]:http://cryoshon.co/2015/12/23/time-management-tips-hot-from-...
[2]:http://cryoshon.co/2016/01/01/how-to-decide-what-to-prioriti...