[dont__panic]

I wonder if the increasing shift toward remote work (often in disparate timezones) will end up pushing teams to eventually adopt 1-3 "core hours" 2-3 days per week with team meetings and collaboration sessions and a more laissez-faire attitude toward working the rest of the usual 9-5 day; I would love to just focus on getting my work done any time I feel like it, attend meetings during core hours, and have the ability to get out of the house and go do things during the normal workweek.

[UnpossibleJim]

Except for meetings and deadlines, why is anything measured in hours. Why aren't things measured in amount produced? (I hope it's obvious I'm speaking in terms of coders and manager's teams - I have no idea how this would work for directors or above.) The majority of coders are employed on salary (so far as I know), so just pay their salary and expect tasks to be completed. This mandatory 40 hours in a seat ritualistic adherence seems dated and unproductive. Different people will work better in different situations, and it is one of management's tasks to see that their team's potential isn't impeded when trying to complete their tasks as a unit, even when that means working as a coordinator between separate individuals on the same team, working towards the same goal. The work should be what's valued and not some myopic adherence to a past life of offices and collared shirts.

[heavyset_go]

It's because workers in general don't have much leverage when it comes to being compensated for the value of the fruits of their labor instead of just their time. Owners want to capture that value instead.

[JanisL]

I think in part its because hours are extremely easy to measure compared to productivity in many complex work environments.