Questioning authority

I explain ALL THE TIME if given the chance. Sometimes, if in a hurry, I'll say "just do it because I SAID SO".<div><br></div><div>But every leadership book I have read tells you that you SHOULD explain, if you can. It leads to more people following you willingly. People are much more likely to do a job if they know WHY.</div><div><br></div><div>It's just human nature.</div><div><br></div><div>Everyone uses the argument "well what about if you are under fire in combat". I have found that by telling people what I said above, they ALWAYS follow me when I tell them "because I said so" mainly because they realize that I would explain IF I had time.</div><div><br></div><div>I also, in my in briefs talking to my Soldiers, tell them that I will ALWAYS explain "why" if I can, but if I tell you to do it, do it.</div><div><br></div><div>I never have issues.</div><div><br></div><div>I don't usually tell people to punt/just color.</div><div><br></div><div>I also, in a decade of being an NCO, have NEVER made a Soldier do pushups, and never ONCE had a Soldier disrespect me or not do what I ask.&nbsp;</div><div><br></div><div>I have a slightly differently leadership style than many.</div>

<div>I don't always see asking "why" as questioning authority.</div><div><br></div><div>Soldiers deserve to be given a "purpose" for every "task". &nbsp;They don't need the purpose so the feel important but so they can most effectively accomplish the mission. &nbsp;A Soldier who knows how his task fits in to the higher units mission not only has a sense of purpose but a guiding direction that leads to the desired end state.</div><div><br></div><div>If the Soldier is digging a hole for a fighting position he will dig it differently if he knows how the fighting position fits in to the sector and much differently &nbsp;if he knows the hole is for a pipe. &nbsp;Also when the Soldier understands task and purpose they may know a better way to do things and recommend it as a new course of action. &nbsp;Too often I have seen Soldiers who were not given a purpose for their task waste a lot of time and effort because they didn't have an understanding of the desired end state.</div><div><br></div><div>If Leaders want Soldiers who are ready to execute tasks as soon as an order is given, ensure leaders are prepared to give a purpose with each task.</div><div><br></div><div>All this said, Soldiers must be respectful and there is a time and place for everything. &nbsp;If you tell a troop to take point or kick in a door, he had better do it.</div>

In garrison (read: not actively engaged in combat), I actually encourage my people to understand the "why'. That's how we learn. When you educate your people, not only do you give them a deeper understanding, but you can also grant them a sense of ownership in the mission.<div><br></div><div>I can just tell you "you have to head-space and time the M2 before firing it" and just leave it at that, but once you understand WHY you have to do it, suddenly it's a lot more important to learn.</div>

I had a boss tell me once that you get two "But, sir..."s before you simply shut up and color.&nbsp; I don't think you get any of those under fire, but it seems appropriate in garrison.&nbsp; <br><br>As far as "Get down!," that seems to be more of a safety issue and only an idiot would ignore it.&nbsp; Darwin says you won't have to deal with that problem very often.<br>

In combat, clearly that is not the best time for discussion. In garrison however, they shouldn't have to ask why, because you should already have told them. You have two options as an NCO you can either; 

I must truly say I am blown away by the informative feedback that I received from this question I honestly didn't see the answers being shifted in the direction that it was. Don't get me wrong explaining to your Soldier is always a plus when done tactfully and for the right reasons, at the appropriate time. Just looking at the majority of the ranks that responded I assumed that many of you grew up under leadership where asking the "why" question was either second guessing your leadership or Soldiers wanting to show their rebellion and that was a NO-GO. Its great to know that we do have leadership out there that strongly believe in changing with this forever changing military force, because if you don't you can either find yourself getting left behind or in trouble because you wanted to be stuck and stubborn in your old ways.

<p>SFC B,</p><p><br></p><p>You have to look at each situation differently, combat and garrison are entirely 2 different environments, while it is expected for a subordinate to do what is told in a perfect world, we all know that there are SMs out there that need to be spoon fed sometimes, or that want to question everything that comes down to them. As an NCO and leader it is our responsibility to ensure that they do understand what is required for the task to prevent any safety or incorrect operations taking place in the end, and sometimes you will have to deal with the occasional smart ass that just wants to try and push the envelope, a good senior NCO also knows how to handle that type of situation as well for the benefit of all involved ;).</p>

The Army of yesterday is gone. The days of blindly following orders has been replaced with smarter more free thinking and self-reliant soldiers. Today's leader has a challenge, understand their soldiers and more importantly learn how to communicate using various types of communication techniques - not a one size fits all. When time permits, leaders should explain the importance of whatever it is they want the soldier to do. Establishing a connection to the mission, helps them relate and in the leaders absence, they can accomplish the mission as expected. This approach leads to and reinforces trust in the leaders ability to lead therefore, at a time when things cannot be explained, they will have enough trust to follow without question. 

I'm a "Why?" Soldier, but for the right reason.  I believe there is a good way and a bad way to ask why.  The difference is the intent behind the question.  The bad "Why?" is when the Soldier automatically has a distaste for the order, and is in search for a reason to complain about it or get out of doing it.  The good "Why?", the one I ask often, is to understand the intent of the order, so that I can take initiative if it leads elsewhere.  

For example: NCO asks me to find a dispatch book for a vehicle.  If I ask why and he/she explains that it needs to be dispatched, I can not only execute the order of finding the book, but also begin the next implied task of PMCSing, QA/QCing, and ultimately dispatching the vehicle without going to the NCO after completing every single little task.  This saves time for both parties.

My "Why?" is just to try and understand the big picture of the order.  The attitude you have when you ask "Why?" is everything; and I think nine times out of ten, if you ask the question with a good attitude and the NCO knows you're only asking so you can make things easier on both you and him/her and get the job done faster, you shouldn't receive any backlash.  Unless of course, the reason for the task really is none of your business.

Just my two cents, SFC.