- Sep 4, 2005
- 28,193
- 17,030
- Country
- United States
- Gender
- Male
- Faith
- Atheist
- Marital Status
- Single
- Politics
- US-Others
That's going to depend on the industry. If you work for an hourly wage where your presence is a component of the work (and therefore a reduction in worker hours per week would require the employer to hire more people), then sure. But for roles where you're simply expected to be "working" and complete your tasks on time (i.e. most office roles), then it doesn't really matter if you work 40 hours or 32 hours as long as the work gets done.
Interestingly, the largest trial of a 32-hour work week included a guarantee that pay would remain static. And it was a massive success:
Yep, I've actually seen a couple different random "experiments" like that where even with a reduction in hours, people still ended up getting the same amount of work done.
I think it shows that by the "end of the day" or "end of the week", people are getting a little bit of burn-out and probably aren't giving 100% by the time they reach the 32+ hour mark and go into "Office Space" mode.
My company does the "summer hours" incentive. Where, between memorial day and labor day, as long as all deliverables are met on-time, the "summer hours" are 8:30 to 3:30 (instead of the normal 8:30 to 5:30)
It's worked pretty well, and people will hustle and put in max effort when they know it means getting to bail early when the weather's nice outside.
They've also implemented the "on-call offset". Like in most IT outfits, everyone takes their turn being the "on-call" contact for issues or client needs that happen off-hours. Any hours that you work "off-hours", gets deducted from the subsequent Friday after your done with your on-call rotation. So if you get a call and have to put in 4 hours in an evening or on the weekend, you get to bounce at noon the Friday of the following week. That's been a pretty popular one at the company as well.
Last edited:
Upvote
0