4 ms·

I've had a fair share of this crap myself being the team lead at the time. I didn't go yelling at the dev for not understanding that my contract said team lead

I've had a fair share of this crap myself being the team lead at the time. I didn't go yelling at the dev for not understanding that my contract said team lead and the CTO failed to communicate that role or giving me the opportunity to communicate it. I spoke with the CTO and asked him to clarify the roles and gave him a clear choice. He decided against clear communication and I decided to take more money elsewhere. The problem is oftentimes not the individual being insubordinate. Oftentimes the issue is that Roles and Responsibilities are not clearly defined. This is especially an issue when one of previous colleagues on the same level is promoted to the higher ranking position. It's an even more common issue in big corp and govt. institutions. > Implicit tasks are not always common sense. There is no such thing as implicit tasks. There are implicit tasks, when you sit in your garage and found a company and one guy is a marketing wiz and the other a rockstar dev. You might even have a well working symbiosis then. Everything beyond that needs to(at least some extent) be defined.

ataturk 9y ago
It's very difficult to be contract help and be in a leadership role. It is also difficult to deal with so many "empowered" individuals who are all scrambling and weaseling to position themselves so that they can take on a leadership role. Everyone has been conditioned to push hard to climb the perceived ladder. It's irritating.
rjmill 9y ago
>The problem is oftentimes not the individual being insubordinate. Oftentimes the issue is that Roles and Responsibilities are not clearly defined. This is entirely possible too. I just had an experience where I unwittingly cut the technical lead of my team out of an important conversation simply because I didn't realize he would care. I wanted to limit the scope of the conversation because of time constraints. I told him to his face in a meeting that I was trying to limit the scope of the conversation. He was not very happy about that. Needless to say, once I realized what a butthead I had been, I apologized profusely, explained that I had misunderstood the situation, and promised not to let that ever happen again. It ended up being fine after that, but boy did I feel dumb. Point is, don't just assume that new hires will automatically infer what everyone's role is.

ataturk 9y ago

It's very difficult to be contract help and be in a leadership role. It is also difficult to deal with so many "empowered" individuals who are all scrambling and weaseling to position themselves so that they can take on a leadership role. Everyone has been conditioned to push hard to climb the perceived ladder. It's irritating.

rjmill 9y ago

>The problem is oftentimes not the individual being insubordinate. Oftentimes the issue is that Roles and Responsibilities are not clearly defined. This is entirely possible too. I just had an experience where I unwittingly cut the technical lead of my team out of an important conversation simply because I didn't realize he would care. I wanted to limit the scope of the conversation because of time constraints. I told him to his face in a meeting that I was trying to limit the scope of the conversation. He was not very happy about that. Needless to say, once I realized what a butthead I had been, I apologized profusely, explained that I had misunderstood the situation, and promised not to let that ever happen again. It ended up being fine after that, but boy did I feel dumb. Point is, don't just assume that new hires will automatically infer what everyone's role is.