[microtonal]

short-term crunch can sometimes make sense

It makes sense when all your employees are singles without a family or any other obligations outside work. You might want to take into account that your employees who are not, may have to pick up their kids from kindergarten/school, etc. They may not be able to work long hours without letting down their children or damaging their marriage.

You could make crunch optional, but there is some peer pressure ('Look, Johnny is not committed to our project').

These are waters to thread carefully if you want to have healthy/happy employees. Make clear rules ahead of times of what is expected, pay extra compensation for overtime.

(Sorry if I set up a straw man.)

[tigroferoce]

Too bad I can only vote once UP for this comment. I fully agree; I have a family, my wife is a doctor and she works on shifts, so I often have to pickup kids and so on.

A huge cost that is often misunderstood is the cost of replacing an employee who leaves because the working conditions (endless hours, regular extra time, bully environment) are not compatible with his/her work/life balance.

My previous workplace was founded upon extra time (I remember our CTO and CEO clearly saying that he expected people to work 50-60 hours per week. The CEO literally said multiple times "these people are young, I expect them to work 120%").

We constantly were fixing issues and problems, we never had time to properly plan and design. Once the CTO told me that he expected our SW to have problems, but since we had no time to fix them or to build better software, he also expected the programmers to be available so fixing production issues when they happened no matter if it was night or weekend. Once he told us that he expected senior developers to check email once a day while on holiday to check if there were no problems.

No wonder that in a few month 3 out of 4 of the senior engineers left the company.

[dkersten]

Peopleware talks about this. There is a cost to overtime in terms of lost productivity afterwards and in terms of developer happiness. When developers are unhappy, their work quality drops and eventually they leave. Cost of employee turnover is mentioned as a cost that is actually quite high, but rarely factored in.

They also say that overtime can make sense if its short and a rare occurrence.

[tigroferoce]

An employee who leaves is a tragedy, especially in smaller companies. His work has to be shared among the other (implying even more extra time). Then you have to start a new acquisition process to hire someone new, train him, fit him into the existing group and so on. And if someone leaves because of the company culture, there is the possibility that other will follow, making the cost even higher.

[Xylakant]

I found a good way to curb crunch is to pay extra for it: Every mandated hour that exceeds the regular work time gets paid 25% - 50% on top, preferably in time off (that is for 8 hours extra a week you get 10-12 hours off the next). This allows for crunch time when needed but provides a strong financial incentive to avoid it. A lot of things suddenly drop in priority from "absolutely crucial" to "can be done next week" when you respond with "I hear you, are you willing to pay a 50% premium for that?".

Also offering help with child-care makes things easier for employees with families. Those are solvable problems if crunch-time is limited to short stints and if both sides are willing to work together.

[douche]

Hmm, compensating employees at 50% more for hours above and beyond the normal work week, what a novel idea! /s

[Xylakant]

I fail to understand your post: it's neither a novel idea to compensate extra for overtime nor did I claim it was. I just said that I found this to work well.

I see unpaid overtime as one of the primary drivers of extreme crunch abuse. It aligns incentives in the worst possible way: More work gets done per week (though only marginally at best), project management gets to claim "we're doing all we can" and then, on top it's actually free time donated by the employees at no immediately obvious costs. Not surprising that this sounds attractive.

[douche]

I've struggled for years trying to get my headspace into the right place to deal with salaried work. I've got a very blue-collar background, and my first few jobs were in those kind of hard-hat & steel-toe boot industries, where you literally punch in and out, and your compensation is directly tied to the number of hours worked. In those situations, the calculus you're describing about "does this need to be done now, or can it be done tomorrow?" already takes place, since unpaid overtime is illegal, and if you need more than 40 hours in a week from an employee, you have to pay the premium for it.

[Xylakant]

It's less of a salaried work issue, it's more one of people not knowing or not caring about their rights. I can't talk about the US landscape but in germany unlimited unpaid overtime is not legal, still you see that often in work contracts, especially in contracts in startups and web/multimedia agencies. Its especially common where unions and other organizations that could enforce legal limits are weak. I've for example never seen such a clause (and unpaid overtime) in organizations where a strong worker rights position existed.

[czep]

There's a better way: order some pizza, cans of red bull, and call it a "hackathon".

[st3v3r]

No to overtime being paid in time off. Many times, they'll gladly let you do that, only to not let you ever use it, assuming they actually remember that they promised it to you.

[smartbit]

are you willing to pay a 50% premium for that?

Nice! I'll remember that one.

[Piskvorrr]

That's the point of "short-term" - that's weeks at the very most. Of course, a PHB will take this to mean "until the next release, half a year away, that's not too long, no?"