[tluyben2]

Not sure what your line of business is or what your employees do, but when working with teams of devs, the day is made up out of focused work, small tech meetings and maybe a bigger meeting. Remote or local makes little difference with us here. Outside those, which need to be more or less synchronised, the rest are deliverables. Some days I am done in 2 hours or I just am unproductive (slept badly, cannot be arsed, nothing works anymore after a minor react native update, whatever the reason); some days code is flowing and I stand behind my desk 17 hours (like today). My colleagues are like that as well, at least by far most of them. With your regime, I would be frustrated on both occasions.

I do not understand (and that does not mean you are wrong; maybe there is no wrong or I am) how anyone conflates hours with productivity; you want me to do tasks a1-a10 this week; why is it relevant if I do those Thursday night in 16 hours or 40 hours spread over the week? As long as they get done and done well right? I cannot think which type of work would not work like that but cannot think of any so how is it related to ‘hours behind the screen’? I have tried these things in the past as well with my colleagues over the years and the ‘bums on seats’ only invites people to work slower (to fill the time and not have to do more work) which in turn indeed invites the use of spyware to see if they are working.

Now we have tasks; if some superhuman does them in 5 minutes instead of 40 hours; glory to her. Obviously that does not happen, but 30 vs 40 does sometimes and that is fine with me; stuff gets delivered, people are happy. I also have a few guys who get nothing done one week and over-perform the next; as long as I know that, it is fine. Weekly sprints are overrated anyway imho.