[QUOTE=Alex_Dubinsky]
People talk about ‘leaders’ as if there’s one kind. In fact, there are two. There is one kind of leader who is cool, who is confident, strong, popular, whom everybody wants to follow and who knows how to bust balls to get things done. There is another kind who is smart, and probably got that way by being a bit nerdy, etc. and who doesn’t inspire people to follow him, and who may be a bit weak and not good at commanding people what to do.
[/QUOTE]
Ever worked with anyone who graduated from the service academies, particularly the Naval Academy? On the whole, those expletive unprintables are SMART, commanding, direct and clear in their speech and deed. They will bust your balls, they are cool, they are confident, and to paraphrase a submarine officer friend of mine, they can walk through their vessel blindfolded naming and describing the purpose and function of any item they lay hands on. They are the ideal of what an officer should be: to the extent that military custom allows them to be “one of the guys” they blend in. To the extent that they must appear superhuman and worthy of absolute trust, they deliver. In your proposed partnering arrangement, where would you put such an officer, and who would you pair them with?
Your partnering idea may be relevant to corporations – and in engineering organizations you do see this frequently in the twin positions of “systems engineer” or “chief scientist” and the “program manager”. The PM controls money and schedule, and ensures that the big picture comes together. The SE or CS concerns himself with the technical details to make sure that when time and money run out, the thing which is delivered does what it must. Nominally the PM is in charge and the SE is on his staff… but woe unto one of the PM’s lower-level managers who disregards the SE’s suggestions. So, partnering in the corporate world? Sure. But the OP is specifically about the military.
In a military setting it is imperative that the authority and responsibility of command reside in a single individual. To that end, the ideal officer possesses both of your (supposedly fractionated) traits in sufficient measure to do his job, and his ideal NCO possesses his or her own strengths that complement the officer’s personality.
The “first shirt” (first sergeant or personnel sergeant) has such a complementary role with the commanding officer that the two jobs are often explained as “mother and father”. The idea is that the Shirt is allowed to have an emotional investment and commitment to the unit’s men, but the CO must appear fair and just at all times, and is limited in what he may do to correct a wayward soldier. The Shirt’s justice may be harder or softer than the rules permit in accordance with his judgment, but the CO, when faced with facts, may be required by law to mete out a specific punishment. It cuts both ways. For some infractions, the Shirt can, at his discretion, assign you a far greater share of the unpleasant duties in a unit and slow-roll the paperwork on your punishment. If questioned, the Shirt will say “Oh, Pvt. So-and-so needs to work on his attention to detail; I’m making him a better soldier, sir,” and by the time the paperwork gets to the CO, he can say “Oh, it’s taken care of, sir.” Sometimes you might prefer to just have the CO yell at you and get docked a week’s pay. As long as it’s handled at that level, the CO never needs to hear about it. But if it comes up between the CO and the Shirt, and they disagree, then excuse the metaphor’s patriarchal bias, please: the CO (as the “father”) always always always has the last word, and that’s the difference between a commissioned officer and an NCO.
I’ve met officers who possessed all of the traits you list, and I’ve met officers who possessed almost no redeeming qualities. I’ve met NCOs all over the spectrum. I think your “two types” theory needs some work.