LEADER CONSIDERATIONS AND GIVING ORDERS
The higher you are in the hierarchy the more you will need to take a step back from your team and put more time into situational awareness and procedures. ASOR has a fairly easy rank step from Commander, Squad Leader and Fire Team Leader, you could also include the Command 2IC, Squad 2IC and even a Fire Team 2IC in that if you wanted to.
Taking a step back can mean different things for each role but normally involves things like checking your map, knowing where friendly forces are, reporting to your commander, assessing tactical situations, accepting feedback from your team or teams and a big one staying alive. Nothing is going to mess your team up more than you going down so try not to overly expose yourself when someone in your team can easily conduct that task in your place.
Also the higher you are in that rank structure the more objective based your orders are going to need to be.
There are plenty of orders, small orders like move over there to mission wide orders like capture this objective however when your break them down there is really only two keys to giving orders.
CLEAR and OBJECTIVE
CLEAR – As a leader you need to give orders that are clear, commonly referred to as the Commanders Intent. If your team doesn’t quite know what you meant it leaves a lot of room for bad initiative calls from the team or mistakes to occur. Clear doesn’t always mean what is the outcome of the order but rather the guide path or left and right of arc on achieving the order.
A bad example but it covers my point an order to move to a town and clear the town for example doesn’t mean go to the town and eradicate every living soul including civilians where as an order to move to the town and eliminate enemy combatants there more effectively conveys your orders intent. The balance is passing your intent without leading down the path of micromanagement, go here like this and do this like this.
OBJECTIVE – Objective based orders are the absolute key for any order. Any order small or large should have an objective without the objective the team will never know when they have completed the order and if they are unable to contact you while attempting to carry out the order will never know exactly what they need to do.
An order without an objective will only feedback multiple questions and cause delays and possibly confuse the whole process. For example team move down the road. How far? Should we run? Crawl perhaps? Can we take that vehicle? Whereas an order team move down the road 500m double time and setup all round defence offers little questions and if you were to be shot after giving it the team would still know exactly what to do.
To properly achieve a clear order that you know will cover your intent and objective it is recommended to use an order with WHO, HOW, WHAT, WHEN, and WHY. I am not going to go in depth on this as its more for fixed larger orders and not something to think about when you are on the ground giving quick orders but just an example so you can see it in action.
Example: ASOR(WHO) utilising ALPHA and BRAVO squads(HOW) are to DESTROY THE BRIDGE(WHAT) at 0700(WHEN) IOT PREVENT ENEMY FORCES RE-ENFORCING so THE ALLIED ASSAULT WILL SUCCEED(WHY).
- ASOR LEADERSHIP
- LEADER CONSIDERATIONS AND GIVING ORDERS
- ASOR LEADERSHIP REQUIREMENTS
- TEAM OPERATION
- TACTICAL CONSIDERATIONS
- LEADER COMMUNICATIONS AND REPORTING