Read on Twitter
For just the second time ever we successfully conducted the mission analysis brief in two parts at LTP
MA #1 was the IPB brief.
MA #2 covered the rest the required outputs.
Im sharing my notes because I think there was some serious goodness it it. 1/
MA #1 was the IPB brief.
MA #2 covered the rest the required outputs.
Im sharing my notes because I think there was some serious goodness it it. 1/
breaking this into two briefs forced another touchpoint with the staff and commander and, more importantly, allowed the SCO to better visualize the ENY. We could overlay the multiple ECOAs and start to paint the picture of what the initial IC plan would likely look like. 2/
He could then use that to refine/begin his COADEV guidance concurrently while the staff refined running estimates and continued to turn assumptions into facts via the RFI process. 3/
The IPB brief is codified in our PSOP and requires no significant changes. I did add a couple notes below. In a time constrained environment, I personally think this brief can be presented without a RXL. 4/
MA#2 we conducted the brief twice. Once as an RXL to the XO and/or S3. During this brief, the sections briefed their entire estimate. Through that dialogue, we collected the most important “so what” data and consolidated it in one running estimate (displayed in the CP). 5/
The field grade filter helped screen out stuff that had no impact on how the SCO would “fight the squadron” but allowed for SA across the staff and the XO particularly. (for example, it’s a fact the the LOGSTAT is now due at 0900 daily and not 0700 daily. 6/
(Good for the XO/OPS SGM to know so they can update the BR but the SCO won’t care about that as he’s thinking about COADEV guidance).
Our LTP coach reminded us often when we started to get bogged down in the process, “interesting but irrelevant.” This RXL captured that info 7/
Our LTP coach reminded us often when we started to get bogged down in the process, “interesting but irrelevant.” This RXL captured that info 7/
The MA #2 brief to the SCO was pretty quick (30-minutes or less). We reviewed any updated ENY “stuff” that had occurred since the MA#1 brief, that one consolidated running estimate (hanging in the CP), and finally the rest of the outputs... 8/
... (forces available, proposed mission and intent, CCIR etc) briefed off the COADEV planning tool (also an analog hanging in the CP). 9/
Our ultimate goal is to continue to get as efficient as possible so that we can get the information into the hands of the dude/dudettes that have to actually do the hard work of executing. This has been helpful. 10/10
