Hacker News new | past | comments | ask | show | jobs | submit login

This is why so many orgs find remote working hard. Everyone has to be willing to compromise on how they communicate to find a middle ground, or the company has to hire for people who work the same way as everyone else. When you have a team made up of people who communicate with different expectations, and they're not willing to accept that other people will think differently about what's reasonable, remote working starts to break down.

Maybe that's why so many companies push for people to return to the office. In-person working where someone can just walk up and interrupt someone else is equally awful for everyone.




I'm all about the compromise. I don't mind waiting for an answer but I'm often hassled for a response in my role and then I need an update from another member of the team. If that response is not forthcoming guess who gets the follow up? Now I'm badgering people who are probably busy but have neglected to tell me and I'm now the block in the pipe to those above me. I don't mind a pat response that they're busy but someone somewhere always needs a status update.


Urgent ad-hoc status update requested by someone above is in most cases a communication anti-pattern. Why would someone need it outside of regular reporting structure (DSM, weeklies etc)? Even in case of disaster recovery, when updates need to be more frequent than daily, it’s better to agree in advance on how communication proceeds and plan the work correspondingly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: