4 ms·
The problem is that when you do this, and then don't go to the meeting, and then a decision is made that you don't agree with, you are told, "well you had a cha
by jedberg 7y ago
The problem is that when you do this, and then don't go to the meeting, and then a decision is made that you don't agree with, you are told, "well you had a chance but you didn't come to the meeting".
The other problem is that sometimes people will literally see you working in your cube/office during the meeting and then ask you why you declined if you clearly weren't busy, because they don't equate coding with being busy. Sitting at your desk == not busy in their mind.
So now you have a political problem because you're seen as uninterested/not a team player.
- nwalker85 7y ago>>Sitting at your desk == not busy in their mind Maddeningly, these are the same people who feel like you have to be in the office 100% of the time so they feel like you are working.
- LegitShady 7y agoThats why you suggest an alternate time, so that the onus is on them. Alternately if you know someone competent and willing to attend to make sure it goes right, ask them if they'll go. Whether you come off as disinterested or busy is up to you.
- kraigie 7y ago>The problem is that when you do this, and then don't go to the meeting, and then a decision is made that you don't agree with, you are told, "well you had a chance but you didn't come to the meeting". I would have if the item, I cared about was on the agenda. This is why agenda are a) important b) should be sent out 24 hours or more before the meeting c) should be rigdly followed. Anything else is either poor communication or a waste of productivity. This gives everyone time to review the agendas. Making a decision which is worth attending,which is worth escalating. Beside the manager should be representing you anyway. >if you clearly weren't busy, because they don't equate coding with being busy. Sitting at your desk == not busy in their mind. Coding yes. A skype meeting would be busy in their mind.