4 ms·
> A group of first-year analysts at Goldman Sachs Group Inc. complained to bank leaders last year that they were working an average of 95 hours a week and that
by neilv 4y ago
> A group of first-year analysts at Goldman Sachs Group Inc. complained to bank leaders last year that they were working an average of 95 hours a week and that job stress had harmed their physical and mental health.
I'm pro-ambition, pro-commitment-to-the-team/mission, and a recovering workaholic. But don't do crazy hours like this. It's permanent damage.
Target 40 hours a week. Make those hours productive towards the org's goals and not misaligned individual goals/metrics (experienced engineers and the manager and PM should be blasting the inefficiencies out of everyone's way). Keep stress low, and only for good reasons (again, stupid reasons need to be fixed promptly).
If you've got people being actually productive and on-track towards org goals at 40 hrs/wk with low stress, that's a great environment. And when some rare emergency happens that can't just mean slipping the schedule, then some people will have the time/energy/morale to surge their effort to to whatever sweat/magic is necessary. Then they get flex time after.
And we educate new people about how we were able to handle the emergency, and the importance of not breaking this hard-earned effective organization.
- yodsanklai 4y ago> Target 40 hours a week. Not as easy as it sounds. For me, doing 40 hours of actual work means staying 60h near the computer or in the office. I take too many breaks chatting with colleagues, or browsing HN. Well, this is my problem... Plus my company measures "impact". Unfortunately, lot of work which has to be done is not impactful from management's perspective, and requires working more in order to generate impact and have something to say in your self-assessment. Of course, everybody in my team do work more than 40h, so you have to keep up in order not be in the 15% of low performers in line for the next layoff.
- jen20 4y ago> I take too many breaks chatting with colleagues, or browsing HN. Have you considered remote work, from a timezone 2-3 hours ahead of others? It’s nice to have mornings free from distraction…
- nerdawson 4y ago40 hours of total work. Not 40h of your best work, 40h of output. If that lands you in the bottom 15%, I’d start looking for other opportunities. I’ve been in your shoes. We had time tracking and for me to consistently log 40h of actual work in a week, I’d have to sit in front of my computer from morning to night. Even weekends sometimes to catch up on what I’d missed. What a fool I was. I did that for years for mediocre pay (although I couldn’t see it at the time) to the detriment of everything else around me. It wasn’t worth it. Now I couldn’t care less. The whole “quiet quitting” phenomenon resonates deeply with me.
- alkonaut 4y agoI report 40h. I might be 35h at my computer. That might be 20h of productive work. No one ever questioned my work output neither in quality or quantity. The idea of the 40h work week isn't to be productive 40h, no one can do that in creative work. The idea is you are available 40h. If you are at a healthy workplace, then no one around you works more than 40h either.
- keithplayer 4y agoI agree and the following is more related to the text you quoted. I interviewed at GS and as soon as I saw the room of clearly exhausted and joyless developers, I could see they actually valued the appearance of work more than productivity. The 40-hour work week was introduced for a reason: https://cs.stanford.edu/people/eroberts/cs181/projects/crunchmode/econ-crunch-mode.html https://cs.stanford.edu/people/eroberts/cs181/projects/crunc... It is sad that 100 years after Ford made the discovery people still don't get this. Team A consistently working 40 hours per week will output more work than Team B working 60+ hours per week. That's true for 60, 80 and especially 95+ hours.