The Compelling Case For Working Less (bbc.com)

An anonymous reader shares a report from the BBC, written by Amanda Ruggeri: As we fill our days with more and more "doing," many of us are finding that non-stop activity isn't the apotheosis of productivity. It is its adversary. Researchers are learning that it doesn't just mean that the work we produce at the end of a 14-hour day is of worse quality than when we're fresh. This pattern of working also undermines our creativity and our cognition. Over time, it can make us feel physically sick -- and even, ironically, as if we have no purpose. Think of mental work as doing push-ups, says Josh Davis, author of Two Awesome Hours. Say you want to do 10,000. The most 'efficient' way would be to do them all at once without a break. We know instinctively, though, that that is impossible. Instead, if we did just a few at a time, between other activities and stretched out over weeks, hitting 10,000 would become far more feasible. "The brain is very much like a muscle in this respect," Davis writes. "Set up the wrong conditions through constant work and we can accomplish little. Set up the right conditions and there is probably little we can't do." Many of us, though, tend to think of our brains not as muscles, but as a computer: a machine capable of constant work. Not only is that untrue, but pushing ourselves to work for hours without a break can be harmful, some experts say. Ruggeri goes on to highlight the negative health effects associated with working long hours. "One meta-analysis found that long working hours increased the risk of coronary heart disease by 40% -- almost as much as smoking (50%)," she writes. "Another found that people who worked long hours had a significantly higher risk of stroke, while people who worked more than 11 hours a day were almost 2.5 times more likely to have a major depressive episode than those who worked seven to eight."

Comments

Re:Work less

[TheRaven64]

There was a study a little over 10 years ago that measured productivity in a variety of 'knowledge worker' applications and concluded that productivity peaks at about 20 hours per week, then plateaus to about 40, and then drops off. This is particularly noticeable in something like programming, where a small mistake made when tired and not thinking straight can lead to 10 hours of debugging the next week. People who work a solid 4-5 hours a day are likely to be a lot more productive than people who are physically present and trying to work for 10.