• Thanks for stopping by. Logging in to a registered account will remove all generic ads. Please reach out with any questions or concerns.

Military Leadership: Innovation vs. Experience

Meridian

Sr. Member
Inactive
Reaction score
0
Points
160
I've often heard comments such as "Its the military way" or "That's how its done in the military" or "Thousands of people have been doing it before you, and will continue on doing it long after you've left"... etc... as reasoning/arguments against strong incremental or dramatic change within the military world. 

I've heard these same arguments in the civilian world used quite frequently.  My profession (IT Project Management) is one that is dramatically tied to implementing innovative change, and quite frequently, users do not want the newfangled thing because the oldfangled thing has worked for decades, and given their experience,  why change? Why innovate?

This was posted in another thread, and proposes some interesting statistics regarding Age and Leadership, the most prominent being that Younger leaders were invariably much better at Innovating than older:

http://www.mrg.com/documents/Age_and_Leadership.pdf


I'm interested in hearing members thoughts on the following:

1 - Does or should Innovation have an important role in Military Leadership? If so, at what levels?

2 - Generally speaking, is the quantity of experience one holds inversely proportionate to the ability one has to innovate?

 
Your topic is related to this one: "22 Measures of Leadership - New Concept?":
http://forums.milnet.ca/forums/threads/67850/post-657297.html#msg657297
(In that the two papers are written by the same pair of academics).

In reply to your comments:

"I've often heard comments such as "Its the military way" or "That's how its done in the military" or "Thousands of people have been doing it before you, and will continue on doing it long after you've left"... etc... as reasoning/arguments against strong incremental or dramatic change within the military world."   

When you join the military, you will hear this quite often.  Most of the time (IMO) its because the members saying it dont know why a specific thing is done, arent interested in exploring the issue, or dont have time to debate the issue.  The job of your instructors is to teach you what is known now, the way it is known now.  After you have mastered the basics, and learned the occupation, and understand how it relates to other trades, then you can promote innovation, as many CF members do.  Instructors have a set schedule and dont have time to deal with every proposal for change.  There is room for change afterwards, often dependent on the situation, the need, and the type of change you propose.  Many people outside the CF have no idea of the constant level of change within the CF, covering everything from IT to HR to operations and equipment.  It is a continuous learning environment. 

"I've heard these same arguments in the civilian world used quite frequently.  My profession (IT Project Management) is one that is dramatically tied to implementing innovative change, and quite frequently, users do not want the newfangled thing because the oldfangled thing has worked for decades, and given their experience,  why change? Why innovate?"

As we become older, job security becomes more important.  Everyone wants the pension and career advancement.  There is also the matter of professional knowledge, which older managers base their reputations and effectiveness on.  Implementing a new 'tool' lessons their knowledge and expertise, challenging their authority on many levels.  Change also entails risk, which in turn threatens these desires and individual expertise.  Further, even the smallest changes can have wide-ranging impacts, especially in organizations that employ tens of thousands of employees.  One 'minor' change in computer software can create a whole training cycle that interferes with critical operations, communications, production, training cycle planning that may have already been planned for several years in advance, plus the rewrite of numerous procedural manuals, policies, and guidelines (mucho $$$ !!!). Overall, it is not about the age of the managers but the size of the organization and the proliferation of documented material that matters.  The managers have to be convinced that the change is worthwhile, requiring a significant amount of time in proposal and ROI writing.  Other change, as many members have seen, is implemented directly as a result of lessons learned in operational environments. 

"This was posted in another thread, and proposes some interesting statistics regarding Age and Leadership, the most prominent being that Younger leaders were invariably much better at Innovating than older:  http://www.mrg.com/documents/Age_and_Leadership.pdf"

In general I would disagree with this.  While younger employees (as a group, not individually) are much better at innovating, exploring new ideas, and adapting to change, they lack the experience and credibility that older managers (again, as a group, not neccesarily individually) have in regard to how their changes affect the organization as a whole.  This is why many companies have formed leadership teams with mixed levels of expertise and age, as pointed out in your referred-to document.  It is also highly dependent on the workplace environment, some workplaces can adapt more quickly to change than others. 

"I'm interested in hearing members thoughts on the following:
1 - Does or should Innovation have an important role in Military Leadership? If so, at what levels?
2 - Generally speaking, is the quantity of experience one holds inversely proportionate to the ability one has to innovate?"


#1 - Citing my previous comments, there is continuous change and innovation in the military environment, even if you dont see it in person.  As such, most of the military leaders I had contact worth were always open to change, provided you demonstrated its value.  No one likes to waste time, money and people on change that does not improve the situation, or 'change for change's sake'.   
#2 - Your statement implies that the less experience you have, the more ability you have to innovate, which makes little sense.  Rather, experience is directly proportional to the ability to innovate.  The more you know, the more you know what needs to be changed, how to change it, and how to convince others what needs to be changed, plus historical memory and precedent as to the results of similiar previous changes.

In summary, it cannot be denied that there are workplaces out there run by managers and not leaders, and where change is frowned upon.  However, it might help if you cited specific examples of times when change was denied.  Many members here could provide insight into the reasons behind why such changes were denied. 
 
IT tends to chase the latest fads and has an astonishingly high project failure rate. Not a good model for other fields. I work in IT as well.
 
On this, I'd recommend Afghanistan and the Troubled Future of Unconventional Warfare by Hy Rothstein, a retired SF Colonel.  He delves deep into organizational theory and how it interplays with innovation and experience in the military environment.

http://www.amazon.com/Afghanistan-Troubled-Future-Unconventional-Warfare/dp/159114745X/ref=sr_1_2?ie=UTF8&s=books&qid=1199570007&sr=1-2
 
IMHO, leadership results in timely decisions, best results (IAW Comd's end state) and minimal casualties.  If there is time available for innovation which can be sand-tabled, war gamed or at least rehearsed then you can consider that option.  If time is not available then experience and gut feel may have to rule the day.
 
DBA said:
IT tends to chase the latest fads and has an astonishingly high project failure rate. Not a good model for other fields. I work in IT as well.

This is one of those 'known' things - we all hear that IT is known to have a high failure rate, and I have several associates in IT with the same opinion, but Ive never found any hard facts to back it up, so was reluctant to mention it.  Is there a study or research of some kind available that can attest to IT having a high project failure rate?  And how high is 'high'? 
 
Greymatters said:
This is one of those 'known' things - we all hear that IT is known to have a high failure rate, and I have several associates in IT with the same opinion, but Ive never found any hard facts to back it up, so was reluctant to mention it.  Is there a study or research of some kind available that can attest to IT having a high project failure rate?  And how high is 'high'? 

Statistics over IT projects failure rate.

Failure Causes

PROJECT SUCCESS AND FAILURE
 
As we become older, job security becomes more important.

An important caveat on that one GM.  And I speak with some authority here. 

I had a long, successful and unbroken career  - that came to a sudden end - and has taken some time to relaunch.
During the first part of my career, young and foolish, I didn't care what the boss thought and just did "the right thing".  I was luckily successful.

Then I got married, had kids and got a mortgage.... then I started worrying about job security.

Then I got laid off because of a reorganization .... and feared the consequences.

I have discovered it was much like falling out of an aeroplane (which I have also done).  The pre-layoff worry was much worse than the reality.  We have hobbled along for the last few years.

Now I go into my new job with an attitude someplace between young and foolish and old and fearful.  Probably old and foolish.

 
Kirkhill said:
I had a long, successful and unbroken career  - that came to a sudden end - and has taken some time to relaunch.
During the first part of my career, young and foolish, I didn't care what the boss thought and just did "the right thing".  I was luckily successful.
Then I got married, had kids and got a mortgage.... then I started worrying about job security.
Then I got laid off because of a reorganization .... and feared the consequences.
I have discovered it was much like falling out of an aeroplane (which I have also done).  The pre-layoff worry was much worse than the reality.  We have hobbled along for the last few years.
Now I go into my new job with an attitude someplace between young and foolish and old and fearful.  Probably old and foolish. 

As much as I would like to NOT worry about job security, and focus more on enjoying my work and having fun, other people in my life are dependent on my steady income... 
 
Thanks to all for the comments so far.  I'm taking notes and reading.

I just want to clarify - my topic is in no way an attack or deep questioning of how I was ever treated or informed by the military - instead I was thinking about this and had some interesting civilian discussions recently, and was curious about the application in the military world.

One of the things Ive heard often enough is that innovating in a research setting tends to be very difficult the more experience the researcher has.  Thinking "out of the box" becomes more convoluted because the box for that experienced person is so big, so to speak.

There are lots of reasons IT projects fail, but as IT is now essentially required as a change enabler in all major business innovations, it stands to reason that IT would be open to a lot of projects that have very little references available for use in scheduling and risk management.    We've grown so fast technologically speaking that it is hard for project teams to estimate and plan for new innovations occurring even during project phases.
 
Meridian

Most of the guys on this site are dealing with kit that was bought 20 plus years ago based on the technology that was available at the time.  I venture to say that is probably true of the C-17 as well - but I'll stand corrected on that one.

Just recently I was interviewing for a position with a company I had worked with over 20 years ago.  The equipment, and the controls, in the plant were all of 20 years old.  Some of the equipment had been supplied to the predecessors of the plant for other plants almost 40 years ago by my father.  That equipment was still running.  The control panels were still doing their job, mostly.  As far as the company was concerned there was no need to change, revise, modernize, update as the plant was still running and parts were still available.  As new products were demanded new lines were grafted on.  As parts became unavailable alternative solutions were found.

Whatever you put together is likely to have a very long life expectancy.

You can't see five years down the road to know what miracle solutions might be available, whether you will need more space for additional capabilities or less space due to miniaturization.  All you can do is work with the stuff that is at hand and make it work as well as possible....and trust that whoever inherits your solution will do the same.

PS watch out for those marketing buzz words - after a while you start to believe you understand what the salesman was saying.
 
In order to make innovative and effective change within any organization it is important that all aspects of the proposed changes be understood. Within the military environment it is often mid level CF members (ie Officers - Major and Lt.Col and NCM - Sgt and WO) who bring forth and implement change. In these examples you have relatively high level of experiences combined with a studied and acquired flexible approach to arriving at practical and innovative solutions to problems at many different levels. While young employees or soldiers often approach issues with an open mind they do not often have the skills and expereince to understand that immutable law............

THE LAW OF UNINTENDED CONSEQUENCES​

Whether you are in IT, the military or any other proffession many good ideas that appear to be innovative will have a knock on effect with a result completely at odds with the intended outcome due to many, and often misunderstood, inter-relationships with other factors.
 
Back
Top