Transitioning From Developer To Management?

An anonymous reader writes "After 15+ years as a code monkey, mostly doing back-end systems design / development, I was surprised by recent developments at my workplace that have resulted in my being transitioned into a dual architect / managerial role within the next few weeks. While I am somewhat confident at this point in my career in my experience and training for an architect-type position, I have serious concerns about being able to properly fulfill the role as manager. Aside from 'Become a manager in 2 days' type books, what resources would you recommend I look to for guidance in this transition?"

Comments

Running shoes....

[GuyverDH]

Seriously though, once you've semi-transitioned into a management position, don't expect to have any time to do any other work during normal hours.

You'll spend 120% of your time in meetings, doing paperwork, reporting on issues to upper management, delivering managements responses to underlings and never have a moment to yourself.

You'll find yourself doing your own tasks after that, so that a normal 40 hour week will become a normal 60 to 80 hour week, and you'll still feel like you're falling behind.

Re:best management book ever...EVER!

[DaftShadow]

Mod this guy up. It may be a shallow seeming title, but it is filled with a highly compassionate and true set of advice!

Much like The Art of War is really about how to make Peace, How to Win Friends and Influence People is not about how to make others just do what you want... it is about understanding the elements of social conduct which make us tick. It's about how to inspire the people you work with. How to hold your tongue, when you truly shouldn't say anything. How to accept the good ideas of your coworkers, and how best to speak when their idea isn't so great.

It's one of the most valuable books on social conduct that you can ever read. Check it out.

- DaftShadow

It's not complex, but not easy

[kbob88]

I've been in and out of management over 20 years in technical work. I don't think it's mysterious or complex, but it's not easy either.

Good resources for you:

• The people you manage. Ask them and listen. They'll appreciate it, and probably give you good feedback. Remember to filter their comments, especially based on what you know about their personalities.
• The people you report to. Follow the advice above.
• Courses at a local college. I wouldn't overdo this, but if you could find a good course on organizational politics and power, that might help. Or it could really suck. Ask around.
• Slashdot. Ok, maybe not. But other discussion groups might help. Plus you'll be fairly anonymous, and won't have to censor your questions as much.

Some tips:

• Listen more than you talk.
• Determine what makes the people above you tick and stay on their good side. To them, you need to appear committed, competent, friendly, and loyal, but not fawning and flattering. And don't bug them too much.
• Cultivate good, friendly relationships with your staff, but..
• Set guidelines for your people and stick to them. You've got to enforce the rules. In the end, you're the boss.
• Be organized and take good notes. It'll save your ass someday.
• Develop relationships outside your group and those above you. You need to know what's going on so you don't get blindsided.
• Set metrics and reward achievement.
• Hire good people and ensure they stay. Can't emphasize this enough. And it's really tough to do.
• Don't be afraid to get rid of bad people. Not only is their performance bad, but they're lowering everyone else's performance too. You can't be nice to all the people all the time. If you can't do this, you should just be an architect.
• Raise issues early. Don't be afraid to deliver the bad news. Don't try to hide it. But you've got to have a solution or path forward. As one of my old bosses said: "Come to me with choices not problems."

YMMV, and good luck!