The Illusion Of Technically Competent Managers
Filed Under Human Factors, Software Process
The role of technical manager is inherently flawed by nature.
It is insanely rare that you can find someone who is both technically competent and has the people management skills to accomplish this job – so already you are working against the odds. Jurgen’s recent opinion that most software developers are utterly unqualified for such a position, although it comes off a bit harsh, it is probably just as valid a statement as saying that most people-only managers are utterly unqualified to manage technology.
Now, this is why I believe that the technically competent manager is as magical or mysterious as the Loch Ness…
The attrition rate of your understanding and skills is directly proportional at the rate of which your environment changes. This isn’t like building a bridge, bridges have been the same for thousands of years, thus being promoted to a bridge building foreman it would be safe to bet that your last 20 years of bridge building knowledge will suit you just fine until retirement.
This logic just does not hold true in technology. Although you may have an opportunity to code, you are not coding enough to really understand the quirks and turns that a particular software niche contains as it moves and grows.
Even roles such as being an architect take you away from the basic skills that have caused the promotion. These are all very flawed roles by nature.
Perhaps I have been reading to many Zen or Tao books where the core message is to be truly great at something it must be the single thing that you do. And from that perspective the technical manager will always be flawed since it is two roles in one.
8 Responses to “The Illusion Of Technically Competent Managers”
Max,
I think there is an opportunity to address this problem for agile teams. I wrote up
[…] The Illusion of Technically Competent Managers (Max Pool) […]
So what’s a possible solution?
[…] The Illusion Of Technically Competent Managers – Max Pool So there’s no hope for devs… glad that Max agrees in that software building is *not* (I repeat *not*, did you hear?) like building a bridge, an example that was even given again by a speaker at Microsoft DevDays 2008 […]
Max,
don’t yout think that technical manager should resemble generalizing specialist? As Scott Ambler wrote in his famous article: “…someone with a good grasp of how everything fits together”.
@Dominique –
Good question, and to be honest…I don’t know.
Sure having someone who knows how the boxes and arrows are aligned is valuable, but does it make them skilled to manage the people building the boxes and arrows?
If a “true” technical manager is impossible – what is the best runner-up? A generalist, a non-techie people manager, a technie non-people manager…what?
I do not agree that both concepts of technical and manager are totally diametrically opposed.
This question is not limited to just software, consider a medical consultant or registrar who has a great overall understanding. However they may not be aware of the latest techniques, they have a team to do this for them. The same holds true in biological and medical research
A software technical manager who has done all the technical stuff before and can quickly grasp the concepts regards new and evolving development techniques is a good bet.
A must for a technical manager is the ability to build and maintain a very good team that is good at the specific technical roles.
That was a very cool way to explain this concept!!!