4 ms·

"I will get rid of someone if their behavior leads the rest of the team to slack off or miss targets." If I understand you correctly, you're saying that you al

by mattm 17y ago

"I will get rid of someone if their behavior leads the rest of the team to slack off or miss targets." If I understand you correctly, you're saying that you allow the team to use an individual as a scapegoat and not take responsibility for their own actions. Could you elaborate on this? Why do you think this is the best course of action rather than dealing with the people that are not being responsible for their own work? If you let people get away with not taking responsibility once, won't they continue to do it in the future?

mmt 17y ago
If I understand you correctly, you're saying that you allow the team to use an individual as a scapegoat and not take responsibility for their own actions. Despite disagreeing in principle with the OC, I don't think this is at all what he was suggesting. Rather, he was presenting a "view from the top," where if he were to perceive a negative influence (whether or not the influenced parties were, themselves, aware), he would eliminate it.
trevelyan 17y ago
> I could easily imagine a situation, however, where this is not the > desired outcome, such as in a company where software is only a > minor component. Perceptive point by mmt - I do most of the programming work myself. I don't know if I'd feel the same way if a critical employee doing coding for a major system behaved this way. I wouldn't knowingly hire someone like that though, and unless someone was truly critical, I'd rather send them on their way than have them create a situation in which their behavior negatively affected office norms, yes. My business is quite small and doesn't have professional managers, so mmt's expectation that there is a level there to deal with this stuff is wrong. Problems are just more work on my plate and distract from the things that people pay us for.

4 ms·

"I will get rid of someone if their behavior leads the rest of the team to slack off or miss targets." If I understand you correctly, you're saying that you al

by mattm 17y ago

mmt 17y ago
If I understand you correctly, you're saying that you allow the team to use an individual as a scapegoat and not take responsibility for their own actions. Despite disagreeing in principle with the OC, I don't think this is at all what he was suggesting. Rather, he was presenting a "view from the top," where if he were to perceive a negative influence (whether or not the influenced parties were, themselves, aware), he would eliminate it.
trevelyan 17y ago
> I could easily imagine a situation, however, where this is not the > desired outcome, such as in a company where software is only a > minor component. Perceptive point by mmt - I do most of the programming work myself. I don't know if I'd feel the same way if a critical employee doing coding for a major system behaved this way. I wouldn't knowingly hire someone like that though, and unless someone was truly critical, I'd rather send them on their way than have them create a situation in which their behavior negatively affected office norms, yes. My business is quite small and doesn't have professional managers, so mmt's expectation that there is a level there to deal with this stuff is wrong. Problems are just more work on my plate and distract from the things that people pay us for.