MSG(P) Rafael Aguilera1285535<div class="images-v2-count-0"></div>Challenges faced from small Units splitting into different areas of operation... What are some lessons learned?2016-02-06T23:13:39-05:00MSG(P) Rafael Aguilera1285535<div class="images-v2-count-0"></div>Challenges faced from small Units splitting into different areas of operation... What are some lessons learned?2016-02-06T23:13:39-05:002016-02-06T23:13:39-05:00SFC William Farrell1285546<div class="images-v2-count-0"></div>Ive bene out too long Top to give you a good answer!Response by SFC William Farrell made Feb 6 at 2016 11:19 PM2016-02-06T23:19:03-05:002016-02-06T23:19:03-05:00SGT Private RallyPoint Member1285953<div class="images-v2-count-0"></div>When my company deployed, there were teams scattered throughout AO. To maintain constant and concise communication, Platoons leadership, Ops team, Command, and staff reps (HR, Comms, etc) held a weekly CUB (Co Update Brief) over SVOIP with a PPT that everyone had a slide to modify and brief. Since Ops, Cmd, and staff reps were at one base, we had daily meetings. . . at times. Furthermore, we operated under big boy rules. Any Leader at any level that doesn't understand communication and can't be trusted to hold their own and trust (or at least "trust but verify"), you're going to have an issue. Having at least one Senior, NCO or PL, that you trust at remote locations is probably a safe template to start from, but that's just from what I saw at my level. Meanwhile, you'll get much more responses if you add more leadership/deployment - related tags.Response by SGT Private RallyPoint Member made Feb 7 at 2016 8:23 AM2016-02-07T08:23:09-05:002016-02-07T08:23:09-05:002016-02-06T23:13:39-05:00