Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Businesses The Almighty Buck

Consequences of Turning Down a Promotion? 104

The Fun Guy asks: "I'm part of a research team, doing interesting work on an important topic. However, I've been getting some signals from various superiors that I might be put in charge of another team; the trouble is, that team is dysfunctional, unproductive, and the focus is not as cool as what I'm working on now. I do have career ambitions to move up the ladder of responsibility and authority, and even recently applied for a job three rungs up, mostly as a way to get noticed by the big wigs. It looks like they noticed, but that project looks like a minefield. I really think I'd rather be second banana on a great project than top banana on a lousy one. How bad would it be for my long-term prospects if I say 'Thanks, but no thanks, I'll wait for a better offer'?"
This discussion has been archived. No new comments can be posted.

Consequences of Turning Down a Promotion?

Comments Filter:
  • Personal Experience. (Score:4, Informative)

    by Leroy_Brown242 ( 683141 ) on Thursday February 12, 2004 @06:44PM (#8263383) Homepage Journal

    Back in my days of working for Directv Broadband, I had ambitions of working my way up the food chain to management. I worked up from peon to tier 2 support. The next step was to start being a lead, then a supervisor. But at that point managers started being targets, instead of leaders.

    As time went by, management started asking questions, and really looking down thier nose at me for discontinuing my advencement.

    I can't say I would have gone farther or be happier, but stopping the promotion cycle sure did raise some eyebrows.

  • by phamlen ( 304054 ) <phamlen&mail,com> on Thursday February 12, 2004 @07:34PM (#8264091) Homepage
    My (limited) background: I've been in Tech for 10+ years, some of it as a manager, VP, SVP. I've actually gone up the ladder, gone back to being technical (coder/architect) and gone back up to management. And I've had my share of people refuse 'promotions'. I disagree with the guy who said "you're obviously the wrong person for the job." Some of the most intelligent managers out there know when to avoid a mess. I personally would much prefer choosing someone who recognizes the mess over someone who is just excited to be managing.

    The answer to your particular situation depends a lot on your corporate culture. The following questions might help clarify things:

    * What happens to managers who fail in your company? Are they fired? Do they get another chance?

    * Does the company routinely promote technical people into management? Or do they prefer bringing in outside people? Or do they just keep the managers they have? Or to put it another way, is this your last chance? Or will there be more opportunities?

    * Are you highly valued? That is, if someone says "Hmmm... X, Y, and Z are great", are you X, Y, or Z? [A mediocre worker might need to seize at any opportunity. A great one will probably get several chances.]

    Some other thoughts:

    * If the team is really so dysfunctional, then it's unlikely that someone new to management will be able to fix it. It sounds like they need someone seasoned enough in management to be able to use their authority easily, discern whose opinions can be trusted, defuse the existing problems, etc. You might not be a good choice.

    * Make SURE that you get the authority to remove people from the project. Without requiring someone else's approval. Otherwise, you might get stuck with a bad team and the inability to fix it. (Hiring the right people is really the greatest tool a manager has - everything else pales in comparison to having the right people on the team.)

    * If you don't want to take the job, you need a good excuse why you shouldn't. 'The project isn't cool' is terrible - and, at least for me, would prevent you from ever getting considered for another promotion. I want managers I can depend on, even when the work is boring but necessary.

    * A good excuse might be something like: "I appreciate the offer, but our team is really working well right now and I don't feel right about abandoning them at this crucial point." or "I think we're on the verge of some critical research right now, and I would really like to stay on the team." If you can subtly make the point "well, I could do it but I think there are other things that are more important for me to do", you would be in the best position.

    * Finally, if you do take the position: There is absolutely nothing (in my opinion) so kickass as turning a dysfunctional team into a functional one. For me, it rivals any coding that I've ever done. The perception that "oh, THAT team will definitely get it done." is great - and when you know you turned it around, that's a bonus.
  • Can you hack it? (Score:4, Informative)

    by AlecC ( 512609 ) <aleccawley@gmail.com> on Friday February 13, 2004 @06:08AM (#8267903)
    You say the current team is a mess. Management probably know that and want you to fix it. So the question to you is - can you fix it?

    If you cannot, you'll have a miserable time working with people you don't get on with on a "less cool" project. And you'll probably end up with a blot on your CV which will take a bit of rubbing out.

    But that is the downside. The upside is that, if you can fix the team, you'll have a great time because your achieveing something (in human rather than technical terms). The un-coolness won't matter, and you'll have gold star on your CV.

    So it is time to do a bit of self-evaluation. Are you up to it? Of course, you cannot know, but you can make a guess. And then you have to take a risk. But it is a risk either way. If you go for it, you may fail. If you don't it may be a while until the next opportunity comes along (though it will - very few things are Once In A Lifetime).

I have hardly ever known a mathematician who was capable of reasoning. -- Plato

Working...