3 ms·

I think if managed correctly the second option is more than achievable for a software development team. I agree it doesn't work for all industries / jobs (e.g.

I think if managed correctly the second option is more than achievable for a software development team. I agree it doesn't work for all industries / jobs (e.g. support staff etc), but for the majority of technical positions, I think the gain in productivity and saving in salary will more than make up for these inconveniences. I also think it will make the recruitment of developers easier as you'll be offering a benefit rarely seen. And ye, a few people have mentioned the point about 28hrs - I'm going to rebrand it as "4 day week".

pc86 6y ago
I'm sure some people will disagree but working less for less money isn't seen as a benefit to me, especially in the US where there may be healthcare implications. And as others have said, given static overhead you're more likely to earn less per hour. You're likely better off going contract and having a higher hourly rate and just billing less, but that has its own set of difficulties. The real benefit I've seen very few places implement is a 36-38 hour week, over 4 days, with no decrease in salary. Productivity is the same or slightly higher (quite a bit higher if it's a set schedule, e.g. everyone has the same day off so there's no communication latency). Satisfaction is through the roof because not only are people getting paid more per hour, but it's a benefit that they're extremely unlikely to find anywhere else, so retention goes up as well.
- BlargMcLarg 6y ago
  I both agree and disagree. Disagree as this implicitly assumes working 40 hours won't produce relatively more negative feedback on one's personal life than a 32 hour week would. Once you start accounting for that, the "net loss" story becomes a lot more vague. Given if the requirement was "you really have to work this number of hours to get that total income", I would prefer longer days + fewer days over the 9-5 mentality most countries have. Unfortunately, the last time I requested 9x4, it got denied. Let alone more extreme variants, 4x10, 3x10 or 3x12. Ironic, since 4x10 would also have less overhead, despite still being a 40h workweek.

pc86 6y ago

I'm sure some people will disagree but working less for less money isn't seen as a benefit to me, especially in the US where there may be healthcare implications. And as others have said, given static overhead you're more likely to earn less per hour. You're likely better off going contract and having a higher hourly rate and just billing less, but that has its own set of difficulties. The real benefit I've seen very few places implement is a 36-38 hour week, over 4 days, with no decrease in salary. Productivity is the same or slightly higher (quite a bit higher if it's a set schedule, e.g. everyone has the same day off so there's no communication latency). Satisfaction is through the roof because not only are people getting paid more per hour, but it's a benefit that they're extremely unlikely to find anywhere else, so retention goes up as well.

BlargMcLarg 6y ago
I both agree and disagree. Disagree as this implicitly assumes working 40 hours won't produce relatively more negative feedback on one's personal life than a 32 hour week would. Once you start accounting for that, the "net loss" story becomes a lot more vague. Given if the requirement was "you really have to work this number of hours to get that total income", I would prefer longer days + fewer days over the 9-5 mentality most countries have. Unfortunately, the last time I requested 9x4, it got denied. Let alone more extreme variants, 4x10, 3x10 or 3x12. Ironic, since 4x10 would also have less overhead, despite still being a 40h workweek.