I work in the engineering industry and am lucky enough that I get to have privacy and my manager is good. I ensure I do my work and well at that.
But I know friends in IT who absolutely loathe the feeling of being in a monitored jail cell.
I work in the engineering industry and am lucky enough that I get to have privacy and my manager is good. I ensure I do my work and well at that.
But I know friends in IT who absolutely loathe the feeling of being in a monitored jail cell.
IMHO it can actually be more frustrating because one feels more on the hook for keeping an eye on notifications. At least at the office I can zone out or focus on something personal or work related, safely assured if a boss really needs me I can be found in person, rather than just missing a ping and being assumed to be a slacker.
The above depends a lot on your company culture though. It's a common failure mode though.
It's pretty difficult to fix bad social behavior with more tech.
On a tangential note, thanks to WFH, I've grown to hate clockwise with a passion. It's the single most disruptive tool in the remote workplace, especially when combined with private-by-default calendars. Maybe I only worked with bad users, I don't know. I just haven't seen anyone with that consistent a schedule, and no one pays attention to their calendar schedule after they set it once anyway. Have to set a meeting for 5 clockwise users? Tough, you'll either have to ask them individually if that time works, or just ignore calendars altogether and hope the relevant people make it work. I hope it dies soon.
Our team has a backlog of approximately 500 tickets / bugs / work ideas. Nobody has to stretch anything, the backlog will outlive us all.
If you don't believe me, and your system allows this to be reconstructed, find out what your full backlog looked like about 10 years ago, find everything on there that still hasn't been done, and find out what percentage of them actually would have significant business value today.
I know this is a gross generalization but we are dealing in generalities. This is what I have found across many projects. We are not always great at predicting what we will need, and the backlog is BY DEFINITION prioritized. By the time we get down to the lowest priority stuff the statistical expected value gets low enough that we are not even covering our own wages.