3 ms·
No, I'm judging by my extensive experience co-working with remotes. No "time zone" makes it legit to be non-responsive for over 24h during work days. It's 100%
by avip 9y ago
No, I'm judging by my extensive experience co-working with remotes. No "time zone" makes it legit to be non-responsive for over 24h during work days. It's 100% ok to be not working but that's referred to as "day off" and should be communicated as such.
- JimDabell 9y agoIt's not just you that has extensive experience with this. Sure, some teams are managed synchronously as if they were co-located, but just because that's what works for you, it doesn't mean that is the only way to do things. You quite clearly have a concept of a standard work day because you keep going on about "work days". Not all teams are run that way. If you communicate to your team that you want them to work to set hours and they don't? Sure, that's unprofessional. But stop pushing the idea that your way is the only way and everybody else is unprofessional. Different teams have different norms.
- dllthomas 9y agoI think it is misleading to label "expected to be responsive within 24 hours during the work week" as "managed synchronously as if co-located". Sure, there are even looser arrangements that can work great for some contexts. And it's absolutely the case that norms vary. But "within 24 hours" more-or-less puts all timezones on the same footing and is pretty far from co-location.