Hello all,
After having been part of a few ops- and recruitment nights as a member and SL, I have an idea as to how to improve our communications to be more efficient and with that, more effective.
As you may or may not know, our way of communication (aside from being as efficient as it is, don't get me wrong) isn't free of problems.
The main reason I noticed the flaws of our current communication system is because I had a much easier time communicating with the squad I was leading when in one of Kamitor's recruitment night open platoons.
Our current way of communicating (see attachment "BRTD communication current") consists of three communication 'lines' in mumble (sorted from top to bottom in the command chain):
There's basically 2 problems that I noticed from all of my time playing and leading:
So having painted the problems I currently see in our communications, I propose we do the following (see attachment "BRTD communication suggestion"):
--------- [ Attachments ] ----------
BRTD communication current:
BRTD communication suggestion:
After having been part of a few ops- and recruitment nights as a member and SL, I have an idea as to how to improve our communications to be more efficient and with that, more effective.
As you may or may not know, our way of communication (aside from being as efficient as it is, don't get me wrong) isn't free of problems.
The main reason I noticed the flaws of our current communication system is because I had a much easier time communicating with the squad I was leading when in one of Kamitor's recruitment night open platoons.
Our current way of communicating (see attachment "BRTD communication current") consists of three communication 'lines' in mumble (sorted from top to bottom in the command chain):
- SL chat (PL conveys orders to SL, PL and SL discuss strategy/orders)
- The channel you're currently in (SL relaying orders to squad members, squad battle comms (SBC))
- Whispering (fireteam battle comms (FBC)
There's basically 2 problems that I noticed from all of my time playing and leading:
- Crowding the communication line (people talking in mumble channel instead of whispering or using the battle comms to relay orders)
- The order a PL gives only reaches the squad members at the discretion of the SL: only the SL knows the order and has to 'translate' it to the members. The order effectively is caught in SL chat and no one else knows about it. The SL in turn has to relay the message which in my opinion, is unnecessary. Why not have the Platoon lead give to the order to EVERYONE so literally everyone knows what the new orders are?
TL;DR: have the Platoon lead shout orders to literally everyone to save time and labor not to mention that everyone knows what the other squads are up to and can act accordingly.
So having painted the problems I currently see in our communications, I propose we do the following (see attachment "BRTD communication suggestion"):
- Introduce a fourth communications line. Namely one where the Platoon lead directly broadcasts to everyone which means:
- No extra layer between the person that gives the orders and the people that execute them saving time and potential for communicative noise. There's no difference between [the PL giving the order and the SL actually leading the squad] and [having the SL give the order only then to lead the squad].
- Improve clarity between squads to improve cohesion and teamwork
- No extra layer between the person that gives the orders and the people that execute them saving time and potential for communicative noise. There's no difference between [the PL giving the order and the SL actually leading the squad] and [having the SL give the order only then to lead the squad].
- Highly encourage people to use the proper communication line for which the recipient of their message is meant for. That means not using the squad battle comms for stuff related to fireteam battle comms.
An example would be to have the PL broadcast the order over a green line (see suggestion pic) and have the SL respond over a blue line or green line to acknowledge depending on the context.
--------- [ Attachments ] ----------
BRTD communication current:
BRTD communication suggestion: