3 ms·
Covered at least in part in http://ericdodds.com/research-and-the-realities-of-time-worked/ http://ericdodds.com/research-and-the-realities-of-time-work... - in
by thenomad 11y ago
Covered at least in part in http://ericdodds.com/research-and-the-realities-of-time-worked/ http://ericdodds.com/research-and-the-realities-of-time-work... - including perception vs reality of productivity in crunch time. He has a graph on that:
http://ericdodds.com/wp-content/uploads/2015/06/graphing-percieved-productivity-daniel-cook-working-overtime-eric-dodds-productivity-hacking-blog-series.jpg http://ericdodds.com/wp-content/uploads/2015/06/graphing-per...
It's possible that some special individuals can work longer hours than average without productivity loss. However, without hard data to prove you're one of those individuals, given the above, it may be inadvisable to simply assume you are...
- falcolas 11y agoIn addition to this, for every "capable of working more than 40 hours" worker, there's another "incapable of being productive more than 40 hours" worker. That's the joy with averages. So look around you - of the 20 people who are working late hours with you and believe they are still productive, 10 of them are wildly unproductive, quite possibly to the point of contributing disproportionally negative productivity due to writing bugs. Is the additional 400 man-hours of productive work worth those 400-800 man-hours spent debugging problems which could have been avoided?