2 Comments

I really enjoyed this vignette, empathized deeply with the hangriness, and what a strong rhetorical flair at the finish. Did you do anything to capture / codify and disseminate this process of cross application data analysis to your peers / higher (either at the time for this specific example, or at anytime in the future REF an analogous experience)? It seems like the logic of taking source data points (like radar hits from the fires cell) and bringing them down stream into a program where you can make sense of them would be an invaluable and repeatable process until a better suited program came to be. Were you a data advocate from the beginning? Did the value / career long relevancy / gravity of what you had done (making sense of data across programs (being the human outside of the computer (or box))) stand out to you at the time?

Expand full comment
author
Jun 26·edited Jul 2Author

Astin, thanks again for the comments and questions.

1) 'Did you do anything to capture this process?' I shared it with my intel cell and my ODB's 18F (Intel Sergeant), as well as suggested the Fires cell should post radar hits into the mIRC more often. Unfortunately, as I'll detail more on the 26th (https://downrangedata.substack.com/p/12-a-stryker-dies-in-diyala), the higher HQ wasn't very supportive. Uptake of mIRC was hit and miss across the rest of deployments, but ISR and MEDEVAC were always huge proponents.

2) 'Data advocate from the beginning?' While I've been a nerd since the outset (0.2, https://downrangedata.substack.com/p/02-ive-always-been-a-data-nerd) I don't think I really understood my approach was novel until later in my career, closer to when I became a MAJ. And so, while what I was doing stood out, it didn't do so in a way that was a clear advantage until later.

Expand full comment