If you have been haunted by the universal question of how technical a PM should be; I'm glad there are people penning down their thoughts on this.
I have met employees and industry peers who are vocal about the fact that expertise in the domain knowledge is a must and then they are some who believe that you really don't need to.
If you read the resume of Project Manager's, some of them are not in the same domain as their college days. I have always been intrigued by the fact- does it really work? It's more of a personal reason you see, I currently work in IT and belong to the communications background. So, I'm always looking for people to attest to the fact that you don't have to be an engineer to manage an IT project.
I hope some day, I can interview PM's and know their opinion on this. Of course, it goes without saying that basic domain knowledge helps and if you are an expert, merrier it is. However, it's perhaps not a necessity.
My mentor 1 (yes, I have 2, 3 and 4) always encouraged me to get into PM and said it helped that I was from non-technical background because it allowed me to connect to my clients very easily and the relationship boosted the communication process.
As long as someone was telling me I could be a PM- I was happy. So, while reading through PM blog's I found this article on PM's technical expertise, click here to read more on the subject.
(Picture: Google images)