Some more notes on squad leading.

I have a long way to go in delivering precise and concise orders and contact reports to my squad mates and appreciate the willingness of others to tolerate my squad leading.

That said, I find that the single biggest obstacle to effective squad leading is ill-trained (and usually not trained at all) squad members. You may be an exceptional BC2 player, but you may not necessarily know much about the demands of teamwork and standard operating procedures in my squad.

The first principle of participating in an organized squad is

Let the Squad Leader Lead.

It is noteworthy that many of the players encountered in BC2 have little or no training in disciplined squad operating procedures, so this throws the Squad Leader (SL) into the position of trainer.

There are many styles of teamplay, and many styles of squad leading -- herein I am only concerned with the development and explicit communication of my own leadership style and expectations.
The way I run a squad is not suitable to all player types, and is not intended to accommodate all players types. The top tier players will usually be ill-suited to participating in my squad. While they are very good at what they do, they are not great as team-players within my type of squad. This player type generally runs ahead of the pack and will only feel like he is being held back by my orders (which may indeed be the case). ALL are indeed welcome in my squad, as long as they are willing to follow my orders.

Some common issues I encounter when SLing:

Excessive comm use by an Squad Member. The comm channel must be kept clear as possible for use by the Squad Leader who is tasked with keeping a high level of Situation Awareness and coordinating the movements of all Squad Members.

Comms regarding action outside of the immediate field of operation. Generally speaking, if it is not an immediate threat or a target that we can engage, then it falls under Not Our Problem.

Improper Spawning. Spawning back at base to grab a vehicle of any sort, without prior authorization from the Squad Leader, is very bad, as it disrupts squad cohesion and interrupts the Squad Leader's current strategy.

Generally, I either run an INFANTY squad or a MECHANIZED squad, and I avoid switching between the two without the proper kits on hand.

A Squad Member giving kit and objective orders/suggestions to another Squad Member. Run all such suggestions through the SL. Let the Squad Leader lead.

Running off everytime the MCOMM is flashing. Nothing breaks the unit's force ratio and current strategy faster than a squad member rushing off position, without being ordered, to secure an MCOMM. A squad cannot be everywhere at once, and my squad cannot be responsible for all aspects of the game. As important as the MCOMM is, there are other priorities, such as protecting the periphery of the MCOMM while our team-mates move in to disarm. Remember: the squad leader sets the priorities. You may not agree with my strategy(s), but you will follow my orders.

My Squad Leading methodology centres on bringing order to the squad to maximize force ratio and focus on common targets within a shared field of action.

Anything that disrupts order, reduces available force, detracts the group's focus, or degrades communication will be a grave disservice to the squad.

Ideally, squad members should be close enough to provide fire support, but separated enough to cover maximum area. It is my job as squad leader to ensure that the squad is well-positioned and mutually supportive.

Running in my squad should (and will) be anything but gaming as usual.

I intend to be more rigorous in my application of these principles and build a group of teammates that are familiar and compliant with my standard operating procedures.

When I am in a squad, I will not always be Squad Leader, but I will always make it clear when I have assumed the leadership role.

And one more thing (for now):

For heaven's sake, stay out of my team speak channel if you are not in my squad.