Monitoring Remote Staff
The discussion
Sven: Our department should drop the activity-tracking software completely. It counts keystrokes and mouse movements, which tells you nothing about whether a report is any good, and it has made people resentful.
Aisha: I'm not defending keystroke counting, but managers need some visibility. Since we went remote, two projects slipped by a month and nobody noticed until the client complained.
Mateo: I'd argue the slipped projects are a planning failure, not a monitoring failure. If milestones had been defined clearly with weekly check-ins, the delay would have shown up in the first fortnight regardless of anyone's mouse movements.
Aisha: Weekly check-ins sound nice until you have twelve direct reports and three of them are in other time zones. Some form of dashboard saves me from twelve separate meetings.
Mateo: A dashboard of task status is different from surveillance, though. If staff update their own progress on a shared board, you get your overview without anyone feeling watched.
Aisha: That's a distinction I can accept. A self-reported board, with the tracking software switched off, would meet my needs if people actually keep it current.
Sven: I'll take that deal and make sure my team updates the board daily. Anything is better than being timed when I pause to think.