Re: Do I Really Need A Supervisor?

[kilgallen@eisner.decus.org (Larry Kilgallen)]

In article <dewar.859473116@merv>, dewar@merv.cs.nyu.edu (Robert Dewar) writes:
> iDarriel says
> 
> <<A first line engineering manager does *not* have to be technically
> great but needs a good general understanding of the relavant technologies
> and of good engineering practices.  But IMO does *NOT* need to be, and it
> is often better if the manager is not, the technical lead.>>
> 
> Well terminology can get in the way of this discussion, but to me the
> technical lead *is* a manager, because they need to make management
> decisions. Someone has to make technical decisions on overall design
> and style. Sure these decisions can be reached by a consensus process,
> but that is always part of a good management style, but someone does
> ultimately have to make the decisions!

I have run into a lot of companies where the technical leads are
quite specifically moved out of the "management" hierarchy and
restricted to only dealing with technical matters.  For others
in the company, that doesn't really count as "management" since
there is no direct authority for budgets and personnel matters.

It can actually work really well, with the "manager" repeating
back to the larger organization in "manager-speak" the results
of those technical decisions, including schedules and feature-
level conflicts.

If the greater "management" hierarchy wants exclusive use of
that word, it should be fine, just so the process works. While
terminology, as Robert points out, can be a barrier, this is
one time where "giving in" to the greater corporate culture
should be acceptable. It saves semantic energy for c.l.a talk
about "illegal" vs. "erroneous" vs. "shoddy", etc. :-)

Larry Kilgallen