![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Note to self:
You learned this in your first week in a full time job.
"Don't respond to angry people you don't know in conference calls".
Let their own team deal with them. They know the person. Or wait a while and say we'll have to deal with this topic later, as it's over running.
It just makes the whole thing drag on, and it can only be resolved offline.
I'm missing my team's Christmas lunch now.
You learned this in your first week in a full time job.
"Don't respond to angry people you don't know in conference calls".
Let their own team deal with them. They know the person. Or wait a while and say we'll have to deal with this topic later, as it's over running.
It just makes the whole thing drag on, and it can only be resolved offline.
I'm missing my team's Christmas lunch now.
no subject
Date: 2008-12-05 12:35 am (UTC)I also tend to want to, during conference calls from Hell, to ask, "why are you doing this?" to the most offensive participant. I haven't done so far, but I suspect that if I ever do, the resultant conversation might be rather interesting if only because people don't expect you to cut right through whatever corporate nonsense they're hiding behind.
(Although I did once answer a 20-paragraph e-mail full of jargonese with simply, "No, probably not.")