Forums

I need some input on the content of a notice to the general IT organization about someone who will be taking over some of my responsibilities.

I have taken a new position as an IT architect and one of my former directs will be taking on my non-supervisory design responsibilities.
I want to make a fairly clean transition and make it clear that he will be the go-to guy for design questions.
I have been in the design role for some time and I feel that I need to make a strong statement about my direct's abilities so that he starts on a solid footing.
My dilemma occurs because this fellow is a great developer, but he will be growing into the design role as he goes.

We had just begun the coaching path that would eventually lead him to the design role, but some organization changes have necessitated a quick handover, without appropriate time to socialize our responsibility changes.

Any suggestions are appreciated.

juliahhavener's picture
Licensee Badge

Do you have a start on what you want to say? What are your main things that need to be said? Would it be better to say in person? Say, at a team meeting?

jhack's picture

Two steps, from someone who's done this:

1. Simple message saying "We are pleased and excited that X has taken over the role of [whatever]. Please work with him on all design issues. Further congrats, etc. "

2. Follow through. emails to you regarding design issues should be forwarded to the new guy, copy sender, short text indicating he's the guy now. Same with personal or phone inquiries, meeting invites, etc. If the new guy needs your assistance, it can be done privately.

IT IS VERY IMPORTANT that you step away and let him do the job. If you reply to emails or go to meetings, they'll keep coming to you. If you don't, they'll quickly learn that the most efficient way to get things done is by going to the new guy.

John

juliahhavener's picture
Licensee Badge

John got the biggest part of why I asked if you already have a plan.

The reality is that change is always hard. It's also usually worthwhile. Just draw your line and stand behind it...and HIM.

Mark's picture
Admin Role Badge

Step away, step away, step away. SAY NO.

THe biggest problem with transitions like these is the PREVIOUS guy (you! :wink: ) trying to be "helpful"...which is usually controlling.

ALL requests go to HIM. If HE has a problem with something, HE can come to you, but YOU don't get between him and the customers.

And the sooner you stop answering him and let him do it (and, yes, stumble a bit - this is how orgs grow), the sooner the "transition" pains will go away.

Step away.

Mark