Do strict working hours affect the productivity of a remote worker?

Question

Work organization

Do you think the workday limits affect the productivity of a programmer working remotely?

Work involves daily participation in the project for 8 hours. A tracker is installed on the computer that tracks your work on the project. It is advisable to close at 8 o'clock. Every 5 minutes, a screenshot of your desktop is sent to your employer. At the same time, there is a daily online planning meeting, where you report on completed tasks from trello and voice an approximate work plan for the day.

At the same time, some team members prefer to work in the evening and at night, some from morning to 18, while others work throughout the day with breaks for rest.

In your opinion, is it reasonable for management to require each participant to work in a limited time period (from 9 to 18) or will this restriction lead to a decrease in productivity in the team?

I noticed by myself that it is not always convenient to work within these frameworks. Sometimes it's easier to start work at lunch and continue until night, and then get enough sleep in the morning and work your shift with good efficiency.

Or is it better for everyone to work in the same mode and accustom yourself to this?

A caveat - the rest of the team members do not suffer from the fact that you work at different hours, unless of course you work at night, but sleep when they start work.

Answer 1

A tracker is installed on the computer that tracks your work on the project.

Surveillance of employees is the most effective way to turn on negative selection and get a team of absolutely useless, and even harmful people, because only those who are no longer needed by anyone will not quit.

Work involves daily participation in the project for 8 hours.

That is, leadership is not result-oriented, but process-oriented. However, any intellectual work in general, and programming in particular, works differently than digging trenches.

Answer 2

yes, most of the time, the schedule of people in the team should coincide, or if people do not communicate promptly, this is not a team
, we have quite acceptable shifts, since the team is quite large and everyone has different time zones,
some have +3 GMT, some have +7, but in general, everyone is available during the daytime, when everyone has a day, and in general, most people are always available, always awake, this is not often required, but if something happens, you can consult without problems.
in general, a constant rhythm and work schedule is important here, there are people who sleep at random, they don’t, when you need them you don’t get through, when they are they are not needed, in the end it drops all the work to zero.