Slashdot Mirror
Half of IT Workers Sleep on the Job
Stony Stevenson writes "According to a new online survey by Harris Interactive, more than half of IT workers say they've fallen asleep at work, while nearly half of techies also are apparently in the mood for love. Forty-seven percent of tech pros admit they've kissed a co-worker, according to the online survey of 5,700 U.S. workers, including 163 techies.
The survey didn't indicate if those work taboos were committed by the same respondents, but in both cases, men were more likely to admit doing both. Forty-nine percent of male techies say they've fallen asleep at work, while only 35 percent of women admitted doing so."
I have an older employee who handles some contracts (hourly) that has a tendency to fall asleep. He's within a decade or less of retirement, and we've caught him napping a few times in recent months (as has the customer he's usually working at). We've talked, and it definitely seems like there's a medical issue here, so it leaves us with having to just compensate the customer for any billable time where he has fallen asleep. We've considered moving him to an internal job, but he's really good at the tasks he leads, and he also works very hard otherwise. The customer is also understanding because they have realized that his productive time more than compensates for his napping time, but there's always a fear that the contract could expire over this particular issue.
I'm sure most of the people polled here are younger, but it's definitely not just a laziness issue.
Yes, falling asleep on the job is one half of the equation, working 12-18 hour days or being on call 24/7 is the other side of the equation. I was at EBay once and saw people with sleeping bags under their desks as well as watched a father singing a lullaby's to his kid over the phone because something blew up and work needed to be done.
Believe it or not, there is actual research done on this--not that anyone ever pays attention to the results. If I recall correctly, it boils down to something like this:
- Productivity is low for the first 1-3 hours of a day as people get into the swing of things- Daily productivity mostly goes up, but drops toward the end of the day (possibly because people are consciously "winding down")
- Productivity per worker hour peaks somewhere around a 30-hour week.
- Total sustainable productivity per week peaks at around a 45-hour week.
- Around 50 hours and up, fatigue builds up over time until burnout kicks in. Sustained work weeks of 50 hours are likely to be getting less TOTAL WORK done than sustained 35-hour weeks.
- Work weeks of around 80 hours are sustainable for maybe a week or so before catastrophic loss of total productivity occurs
- Anything much more than 80 hours likely results in immediately LOWER productivity, as fatigued workers make mistakes that take more time to fix than the extra hours provide.
From this, one can conclude that European schedules are more likely to maximize individual productivity (more work per hour), while American schedules are more likely to maximize organizational productivity (more work per person). One can also conclude that any manager who demands sustained work weeks of 50 hours or more is incompetent and a fool; the management equivalent of the kind of programmer who creates so many bugs he provides a net negative productivity to the team.
In practice, actual work hours are lower than they appear; most salaried workers are prone to finding numerous ways to not work while at work, largely because in many office environments physical presence is seen as more important than actual productivity.
I suspect the best balancing point would be something like four 9-hour workdays per week. Longer days to minimize the productivity drain of mornings, but a shorter total work week to allow occasional bursts of extra effort without creating long-term burnout.