Discussion Locked

Non-IT person in IT Administration

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Recently my Chairman recruited a non-it background senior manager as a head professional services. No doubt the person is good, efficient but in some specific situations he gets or rather puts the other person in a very embarrassing situation.

Once we were discussing about the modules within a product. When we started discussing external interfaces and dependancies of different modules, he immediately bursted out saying that pl don't divert the subject. When we tried to emphasize that this is an integral part of development still he didn't agree saying that' let us don't get away from the core subject, we will talk about dependancies as and when it required' Incidently our CEO dropped in and after hearing, he asked to continue the discussion from all angles. Such incidences happened for couple of times in different situations.

Some times we hear from our friends also that how they got in awkward situation because of improper insistance of a senior manager, only because he is lagging in IT procedures or terminologies.

I think technical competence upto a certain level is definitely required at higher positions. Simply managerial ability will not be sufficient to carry out the task.

5 replies

by j.lupo

Sometimes it is required and sometimes not. If the position requires a high level of technical know-how then yes they should be someone who came from the "trenches". However, most department heads need to keep the department in line with the bigger organizational goals. Perhaps, in this case the senior manager was trying to stay on the topic of the bigger picture. Usually technical project managers and team leads need to delve into the specific details and then produce a summary for the senior executives.

Personally, I find it interesting that the CEO stopped in and got involved. He/She has much more important things to do to run the company than micro-manage. Perhaps the issue at your company is a culture of micro-management and that is the real problem. Just a thought.

by thechas

Some of the best managers I have worked for have had no knowledge or understanding of what I was doing.

Early on, we established a level of trust in each other. I would explain things so that they could discuss issues with other managers with confidence. They backed me up and called me in when needed to provide technical detail.

Establishing trust is the first step in dealing with any new manager. Next, you need to show your competence.

One of the advantages that a non-technical manager can bring is a fresh perspective. Along with forcing you to comprehend how a non-technical person perceives your job.

Another aspect of this situation is jargon. A manager looks at dependencies as outside resources that impact the project schedule. That is why talk of dependencies and interactions appeared to be off topic. You need to shift your jargon to avoid management specific jargon.

Finally, avoid being confrontational in front of others. You need to calmly explain the whats, wheres and whys of your projects until you have established trust with the new manager.

Chas

by jbaker

it has been my exeprience that more often than not, an IT manager does not come from within the field. It seems to be that we are forced to deal with non-technical admininstrators, and still effectively do our jobs. since you seem to be getting a handle on what it is that the manager wants discussed, have those discussions in his presence, then the staff that is actually working on the project can meet and hash out the details of how the project is going to work. Iu realize this reduces your effective programming time, but it appears to be a necessary evil with this boss.

by thebarrywilliamsshow

my boss is also a "non-IT" person.

they are called non-technical managers. they are fine as long as they keep remembering that they are non-technical. the problems arise when a non-technical manager starts to think he is a "technical" manager because the IT folks report to him and he starts to think that he should be making the technical decisions around here.

thats pretty much when all the competent IT people leave and complete idiots are hired.

:-)

by the admiral

A Non-IT manager is OK if they are going to be managing people, but not the business. You need a person in there who can manage the project and the people and has an idea as to what is needed. If not, the non-technical person will get the project and yourself killed.

This discussion is closed to new replies.